Qualified Outage History

15 incidents recorded over the last 365 days, 15 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 Qualified status99.86% uptime history

Every Recorded Qualified Incident

Qualified incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 26, 2026Performance Degradation for a subset of OrgsThis incident has been resolved and performance is back to normal. Thank you for your patience.1h 54mResolved
Aug 27, 2026System-Wide Service DisruptionThis incident has been resolved and is back to normal. Thank you for your patience.4h 42mResolved
Jul 27, 2026Service Disruption: Widget Load & User Login IssuesThis incident has been resolved and the systems are fully back to normal. Thank you for your patience.2h 14mResolved
Jun 10, 2026Application Partial OutageA fix has been implemented for the issue impacting our platform.  We will be closely monitoring to ensure systems are back to normal.51 minResolved
May 8, 2026Application Performance DegradationThis incident has been resolved and everything is back to normal. Thank you for your patience.36 minResolved
Apr 6, 2026Dropdowns unavailable in the ApplicationThis incident has been resolved. Thank you for your patience.1h 45mResolved
Mar 19, 2026Partial Outage impacting Meeting Bookings for Microsoft Calendar usersThis incident has been resolved we put a fix in place and verified all connections have been restored and Meetings are fully operational for these Microsoft Calendar services1h 19mResolved
Mar 17, 2026Large delay in Analytics and Signals data being UpdatedThis incident has been resolved and our Analytics and Signals data is back to normal. Thank you for your patience.4h 35mResolved
Mar 9, 2026Application Performance DegradationThis incident has been resolved and performance is back to normal. Thank you for your patience.2h 9mResolved
Mar 4, 2026Major Service Outage: Authentication & Core FunctionalityThis incident has been resolved and we are seeing a full recovery.1h 50mResolved
Dec 15, 2025Application Performance DegradationThis incident has been resolved and our Application is back to normal. Thank you for your patience.1h 24mResolved
Dec 9, 2025Application Performance DegradationThis incident has been resolved with performance being back to normal. Thank you for your patience.1h 16mResolved
Nov 21, 2025Analytics data not refreshingThis incident has been resolved and our Analytics platform is back to normal. Thank you for your patience.5h 13mResolved
Nov 18, 2025Application Performance DegradationThis incident has been resolved and is back to normal. Thank you for your patience.6h 52mResolved
Nov 17, 2025Meeting Bookings for some orgs unable to processThis incident has been resolved. Thank you for your patience.4h 37mResolved

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 Qualified 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 Qualified 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 Qualified 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 Qualified outage in this window ran 6h 52m, against a mean recovery of 2h 45m. If you depend on Qualified 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.