Steem API Health — Daily Report 2026-05-13

in #steem3 days ago

Steem API Health · 2026-05-13

On 2026-05-13 (UTC) the monitor tracked 12 Steem API nodes with a global uptime of 91.60% across 17,028 measurements. Median latency across all nodes: 226 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, 1419 consecutive failed minutes.
  • First failure in 7 days: api.moecki.online had 1 failed tick today.
  • Fleet trend: median latency regressed by 31 ms vs. yesterday (+31 ms; now 226 ms).
  • Latency change: api2.steemyy.com improved by 430 ms vs. yesterday (−430 ms; now 337 ms average).
  • Fastest node: api.moecki.online at 46 ms average. That is 238 ms below the fleet average of 284 ms across 11 nodes.
  • Slowest node: steem.justyy.com at 796 ms average. That is 512 ms above the fleet average of 284 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.justyy.comus-west100.00 %81 ms72 ms97 ms273 ms0
steemd.steemworld.orgeu-central100.00 %101 ms100 ms104 ms123 ms0
steem.senior.workers.devglobal100.00 %136 ms130 ms198 ms281 ms0
api3.justyy.comasia100.00 %149 ms123 ms227 ms472 ms0
api.steem.fansasia100.00 %226 ms190 ms374 ms730 ms0
api.steemyy.comunknown100.00 %361 ms315 ms646 ms993 ms0
api.campingclub.measia100.00 %363 ms476 ms576 ms813 ms0
api.moecki.onlineeu-central99.93 %46 ms42 ms68 ms179 ms1timeout ×1
api.steemit.comus-east99.93 %525 ms492 ms781 ms810 ms1timeout ×1
steem.justyy.comus-central99.93 %796 ms717 ms1090 ms2908 ms1http_5xx ×1
api2.steemyy.comglobal99.37 %337 ms136 ms1007 ms1068 ms9http_5xx ×9
steemd.blazeapps.orgeu-central0.00 %1419http_5xx ×1419

Latency distribution

Across 15,597 successful measurements today: 59.3 % under 200 ms, 81.6 % under 500 ms, 98.6 % under 1 000 ms. (1.4 % were slower than 1 second.)

Time-of-day pattern

Best hour today: 13:00–14:00 UTC (avg latency 248 ms, 649 measurements). Worst hour: 00:00–01:00 UTC (avg latency 362 ms, 649 measurements).

Error pattern

Most common error today: http_5xx (99.9 %), followed by timeout (0.1 %) (of 1,431 total errors).

Biggest outage of the day

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

Week over week

Week-over-week: current week 95.48 %, previous week 99.94 % (Δ -4.46 pp).

NodeΔ uptime
steemd.blazeapps.org-52.54 pp
api.steem.fans-0.73 pp
api.steemit.com-0.18 pp
api.campingclub.me-0.15 pp
api2.steemyy.com-0.07 pp
steem.justyy.com-0.06 pp
api.moecki.online-0.01 pp
steemd.steemworld.org±0.00 pp
api3.justyy.com+0.01 pp
api.steemyy.com+0.03 pp
steem.senior.workers.dev+0.04 pp
api.justyy.com+0.21 pp

Best vs worst performance gap

The fastest node was 17.30× faster than the slowest today (46 ms vs 796 ms). Last week the same factor was 17.54× — the gap is stable.

20-day reliability ranking

Most reliable

    1. api3.justyy.com — 99.90 %
    1. api2.steemyy.com — 99.68 %
    1. api.moecki.online — 99.63 %

Least reliable

    1. steemd.blazeapps.org — 79.37 %
    1. api.steem.fans — 99.40 %
    1. api.steemit.com — 99.45 %

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

Visual detail

Steem API Health · detail · 2026-05-13

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