Steem API Health — Daily Report 2026-07-22

in #steem6 days ago

Steem API Health · 2026-07-22

On 2026-07-22 (UTC) the monitor tracked 12 Steem API nodes with a global uptime of 83.22% across 16,992 measurements. Median latency across all nodes: 132 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, 1416 consecutive failed minutes.
  • Fastest node: api.campingclub.me at 53 ms average. That is 230 ms below the fleet average of 282 ms across 10 nodes.
  • Slowest node: steem.justyy.com at 872 ms average. That is 590 ms above the fleet average of 282 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 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 %53 ms52 ms67 ms84 ms0
steemd.steemworld.orgeu-central100.00 %102 ms102 ms106 ms127 ms0
api3.justyy.comasia100.00 %109 ms111 ms130 ms145 ms0
api.moecki.onlineeu-central100.00 %116 ms131 ms148 ms328 ms0
steem.senior.workers.devglobal100.00 %158 ms154 ms210 ms322 ms0
api.steemit.comus-east100.00 %569 ms557 ms598 ms854 ms0
steem.justyy.comus-central100.00 %872 ms818 ms1045 ms2803 ms0
api2.steemyy.comglobal99.93 %149 ms150 ms207 ms265 ms1rpc_error ×1
api.justyy.comus-west99.79 %81 ms73 ms97 ms303 ms3rpc_error ×3
api.steemyy.comunknown98.87 %616 ms458 ms1018 ms4099 ms16http_4xx ×16
api.steem.fansasia0.00 %1416http_5xx ×1, rpc_error ×1415
steemd.blazeapps.orgeu-central0.00 %1416http_5xx ×1416

Latency distribution

Across 14,140 successful measurements today: 68.2 % under 200 ms, 76.5 % under 500 ms, 98.8 % under 1 000 ms. (1.2 % were slower than 1 second.)

Time-of-day pattern

Best hour today: 18:00–19:00 UTC (avg latency 253 ms, 590 measurements). Worst hour: 22:00–23:00 UTC (avg latency 408 ms, 577 measurements).

Error pattern

Most common error today: rpc_error (49.8 %), followed by http_5xx (49.7 %), followed by http_4xx (0.6 %) (of 2,852 total errors).

Biggest outage of the day

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

Week over week

Week-over-week: current week 82.77 %, previous week 82.23 % (Δ +0.54 pp).

NodeΔ uptime
api.moecki.online-3.62 pp
api3.justyy.com-0.03 pp
steemd.steemworld.org-0.01 pp
api.steemit.com-0.01 pp
api.steem.fans±0.00 pp
steemd.blazeapps.org±0.00 pp
api.campingclub.me+0.01 pp
api2.steemyy.com+0.02 pp
api.justyy.com+0.22 pp
steem.justyy.com+0.33 pp
api.steemyy.com+1.23 pp
steem.senior.workers.dev+8.36 pp

Best vs worst performance gap

The fastest node was 16.45× faster than the slowest today (53 ms vs 872 ms). Last week the same factor was 20.07× — the gap is narrowing.

30-day reliability ranking

Most reliable

    1. steemd.steemworld.org — 100.00 %
    1. api.steemit.com — 99.96 %
    1. api.campingclub.me — 99.80 %

Least reliable

    1. steemd.blazeapps.org — 0.00 %
    1. api.steem.fans — 0.00 %
    1. api3.justyy.com — 97.47 %

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

Visual detail

Steem API Health · detail · 2026-07-22

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-07-22T00:00:00Z — 2026-07-23T00:00:00Z. Source location: contabo-de-1.