Steem API Health — Daily Report 2026-05-16

in #steem5 hours ago

Steem API Health · 2026-05-16

On 2026-05-16 (UTC) the monitor tracked 12 Steem API nodes with a global uptime of 91.48% across 17,040 measurements. Median latency across all nodes: 187 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, 1420 consecutive failed minutes.
  • Fleet trend: median latency improved by 34 ms vs. yesterday (−34 ms; now 187 ms).
  • Latency change: api.steem.fans improved by 123 ms vs. yesterday (−123 ms; now 295 ms average).
  • Fastest node: api.moecki.online at 60 ms average. That is 221 ms below the fleet average of 281 ms across 11 nodes.
  • Slowest node: steem.justyy.com at 703 ms average. That is 422 ms above the fleet average of 281 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 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 %60 ms46 ms120 ms189 ms0
steemd.steemworld.orgeu-central100.00 %101 ms100 ms104 ms127 ms0
steem.senior.workers.devglobal100.00 %153 ms147 ms226 ms321 ms0
api2.steemyy.comglobal100.00 %187 ms175 ms313 ms414 ms0
api.steemyy.comunknown100.00 %381 ms338 ms672 ms1206 ms0
steem.justyy.comus-central100.00 %703 ms647 ms932 ms2482 ms0
api.justyy.comus-west99.93 %80 ms73 ms99 ms230 ms1rpc_error ×1
api3.justyy.comasia99.93 %150 ms133 ms234 ms403 ms1http_5xx ×1
api.steem.fansasia99.37 %295 ms206 ms587 ms636 ms9rpc_error ×9
api.campingclub.measia99.30 %368 ms468 ms579 ms701 ms10rpc_error ×10
api.steemit.comus-east99.30 %614 ms578 ms876 ms1096 ms10rpc_error ×10
steemd.blazeapps.orgeu-central0.00 %1420http_5xx ×1420

Latency distribution

Across 15,589 successful measurements today: 56.1 % under 200 ms, 75.8 % under 500 ms, 99.3 % under 1 000 ms. (0.7 % were slower than 1 second.)

Time-of-day pattern

Best hour today: 03:00–04:00 UTC (avg latency 251 ms, 625 measurements). Worst hour: 18:00–19:00 UTC (avg latency 316 ms, 649 measurements).

Error pattern

Most common error today: http_5xx (97.9 %), followed by rpc_error (2.1 %) (of 1,451 total errors).

Biggest outage of the day

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

Week over week

Week-over-week: current week 91.40 %, previous week 99.86 % (Δ -8.46 pp).

NodeΔ uptime
steemd.blazeapps.org-95.38 pp
api.campingclub.me-2.68 pp
api.steemit.com-1.82 pp
api.steem.fans-1.31 pp
api2.steemyy.com-0.12 pp
api.justyy.com-0.07 pp
steem.justyy.com-0.06 pp
api.steemyy.com-0.04 pp
steemd.steemworld.org-0.03 pp
api.moecki.online-0.02 pp
steem.senior.workers.dev-0.01 pp
api3.justyy.com+0.02 pp

Best vs worst performance gap

The fastest node was 11.72× faster than the slowest today (60 ms vs 703 ms). Last week the same factor was 16.23× — the gap is narrowing.

23-day reliability ranking

Most reliable

    1. api3.justyy.com — 99.90 %
    1. api2.steemyy.com — 99.70 %
    1. api.moecki.online — 99.67 %

Least reliable

    1. steemd.blazeapps.org — 68.16 %
    1. api.campingclub.me — 98.78 %
    1. api.steem.fans — 98.93 %

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

Visual detail

Steem API Health · detail · 2026-05-16

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