Bolt Outage History

8 incidents recorded over the last 365 days, 2 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 Bolt Incident

Bolt incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 2, 2026Outage affecting the bolt.com domainIncident is resolved. All Bolt sub-domains continue to be served from both bolt.com and boltapp.com. Refer to https://help.bolt.com for more updates.74h 8mResolved
Oct 2, 2026Outage affecting the bolt.com domainWe are experiencing an outage affecting the bolt.com domain. Bolt services loaded from bolt.com, including Checkout, may fail to load. Services on boltapp.com are not affected. A fix is available now: in every Bolt…-204 minResolved
Jul 22, 2026Backend System UpgradeThe scheduled maintenance has been completed.3h 0mScheduled
Apr 23, 2026Backend System UpgradeThe scheduled maintenance has been completed.3h 0mScheduled
Mar 19, 2026Backend System Upgrade - Thursday March 19th 2026The scheduled maintenance has been completed.1h 0mScheduled
Mar 16, 2026Backend System UpgradeThe scheduled maintenance has been completed.1h 0mScheduled
Mar 11, 2026Backend System Upgrade - Wednesday March 11th 2026 at 10:00 UTCThe scheduled maintenance has been completed.30 minScheduled
Nov 21, 2025Backend System Upgrade - Bolt ProductionThe scheduled maintenance has been completed.30 minScheduled

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 Bolt 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 Bolt 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 Bolt 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 Bolt outage in this window ran 3d 2h, against a mean recovery of 11h 53m. If you depend on Bolt 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.