AuditBoard Outage History

10 incidents recorded over the last 365 days, 10 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.

Live AuditBoard status99.98% uptime history

Every Recorded AuditBoard Incident

AuditBoard incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 16, 2026GAMEDAY - csuper clear incident title8 minResolved
Sep 14, 2026GAMEDAY INCIDENT - Testing - Better stuff that makes sense to customers29h 3mResolved
Sep 9, 2026GAMEDAY INCIDENT - The Last Test Incident (hopefully) - Title update8 minResolved
Sep 8, 2026GAMEDAY - This is a test - Adding status page using /fh command - editing title1h 24mResolved
Sep 1, 2026TESTING - ACTIVELY IGNORE THIS PLEASE25 minResolved
May 14, 2026TEST INCIDENT (This is a test incident)1154h 36mResolved
Mar 10, 2026Optro Academy link broken after domain change52h 11mResolved
Feb 18, 2026PowerBI ADA Database Upgrade13h 53mResolved
Jan 30, 2026Database re-shard in eu-west-1 region102h 31mResolved
Jan 14, 2026max_replication_slots increase in support-a-0 RDS instance (us-west-2 region)7h 23mResolved

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 AuditBoard 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 AuditBoard 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 AuditBoard 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 AuditBoard outage in this window ran 48d 2h, against a mean recovery of 5d 16h. If you depend on AuditBoard 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.