BTC Markets Outage History
3 incidents recorded over the last 365 days, 1 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 BTC Markets Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 23, 2026 | Scheduled Maintenance Downtime: 24th Jul 2026The scheduled maintenance has been completed. | 7h 5m | Scheduled |
| Nov 18, 2025 | Network issues due to CloudFlareThis incident has been resolved. | 3h 52m | Resolved |
| Nov 13, 2025 | Scheduled Maintenance Downtime: 14th Nov 2025The scheduled maintenance has been completed. | 6h 5m | Scheduled |
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 BTC Markets 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 BTC Markets 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 BTC Markets 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 BTC Markets outage in this window ran 7h 5m, against a mean recovery of 5h 41m. If you depend on BTC Markets 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.