Steem API Health — Daily Report 2026-05-05
On 2026-05-05 (UTC) the monitor tracked 12 Steem API nodes with a global uptime of 99.95% across 17,016 measurements. Median latency across all nodes: 163 ms. Today's full picture and notable patterns below.
All measurements are taken from a single European location (Germany). Latency to nodes hosted outside Europe will naturally be higher than for users connecting from those regions. Want to contribute measurements from your region? See the participation block below.
Observations
- Longest outage today:
api.justyy.com, 1 consecutive failed minute. - Fastest node:
api.moecki.onlineat 49 ms average. That is 211 ms below the fleet average of 260 ms across 12 nodes. - Slowest node:
steem.justyy.comat 796 ms average. That is 536 ms above the fleet average of 260 ms. - Consistent leader:
api.moecki.onlinehas been in the top 3 by latency every day this week. - Consistent laggard:
api.steemit.comhas been in the bottom 3 by latency every day this week. - Consistent laggard:
steem.justyy.comhas been in the bottom 3 by latency every day this week.
Nodes
| Node | Region | Uptime | Avg | p50 | p95 | p99 | Errors | Error classes |
|---|---|---|---|---|---|---|---|---|
api.moecki.online | eu-central | 100.00 % | 49 ms | 41 ms | 63 ms | 149 ms | 0 | — |
steemd.steemworld.org | eu-central | 100.00 % | 105 ms | 100 ms | 113 ms | 129 ms | 0 | — |
steem.senior.workers.dev | global | 100.00 % | 137 ms | 124 ms | 183 ms | 407 ms | 0 | — |
api.steem.fans | asia | 100.00 % | 189 ms | 178 ms | 198 ms | 516 ms | 0 | — |
api2.steemyy.com | global | 100.00 % | 266 ms | 256 ms | 278 ms | 468 ms | 0 | — |
api.campingclub.me | asia | 100.00 % | 342 ms | 475 ms | 499 ms | 525 ms | 0 | — |
api.steemit.com | us-east | 100.00 % | 550 ms | 490 ms | 784 ms | 1988 ms | 0 | — |
steem.justyy.com | us-central | 100.00 % | 796 ms | 687 ms | 1357 ms | 3373 ms | 0 | — |
steemd.blazeapps.org | eu-central | 99.93 % | 77 ms | 68 ms | 82 ms | 133 ms | 1 | rpc_error ×1 |
api.steemyy.com | unknown | 99.93 % | 385 ms | 338 ms | 685 ms | 1102 ms | 1 | http_5xx ×1 |
api.justyy.com | us-west | 99.79 % | 96 ms | 76 ms | 133 ms | 652 ms | 3 | rpc_error ×3 |
api3.justyy.com | asia | 99.79 % | 130 ms | 114 ms | 195 ms | 229 ms | 3 | rpc_error ×2, timeout ×1 |
Latency distribution
Across 17,008 successful measurements today: 60.6 % under 200 ms, 87.1 % under 500 ms, 98.6 % under 1 000 ms. (1.4 % were slower than 1 second.)
Time-of-day pattern
Best hour today: 04:00–05:00 UTC (avg latency 244 ms, 719 measurements). Worst hour: 17:00–18:00 UTC (avg latency 285 ms, 708 measurements).
Error pattern
Most common error today: rpc_error (75.0 %), followed by http_5xx (12.5 %), followed by timeout (12.5 %) (of 8 total errors).
Biggest outage of the day
api.justyy.com had a stretch of 1 consecutive failed minute today. Full per-tick view: node detail page.
Week over week
Week-over-week: current week 99.94 %, previous week 98.77 % (Δ +1.17 pp).
| Node | Δ uptime |
|---|---|
api2.steemyy.com | +0.87 pp |
api.justyy.com | +1.02 pp |
api.steemyy.com | +1.04 pp |
api.steem.fans | +1.07 pp |
api.moecki.online | +1.09 pp |
steemd.steemworld.org | +1.12 pp |
steem.senior.workers.dev | +1.17 pp |
api.campingclub.me | +1.23 pp |
api.steemit.com | +1.26 pp |
steem.justyy.com | +1.27 pp |
steemd.blazeapps.org | +3.02 pp |
Best vs worst performance gap
The fastest node was 16.24× faster than the slowest today (49 ms vs 796 ms). Last week the same factor was 10.55× — the gap is widening.
12-day reliability ranking
Most reliable
api3.justyy.com— 99.87 %
api2.steemyy.com— 99.55 %
api.moecki.online— 99.45 %
Least reliable
steemd.blazeapps.org— 99.22 %
api.justyy.com— 99.25 %
api.steemit.com— 99.28 %
Longest unbroken uptime streak: api.moecki.online — 7 days without a single failed tick.
Visual detail
Top: latency distribution per node. Middle: hourly performance. Bottom: cross-region comparison (when multi-source data is available).
Methodology: one condenser_api.get_dynamic_global_properties request per node every 60 seconds, 8-second timeout. Full rules and thresholds in MEASUREMENT-METHODOLOGY.
Want to make these reports more accurate?
Anyone can contribute measurements from their own server. The participant script runs in Docker (3 commands to install) and helps build a global view of node performance.
- Participant script and instructions: https://github.com/greece-lover/steemapps-monitor/tree/main/participant
- Full participation guide: https://github.com/greece-lover/steemapps-monitor/blob/main/docs/PARTICIPATE.md
- Request an API key: visit https://api.steemapps.com/join.html — fully automated, takes about 2 minutes.
Contributors get attribution on the Sources page.
Feedback wanted
Have ideas for additional metrics, views, or analyses you'd like to see? Leave a comment below — the report format is still evolving and your input shapes future versions.
Resources
- Live dashboard: https://api.steemapps.com
- API documentation: https://github.com/greece-lover/steemapps-monitor/blob/main/docs/API.md
- Source code: https://github.com/greece-lover/steemapps-monitor
- Methodology: https://github.com/greece-lover/steemapps-monitor/blob/main/docs/MEASUREMENT-METHODOLOGY.md
- Raw data of this report:
custom_jsonoperationsteemapps_api_stats_daily, transaction75af18dd1ca95fa858a26638b38d7f871e71b669in block26745 - Reporter account: @steem-api-health
- Operated by: @greece-lover (witness vote: https://steemitwallet.com/~witnesses)
Measurement window: 2026-05-05T00:00:00Z — 2026-05-06T00:00:00Z. Source location: contabo-de-1.