Steem API Health — Daily Report 2026-05-08

in #steem5 days ago

Steem API Health · 2026-05-08

On 2026-05-08 (UTC) the monitor tracked 12 Steem API nodes with a global uptime of 99.33% across 17,028 measurements. Median latency across all nodes: 160 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: api.steem.fans, 59 consecutive failed minutes.
  • Latency change: api.campingclub.me improved by 157 ms vs. yesterday (−157 ms; now 190 ms average).
  • Fastest node: api.moecki.online at 46 ms average. That is 199 ms below the fleet average of 245 ms across 12 nodes.
  • Slowest node: steem.justyy.com at 749 ms average. That is 504 ms above the fleet average of 245 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 %46 ms41 ms71 ms147 ms0
steemd.blazeapps.orgeu-central100.00 %80 ms68 ms127 ms150 ms0
steem.senior.workers.devglobal100.00 %129 ms127 ms181 ms234 ms0
api2.steemyy.comglobal100.00 %269 ms257 ms443 ms478 ms0
api.justyy.comus-west99.93 %83 ms73 ms97 ms254 ms1timeout ×1
steemd.steemworld.orgeu-central99.93 %102 ms100 ms105 ms129 ms1timeout ×1
api3.justyy.comasia99.93 %128 ms114 ms198 ms224 ms1rpc_error ×1
api.steemyy.comunknown99.93 %395 ms349 ms718 ms1032 ms1timeout ×1
steem.justyy.comus-central99.65 %749 ms666 ms1081 ms3039 ms5http_5xx ×2, timeout ×3
api.campingclub.measia98.59 %190 ms86 ms495 ms537 ms20rpc_error ×20
api.steemit.comus-east98.45 %562 ms488 ms784 ms1991 ms22http_5xx ×21, timeout ×1
api.steem.fansasia95.56 %209 ms180 ms523 ms550 ms63http_5xx ×1, rpc_error ×59, timeout ×3

Latency distribution

Across 16,914 successful measurements today: 62.6 % under 200 ms, 87.2 % under 500 ms, 99.0 % under 1 000 ms. (1.0 % were slower than 1 second.)

Time-of-day pattern

Best hour today: 20:00–21:00 UTC (avg latency 221 ms, 720 measurements). Worst hour: 01:00–02:00 UTC (avg latency 295 ms, 707 measurements).

Error pattern

Most common error today: rpc_error (70.2 %), followed by http_5xx (21.1 %), followed by timeout (8.8 %) (of 114 total errors).

Biggest outage of the day

api.steem.fans had a stretch of 59 consecutive failed minutes today. Full per-tick view: node detail page.

Week over week

Week-over-week: current week 99.86 %, previous week 99.15 % (Δ +0.71 pp).

NodeΔ uptime
api.steem.fans+0.13 pp
api2.steemyy.com+0.60 pp
api.steemyy.com+0.71 pp
api.steemit.com+0.74 pp
api.campingclub.me+0.74 pp
steem.justyy.com+0.75 pp
api.moecki.online+0.76 pp
steemd.steemworld.org+0.76 pp
steem.senior.workers.dev+0.81 pp
api.justyy.com+0.81 pp
steemd.blazeapps.org+1.21 pp

Best vs worst performance gap

The fastest node was 16.28× faster than the slowest today (46 ms vs 749 ms). Last week the same factor was 8.96× — the gap is widening.

15-day reliability ranking

Most reliable

    1. api3.justyy.com — 99.88 %
    1. api2.steemyy.com — 99.62 %
    1. api.moecki.online — 99.54 %

Least reliable

    1. api.steem.fans — 99.29 %
    1. api.steemit.com — 99.31 %
    1. api.campingclub.me — 99.34 %

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

Visual detail

Steem API Health · detail · 2026-05-08

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