Steem API Health — Daily Report 2026-05-11

in #steem2 days ago

Steem API Health · 2026-05-11

On 2026-05-11 (UTC) the monitor tracked 12 Steem API nodes with a global uptime of 91.64% across 17,016 measurements. Median latency across all nodes: 191 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, 1418 consecutive failed minutes.
  • Latency change: api2.steemyy.com slowed by 161 ms vs. yesterday (+161 ms; now 427 ms average).
  • Fastest node: api.moecki.online at 47 ms average. That is 241 ms below the fleet average of 288 ms across 11 nodes.
  • Slowest node: steem.justyy.com at 801 ms average. That is 513 ms above the fleet average of 288 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 %47 ms41 ms61 ms87 ms0
steemd.steemworld.orgeu-central100.00 %103 ms100 ms105 ms127 ms0
steem.senior.workers.devglobal100.00 %139 ms127 ms190 ms314 ms0
api.steem.fansasia100.00 %191 ms181 ms213 ms515 ms0
api.campingclub.measia100.00 %256 ms165 ms504 ms533 ms0
api2.steemyy.comglobal100.00 %427 ms264 ms1022 ms1082 ms0
api.steemit.comus-east100.00 %572 ms490 ms789 ms2008 ms0
steem.justyy.comus-central100.00 %801 ms745 ms1080 ms2514 ms0
api.justyy.comus-west99.93 %81 ms72 ms96 ms224 ms1rpc_error ×1
api3.justyy.comasia99.86 %152 ms119 ms241 ms463 ms2http_5xx ×1, timeout ×1
api.steemyy.comunknown99.86 %398 ms352 ms730 ms1088 ms2http_5xx ×1, rpc_error ×1
steemd.blazeapps.orgeu-central0.00 %1418http_5xx ×1418

Latency distribution

Across 15,593 successful measurements today: 58.0 % under 200 ms, 82.4 % under 500 ms, 98.0 % under 1 000 ms. (2.0 % were slower than 1 second.)

Time-of-day pattern

Best hour today: 04:00–05:00 UTC (avg latency 240 ms, 660 measurements). Worst hour: 19:00–20:00 UTC (avg latency 371 ms, 647 measurements).

Error pattern

Most common error today: http_5xx (99.8 %), followed by rpc_error (0.1 %), followed by timeout (0.1 %) (of 1,423 total errors).

Biggest outage of the day

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

Week over week

Week-over-week: current week 97.86 %, previous week 99.00 % (Δ -1.14 pp).

NodeΔ uptime
steemd.blazeapps.org-23.00 pp
api3.justyy.com-0.01 pp
api.steem.fans+0.08 pp
api2.steemyy.com+0.79 pp
api.campingclub.me+0.83 pp
api.steemit.com+0.84 pp
api.steemyy.com+0.96 pp
steem.justyy.com+0.99 pp
api.moecki.online+1.00 pp
steemd.steemworld.org+1.00 pp
steem.senior.workers.dev+1.02 pp
api.justyy.com+1.26 pp

Best vs worst performance gap

The fastest node was 17.04× faster than the slowest today (47 ms vs 801 ms). Last week the same factor was 17.11× — the gap is stable.

18-day reliability ranking

Most reliable

    1. api3.justyy.com — 99.88 %
    1. api2.steemyy.com — 99.68 %
    1. api.moecki.online — 99.60 %

Least reliable

    1. steemd.blazeapps.org — 89.14 %
    1. api.steem.fans — 99.35 %
    1. api.steemit.com — 99.40 %

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

Visual detail

Steem API Health · detail · 2026-05-11

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