SafeBreach Outage History

24 incidents recorded over the last 365 days. 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 SafeBreach status100.00% uptime history

Every Recorded SafeBreach Incident

SafeBreach incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 25, 2026SafeBreach Scheduled Maintenance: Sunday, October 25, 2026The scheduled maintenance has been completed.12h 0mScheduled
Oct 11, 2026SafeBreach Scheduled Maintenance: Sunday, October 11, 2026The scheduled maintenance has been completed.8h 0mScheduled
Sep 27, 2026SafeBreach Scheduled Maintenance: Sunday, September 27, 2026The scheduled maintenance has been completed.8h 0mScheduled
Sep 14, 2026SafeBreach Scheduled Maintenance: Monday, September 14, 2026The scheduled maintenance has been completed.8h 0mScheduled
Aug 2, 2026SafeBreach Scheduled Maintenance: Sunday, August 2, 2026The scheduled maintenance has been completed.8h 0mScheduled
Jul 12, 2026SafeBreach Scheduled Maintenance: Sunday, July 12, 2026The scheduled maintenance has been completed.8h 0mScheduled
Jul 5, 2026SafeBreach Scheduled Maintenance: Sunday, July 5, 2026The scheduled maintenance has been completed.8h 0mScheduled
Jun 21, 2026SafeBreach Scheduled Maintenance: Sunday, June 21, 2026The scheduled maintenance has been completed.8h 0mScheduled
Jun 10, 2026SafeBreach Backend Maintenance: Wednesday, June 10, 2026The scheduled maintenance has been completed.2h 0mScheduled
May 31, 2026SafeBreach Scheduled Maintenance: Sunday, May 31, 2026The scheduled maintenance has been completed.8h 0mScheduled
May 18, 2026SafeBreach Backend Maintenance: Monday, May 18, 2026The scheduled maintenance has been completed.1h 0mScheduled
May 11, 2026SafeBreach Backend Maintenance: Monday, May 11, 2026The scheduled maintenance has been completed.2h 0mScheduled
Apr 29, 2026SafeBreach Scheduled Maintenance: Wednesday, April 29, 2026The scheduled maintenance has been completed.8h 0mScheduled
Mar 29, 2026SafeBreach Scheduled Maintenance: Sunday, March 29, 2026The scheduled maintenance has been completed.8h 0mScheduled
Mar 15, 2026SafeBreach Scheduled Maintenance: Sunday, March 15, 2026The scheduled maintenance has been completed.8h 0mScheduled
Mar 9, 2026SafeBreach Scheduled Maintenance: Monday, March 9, 2026The scheduled maintenance has been completed.6h 0mScheduled
Mar 8, 2026SafeBreach Scheduled Maintenance: Sunday, March 8, 2026The scheduled maintenance has been completed.6h 0mScheduled
Mar 1, 2026SafeBreach Scheduled Maintenance: Sunday, March 1, 2026The scheduled maintenance has been completed.8h 0mScheduled
Feb 16, 2026SafeBreach Scheduled Maintenance: Monday, February 16, 2026The scheduled maintenance has been completed.9h 0mScheduled
Feb 15, 2026SafeBreach Scheduled Maintenance: Sunday, February 15, 2026The scheduled maintenance has been completed.9h 0mScheduled
Feb 1, 2026SafeBreach Scheduled Maintenance: Sunday, February 1st, 2026The scheduled maintenance has been completed.12h 0mScheduled
Jan 18, 2026SafeBreach Scheduled Maintenance: Sunday, January 18th, 2026The scheduled maintenance has been completed.8h 0mScheduled
Jan 11, 2026SafeBreach Scheduled Maintenance: January, 11th, 2026The scheduled maintenance has been completed.4h 0mScheduled
Jan 5, 2026SafeBreach Backend Maintenance: Monday, January 5, 2026The scheduled maintenance has been completed.4h 0mScheduled

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 SafeBreach 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 SafeBreach 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 SafeBreach 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 SafeBreach outage in this window ran 12h, against a mean recovery of 7h 8m. If you depend on SafeBreach 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.