Steem API Health — Daily Report 2026-05-10

in #steem3 days ago

Steem API Health · 2026-05-10

On 2026-05-10 (UTC) the monitor tracked 12 Steem API nodes with a global uptime of 94.31% across 17,040 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: steemd.blazeapps.org, 966 consecutive failed minutes.
  • Fleet trend: median latency regressed by 30 ms vs. yesterday (+30 ms; now 163 ms).
  • Fastest node: api.moecki.online at 44 ms average. That is 200 ms below the fleet average of 244 ms across 12 nodes.
  • Slowest node: steem.justyy.com at 730 ms average. That is 486 ms above the fleet average of 244 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.blazeapps.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: api.steemyy.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 %44 ms40 ms59 ms99 ms0
api.justyy.comus-west100.00 %79 ms72 ms95 ms180 ms0
steemd.steemworld.orgeu-central100.00 %103 ms100 ms106 ms124 ms0
steem.senior.workers.devglobal100.00 %133 ms124 ms177 ms252 ms0
api.steem.fansasia100.00 %193 ms179 ms208 ms521 ms0
api.campingclub.measia100.00 %204 ms158 ms489 ms505 ms0
api2.steemyy.comglobal100.00 %266 ms255 ms289 ms457 ms0
api.steemyy.comunknown100.00 %423 ms361 ms820 ms1348 ms0
api.steemit.comus-east99.93 %556 ms488 ms784 ms1992 ms1timeout ×1
steem.justyy.comus-central99.93 %730 ms671 ms981 ms2498 ms1timeout ×1
api3.justyy.comasia99.86 %128 ms112 ms197 ms226 ms2rpc_error ×2
steemd.blazeapps.orgeu-central31.97 %73 ms65 ms125 ms132 ms966http_5xx ×938, rpc_error ×27, timeout ×1

Latency distribution

Across 16,070 successful measurements today: 61.3 % under 200 ms, 85.8 % under 500 ms, 99.0 % under 1 000 ms. (1.0 % were slower than 1 second.)

Time-of-day pattern

Best hour today: 04:00–05:00 UTC (avg latency 240 ms, 708 measurements). Worst hour: 09:00–10:00 UTC (avg latency 280 ms, 648 measurements).

Error pattern

Most common error today: http_5xx (96.7 %), followed by rpc_error (3.0 %), followed by timeout (0.3 %) (of 970 total errors).

Biggest outage of the day

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

Week over week

Week-over-week: current week 99.05 %, previous week 99.07 % (Δ -0.02 pp).

NodeΔ uptime
steemd.blazeapps.org-8.74 pp
api3.justyy.com-0.03 pp
api.steem.fans+0.04 pp
api2.steemyy.com+0.71 pp
api.steemit.com+0.77 pp
api.campingclub.me+0.78 pp
api.steemyy.com+0.88 pp
steemd.steemworld.org+0.89 pp
steem.justyy.com+0.89 pp
api.moecki.online+0.90 pp
steem.senior.workers.dev+0.94 pp
api.justyy.com+1.05 pp

Best vs worst performance gap

The fastest node was 16.59× faster than the slowest today (44 ms vs 730 ms). Last week the same factor was 17.63× — the gap is stable.

17-day reliability ranking

Most reliable

    1. api3.justyy.com — 99.89 %
    1. api2.steemyy.com — 99.66 %
    1. api.moecki.online — 99.58 %

Least reliable

    1. steemd.blazeapps.org — 95.00 %
    1. api.steem.fans — 99.32 %
    1. api.steemit.com — 99.37 %

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

Visual detail

Steem API Health · detail · 2026-05-10

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-10T00:00:00Z — 2026-05-11T00:00:00Z. Source location: contabo-de-1.