Steem API Health — Daily Report 2026-09-18
On 2026-09-18 (UTC) the monitor tracked 12 Steem API nodes with a global uptime of 89.56% across 16,656 measurements. Median latency across all nodes: 169 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:
steemd.blazeapps.org, 1388 consecutive failed minutes. - Latency change:
api.steemyy.comslowed by 151 ms vs. yesterday (+151 ms; now 760 ms average). - Fastest node:
api.campingclub.meat 55 ms average. That is 269 ms below the fleet average of 324 ms across 11 nodes. - Slowest node:
steem.justyy.comat 989 ms average. That is 665 ms above the fleet average of 324 ms. - Consistent leader:
api.campingclub.mehas been in the top 3 by latency every day this week. - Consistent leader:
api.justyy.comhas 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:
api.steemyy.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.campingclub.me | asia | 100.00 % | 55 ms | 52 ms | 80 ms | 109 ms | 0 | — |
steemd.steemworld.org | eu-central | 100.00 % | 103 ms | 102 ms | 108 ms | 123 ms | 0 | — |
api.moecki.online | eu-central | 100.00 % | 136 ms | 134 ms | 150 ms | 218 ms | 0 | — |
api3.justyy.com | asia | 99.93 % | 118 ms | 112 ms | 134 ms | 230 ms | 1 | rpc_error ×1 |
steem.senior.workers.dev | global | 99.93 % | 169 ms | 164 ms | 242 ms | 355 ms | 1 | rpc_error ×1 |
api.steemit.com | us-east | 99.93 % | 557 ms | 540 ms | 583 ms | 886 ms | 1 | rpc_error ×1 |
api.justyy.com | us-west | 99.86 % | 79 ms | 72 ms | 99 ms | 296 ms | 2 | rpc_error ×2 |
api.steem.fans | asia | 99.86 % | 185 ms | 182 ms | 206 ms | 262 ms | 2 | rpc_error ×2 |
api2.steemyy.com | global | 99.71 % | 411 ms | 259 ms | 887 ms | 931 ms | 4 | rpc_error ×4 |
api.steemyy.com | unknown | 93.44 % | 760 ms | 509 ms | 3323 ms | 3549 ms | 91 | http_4xx ×31, http_5xx ×58, rpc_error ×2 |
steem.justyy.com | us-central | 82.06 % | 989 ms | 832 ms | 1832 ms | 3587 ms | 249 | connect_error ×1, http_4xx ×3, rpc_error ×1, timeout ×244 |
steemd.blazeapps.org | eu-central | 0.00 % | — | — | — | — | 1388 | http_5xx ×1388 |
Latency distribution
Across 14,917 successful measurements today: 66.6 % under 200 ms, 73.8 % under 500 ms, 97.9 % under 1 000 ms. (2.1 % were slower than 1 second.)
Time-of-day pattern
Best hour today: 08:00–09:00 UTC (avg latency 288 ms, 522 measurements). Worst hour: 07:00–08:00 UTC (avg latency 360 ms, 508 measurements).
Error pattern
Most common error today: http_5xx (83.2 %), followed by timeout (14.0 %), followed by http_4xx (2.0 %) (of 1,739 total errors).
Biggest outage of the day
steemd.blazeapps.org had a stretch of 1388 consecutive failed minutes today. Full per-tick view: node detail page.
Week over week
Week-over-week: current week 97.23 %, previous week 91.39 % (Δ +5.84 pp).
| Node | Δ uptime |
|---|---|
steem.justyy.com | -2.41 pp |
api.steemyy.com | -0.58 pp |
api2.steemyy.com | -0.04 pp |
api.justyy.com | -0.03 pp |
api3.justyy.com | -0.01 pp |
steemd.steemworld.org | ±0.00 pp |
api.moecki.online | ±0.00 pp |
steem.senior.workers.dev | ±0.00 pp |
api.campingclub.me | ±0.00 pp |
api.steem.fans | +0.03 pp |
api.steemit.com | +1.02 pp |
steemd.blazeapps.org | +72.16 pp |
Best vs worst performance gap
The fastest node was 17.98× faster than the slowest today (55 ms vs 989 ms). Last week the same factor was 14.58× — the gap is widening.
30-day reliability ranking
Most reliable
steemd.steemworld.org— 100.00 %
api.campingclub.me— 100.00 %
api.moecki.online— 99.96 %
Least reliable
steemd.blazeapps.org— 16.98 %
steem.justyy.com— 91.86 %
api.steemyy.com— 98.39 %
Longest unbroken uptime streak: steemd.steemworld.org — 30 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, transaction538622423f0e7f5f0ec6245c5ebdff0e76983249in block62068 - Reporter account: @steem-api-health
- Operated by: @greece-lover (witness vote: https://steemitwallet.com/~witnesses)
Measurement window: 2026-09-18T00:00:00Z — 2026-09-19T00:00:00Z. Source location: contabo-de-1.


Comprehensive latency and uptime breakdown. The widening gap between fastest and slowest public endpoints highlights the importance of maintaining regional monitoring nodes.