Steem API Health — Daily Report 2026-10-02

in #steem • yesterday

Steem API Health · 2026-10-02

On 2026-10-02 (UTC) the monitor tracked 12 Steem API nodes with a global uptime of 91.28% across 16,920 measurements. Median latency across all nodes: 172 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, 1410 consecutive failed minutes.
  • Latency change: api.steemit.com slowed by 116 ms vs. yesterday (+116 ms; now 688 ms average).
  • Fastest node: api.campingclub.me at 58 ms average. That is 282 ms below the fleet average of 340 ms across 11 nodes.
  • Slowest node: steem.justyy.com at 901 ms average. That is 561 ms above the fleet average of 340 ms.
  • Consistent leader: api.campingclub.me has been in the top 3 by latency every day this week.
  • Consistent leader: api.justyy.com 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: 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.campingclub.measia100.00 %58 ms57 ms78 ms93 ms0—
steemd.steemworld.orgeu-central100.00 %105 ms102 ms107 ms123 ms0—
api3.justyy.comasia100.00 %115 ms115 ms139 ms168 ms0—
api.moecki.onlineeu-central100.00 %138 ms133 ms155 ms336 ms0—
api2.steemyy.comglobal100.00 %415 ms262 ms888 ms936 ms0—
steem.senior.workers.devglobal99.93 %172 ms163 ms241 ms432 ms1rpc_error ×1
api.steem.fansasia99.93 %202 ms188 ms237 ms541 ms1rpc_error ×1
api.justyy.comus-west99.86 %81 ms72 ms98 ms303 ms2rpc_error ×2
steem.justyy.comus-central99.79 %901 ms806 ms1124 ms3502 ms3http_5xx ×1, rpc_error ×2
api.steemit.comus-east99.50 %688 ms571 ms1069 ms4137 ms7rpc_error ×1, timeout ×6
api.steemyy.comunknown96.38 %864 ms639 ms2143 ms3692 ms51http_4xx ×51
steemd.blazeapps.orgeu-central0.00 %————1410connect_error ×4, http_5xx ×1405, timeout ×1

Latency distribution

Across 15,445 successful measurements today: 64.2 % under 200 ms, 69.6 % under 500 ms, 97.2 % under 1 000 ms. (2.8 % were slower than 1 second.)

Time-of-day pattern

Best hour today: 18:00–19:00 UTC (avg latency 299 ms, 648 measurements). Worst hour: 12:00–13:00 UTC (avg latency 400 ms, 633 measurements).

Error pattern

Most common error today: http_5xx (95.3 %), followed by http_4xx (3.5 %), followed by rpc_error (0.5 %) (of 1,475 total errors).

Biggest outage of the day

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

Week over week

Week-over-week: current week 91.32 %, previous week 91.09 % (Δ +0.22 pp).

NodeΔ uptime
api.steemyy.com-1.40 pp
api.justyy.com-0.45 pp
api.steemit.com-0.07 pp
steem.senior.workers.dev-0.07 pp
api.moecki.online-0.02 pp
steemd.steemworld.org±0.00 pp
api.campingclub.me±0.00 pp
steemd.blazeapps.org±0.00 pp
api2.steemyy.com+0.01 pp
api.steem.fans+0.05 pp
api3.justyy.com+0.15 pp
steem.justyy.com+4.50 pp

Best vs worst performance gap

The fastest node was 15.53× faster than the slowest today (58 ms vs 901 ms). Last week the same factor was 13.52× — the gap is widening.

30-day reliability ranking

Most reliable

    1. steemd.steemworld.org — 100.00 %
    1. api.campingclub.me — 100.00 %
    1. api.moecki.online — 99.99 %

Least reliable

    1. steemd.blazeapps.org — 16.87 %
    1. steem.justyy.com — 97.66 %
    1. api.steemyy.com — 98.22 %

Longest unbroken uptime streak: steemd.steemworld.org — 30 days without a single failed tick.

Visual detail

Steem API Health · detail · 2026-10-02

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