BigID Outage History

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

Every Recorded BigID Incident

BigID incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 3, 202603-09-2026 IncidentThis incident has been resolved.174h 22mResolved
Sep 1, 202601-09-2026 IncidentThis incident has been resolved.18h 1mResolved
Aug 3, 202608-03-2026 IncidentThis incident has been resolved.46 minResolved
Jul 21, 202621-07-2026 IncidentThe issue affecting Cloud customers has been resolved. We implemented a fix and confirmed that services are operating normally. We will continue monitoring to ensure stability.1h 36mResolved
Jul 13, 202607-13-2026 IncidentThis incident has been resolved.24h 39mResolved
Jul 10, 202607-10-2026 IncidentThis incident has been resolved.16h 11mResolved
Jun 17, 202617-06-2026 OutageThis incident has been resolved.22h 45mResolved
May 19, 202618-05-2026The incident has been resolved.11h 46mResolved
Mar 26, 202625-02-2026: Degraded PerformanceThis incident has been resolved.12h 57mResolved
Dec 5, 2025Critical OutageThis incident has been resolved.18 minResolved
Dec 3, 2025Degraded PerformanceThis incident has been resolved.2h 59mResolved
Nov 19, 2025Intermittent Connectivity IssuesThis incident has been resolved.4h 15mResolved

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