Bakkt Outage History

15 incidents recorded over the last 365 days, 5 of them resolved, 2 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Bakkt status100.00% uptime history

Every Recorded Bakkt Incident

Bakkt incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Delays in Crypto TransfersHi All - We are currently experiencing delays in processing coin transfers. Transfers may take longer than usual to complete. All pending transactions are queued and will be processed automatically once stability is…—Investigating
Nov 3, 2026Production MaintenanceScheduled maintenance is currently in progress. We will provide updates as necessary.3h 0mScheduled
Oct 30, 2026Monitoring Industry Security EventsWe are aware of the security incident affecting a large crypto exchange and the volatility across digital asset markets. We have seen no impact to Bakkt systems, customer assets, or services. Out of an abundance of…—Investigating
Oct 6, 2026Production MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Sep 22, 2026Intermittent Market DataBetween 08:11 and 10:35 UTC on 22 September 2026, a degradation in market data affected our trading platform. During this period, some customers experienced intermittent order rejections. Affected orders were rejected…0 minResolved
Aug 13, 2026Bakkt Production Maintenance September 1st 2026The maintenance window has concluded.447h 31mResolved
Aug 4, 2026Production Maintenance WindowThe scheduled maintenance has been completed.3h 0mScheduled
Jul 7, 2026Production MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
May 5, 2026Trading Production MaintenanceThe scheduled maintenance has been completed.45 minScheduled
Apr 7, 2026April 7th - Production MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Mar 3, 2026March 3rd - Production MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Feb 23, 2026Delays in Crypto TransfersThis incident is now resolved. You should see transfers processing as normal.32 minResolved
Dec 5, 2025Crypto Transfers Delays Due to Third-Party Cloudflare OutageThis incident has been resolved.5 minResolved
Dec 2, 2025December 2nd - Production MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Nov 18, 2025Increased Latency and Instability Due to Third-Party Cloudflare OutageThis incident has been resolved.20h 45mResolved

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 Bakkt 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 Bakkt 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 Bakkt 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 Bakkt outage in this window ran 18d 15h, against a mean recovery of 1d 13h. If you depend on Bakkt 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.