Triple A Outage History
3 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 Triple A Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 25, 2026 | Maintenance of the 25-07-2026This incident has been resolved. | 3h 17m | Resolved |
| Jun 7, 2026 | Incident - Issue identifiedThe incident has been resolved and all services are operating normally. | 1h 15m | Resolved |
| Jan 22, 2026 | Scheduled System MaintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
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 Triple A 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 Triple A 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 Triple A 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 Triple A outage in this window ran 3h 17m, against a mean recovery of 1h 41m. If you depend on Triple A 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.