iSpot 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 iSpot Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | PHP Security VulnerabilitiesServices have been restored to universal-api and dashboard. | 8h 6m | Resolved |
| Oct 8, 2026 | iSpot WebsiteThis issue has been resolved and all services are fully operational. | 18h 45m | Resolved |
| Oct 2, 2026 | Impressions Delay 9/27-9/28The 9/27-9/28 impressions data delay has been resolved. All impacted data is fully reprocessed and up-to-date. | 30h 6m | Resolved |
| Sep 14, 2026 | Processing Delay 9/11-9/13# Root Cause Analysis: Pixel Measurement Data Delay \(Sept 2–15, 2026\) Sep 24, 2026 ## Summary Between September 2–15, 2026, a data pipeline issue caused delays in processing pixel-based measurement data… | 94h 22m | Resolved |
| Jun 8, 2026 | API Upload FailuresThe fix deployed to address the API upload issue has been successfully validated, and all upload processing is now functioning as expected. We have observed stable performance across affected services. We appreciate… | 45h 25m | Resolved |
| Nov 18, 2025 | iSpot.tv Website OutageThis incident is resolved and full www.ispot.tv functionality is restored. | 7h 49m | Resolved |
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 iSpot 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 iSpot 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 iSpot 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 iSpot outage in this window ran 3d 22h, against a mean recovery of 1d 10h. If you depend on iSpot 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.