Pingdom Outage History
6 incidents recorded over the last 365 days, 6 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 Pingdom Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 8, 2026 | Performance issues in my PingdomThe issue has been resolved and my Pingdom is back to normal. Thanks for your patience, remember that monitoring and alerting was unaffected, and please reach out if you have any questions about this or anything else! | 1h 48m | Resolved |
| Mar 17, 2026 | Performance issues on my Pingdom and the public APIWe've now resolved the incident. Thanks for your patience. | 1h 45m | Resolved |
| Mar 16, 2026 | Increased API response times and slow interface of my PingdomThe issue has been resolved. Thanks for your patience. Please reach out to us if you have any additional questions or concerns. | 1h 22m | Resolved |
| Jan 16, 2026 | Issues accessing the subscriptions and invoices pagesThe issue has been resolved. If a page doesn't show up correctly, refresh without cache and it will work. Thank you for your patience. | 1h 49m | Resolved |
| Nov 18, 2025 | We are investigating a degradation in a subset of our systemsWe've now resolved the incident. Thanks for your patience. | 5h 12m | Resolved |
| Oct 20, 2025 | We are investigating a degradation in a subset of our systemsThe degradation of Page Speed Checks has recovered, tests performed during this outage should populate the dashboard now. No alerting or monitoring was affected, please reach out if you have any questions or issues. | 2h 1m | Resolved |
How to Read This Pingdom 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 Pingdom 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 Pingdom outage in this window ran 5h 12m, against a mean recovery of 2h 20m. If you depend on Pingdom 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.