Steem API Health — Daily Report 2026-05-20

in #steem5 days ago

Steem API Health · 2026-05-20

On 2026-05-20 (UTC) the monitor tracked 12 Steem API nodes with a global uptime of 91.13% across 16,992 measurements. Median latency across all nodes: 250 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, 1416 consecutive failed minutes.
  • Fleet trend: median latency regressed by 80 ms vs. yesterday (+80 ms; now 250 ms).
  • Fastest node: api.moecki.online at 79 ms average. That is 216 ms below the fleet average of 295 ms across 11 nodes.
  • Slowest node: steem.justyy.com at 759 ms average. That is 464 ms above the fleet average of 295 ms.
  • Consistent leader: api.justyy.com has been in the top 3 by latency every day this week.
  • Consistent leader: api.moecki.online has been in the top 3 by latency every day this week.
  • Consistent leader: steemd.steemworld.org has been in the top 3 by latency every day this week.
  • Consistent laggard: api.steemit.com has been in the bottom 3 by latency every day this week.
  • Consistent laggard: steem.justyy.com has been in the bottom 3 by latency every day this week.

Nodes

NodeRegionUptimeAvgp50p95p99ErrorsError classes
api.moecki.onlineeu-central100.00 %79 ms56 ms127 ms211 ms0
steemd.steemworld.orgeu-central100.00 %104 ms101 ms108 ms137 ms0
api.steemyy.comunknown100.00 %419 ms368 ms754 ms1185 ms0
steem.senior.workers.devglobal99.93 %196 ms175 ms329 ms492 ms1rpc_error ×1
api2.steemyy.comglobal99.93 %270 ms183 ms375 ms3266 ms1rpc_error ×1
api3.justyy.comasia99.86 %158 ms140 ms261 ms432 ms2rpc_error ×1, timeout ×1
api.steem.fansasia99.86 %334 ms212 ms602 ms736 ms2rpc_error ×2
steem.justyy.comus-central99.86 %759 ms697 ms1019 ms2705 ms2http_4xx ×1, http_5xx ×1
api.campingclub.measia99.79 %250 ms169 ms558 ms646 ms3rpc_error ×3
api.steemit.comus-east99.65 %593 ms567 ms844 ms936 ms5rpc_error ×4, timeout ×1
api.justyy.comus-west94.70 %80 ms73 ms100 ms216 ms75rpc_error ×75
steemd.blazeapps.orgeu-central0.00 %1416http_5xx ×1415, timeout ×1

Latency distribution

Across 15,485 successful measurements today: 54.3 % under 200 ms, 75.9 % under 500 ms, 98.9 % under 1 000 ms. (1.1 % were slower than 1 second.)

Time-of-day pattern

Best hour today: 22:00–23:00 UTC (avg latency 239 ms, 649 measurements). Worst hour: 07:00–08:00 UTC (avg latency 440 ms, 572 measurements).

Error pattern

Most common error today: http_5xx (94.0 %), followed by rpc_error (5.8 %), followed by timeout (0.2 %) (of 1,507 total errors).

Biggest outage of the day

steemd.blazeapps.org had a stretch of 1416 consecutive failed minutes today. Full per-tick view: node detail page.

Week over week

Week-over-week: current week 90.93 %, previous week 95.48 % (Δ -4.56 pp).

NodeΔ uptime
steemd.blazeapps.org-47.44 pp
api.campingclub.me-2.77 pp
api.steemit.com-1.87 pp
api.steem.fans-1.38 pp
api.justyy.com-0.98 pp
steem.justyy.com-0.14 pp
steemd.steemworld.org-0.04 pp
api.steemyy.com-0.03 pp
steem.senior.workers.dev-0.02 pp
api.moecki.online-0.01 pp
api2.steemyy.com-0.01 pp
api3.justyy.com±0.00 pp

Best vs worst performance gap

The fastest node was 9.61× faster than the slowest today (79 ms vs 759 ms). Last week the same factor was 17.30× — the gap is narrowing.

27-day reliability ranking

Most reliable

    1. api3.justyy.com — 99.90 %
    1. api2.steemyy.com — 99.73 %
    1. api.moecki.online — 99.71 %

Least reliable

    1. steemd.blazeapps.org — 57.35 %
    1. api.campingclub.me — 98.92 %
    1. api.steem.fans — 99.05 %

Longest unbroken uptime streak: api.moecki.online — 14 days without a single failed tick.

Visual detail

Steem API Health · detail · 2026-05-20

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.

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


Measurement window: 2026-05-20T00:00:00Z — 2026-05-21T00:00:00Z. Source location: contabo-de-1.