Blockchain.com Outage History
7 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Blockchain.com Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 11, 2026 | Cardano block processing delayedAll systems are working. We are actively monitoring the current status. | 16h 42m | Resolved |
| Aug 8, 2026 | Withdrawals temporarily unavailableAll systems are working. We are actively monitoring the current status. | 24h 37m | Resolved |
| May 20, 2026 | Arbitrum Block Processing delayedAll systems are working. We are actively monitoring the current status. | 14h 3m | Resolved |
| Jan 14, 2026 | Naira (NGN) deposit issueAll systems are working. We are actively monitoring the current status. | 20h 34m | Resolved |
| Jan 12, 2026 | USD Wires temporarily disabledAll systems are working. We are actively monitoring the current status. | 335h 57m | Resolved |
| Nov 21, 2025 | Cardano deposits/withdrawals delayedAll systems are working. We are actively monitoring the current status. | 52h 29m | Resolved |
| Nov 10, 2025 | Polkadot deposits/withdrawals delayedAll systems are working. We are actively monitoring the current status. | 27h 6m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Blockchain.com incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Blockchain.com Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Blockchain.com acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Blockchain.com outage in this window ran 13d 23h, against a mean recovery of 2d 22h. If you depend on Blockchain.com in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.