Blockchain status history
Current state: operational — “All Systems Operational” per https://www.blockchain-status.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Blockchain incidents last?
From 6 incidents with a vendor-posted start and resolve time. Longest on record: USD Wires temporarily disabled — 14.0 days (2026-01-12 14:31 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (6)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-08 09:06 UTC | Withdrawals temporarily unavailable | resolved | none | 24 h 37 min |
| 2026-05-20 02:54 UTC | Arbitrum Block Processing delayed | resolved | minor | 14 h 03 min |
| 2026-01-14 15:41 UTC | Naira (NGN) deposit issue | resolved | none | 20 h 34 min |
| 2026-01-12 14:31 UTC | USD Wires temporarily disabled | resolved | none | 13 d 23 h |
| 2025-11-21 10:59 UTC | Cardano deposits/withdrawals delayed | resolved | minor | 2 d 4 h |
| 2025-11-10 15:25 UTC | Polkadot deposits/withdrawals delayed | resolved | critical | 27 h 06 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Blockchain with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"blockchain"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
