Webpagetest Outage History
5 incidents recorded over the last 365 days, 4 of them resolved, 1 still open. 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 Webpagetest Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 13, 2026 | Incident NameThis incident has been resolved. | 16 min | Resolved |
| Aug 10, 2026 | Aug 10 Test NameThis incident has been resolved. | 362h 30m | Resolved |
| Aug 7, 2026 | Test CP SDThis incident has been resolved. | 1 min | Resolved |
| Jun 17, 2026 | WPT Instant and Scheduled Test Execution DisruptionThis incident has been resolved. | 22h 44m | Resolved |
| Mar 10, 2026 | WPT Location Outage - BahrainDue to the ongoing conflict in the region and related impacts to infrastructure, the AWS Bahrain (me-south-1) region is currently experiencing an outage. As a result, the WebPageTest location in Bahrain is offline. We… | — | Investigating |
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 Webpagetest 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 Webpagetest 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 Webpagetest 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 Webpagetest outage in this window ran 15d 2h, against a mean recovery of 4d. If you depend on Webpagetest 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.