Skai Outage History
9 incidents recorded over the last 365 days, 9 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 Skai Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 1, 2026 | Amazon Advertising Data Sync DegradationThe issue affecting campaign sync and BDS downloads has been fully resolved. All processes are running normally. Please note that as part of our investigation, Amazon negative targeting has been temporarily disabled. We… | 5h 24m | Resolved |
| May 28, 2026 | General data delays in Skai platformThis incident has been resolved. | 13h 8m | Resolved |
| May 8, 2026 | Amazon AWS experiencing outageWe wanted to provide an update regarding the earlier AWS infrastructure issue affecting a small number of servers hosted in the US-East region. While AWS is still continuing recovery activities within their… | 9h 45m | Resolved |
| Mar 10, 2026 | Missing Amazon Stream Performance Data for some AccountsThis issue is resolved. Amazon performance data is now updated in Skai and the campaign budgets will get updated accordingly. | 6h 19m | Resolved |
| Mar 10, 2026 | Criteo API OutageThis incident has been resolved. | 5h 22m | Resolved |
| Mar 1, 2026 | Walmart Performance Data DelaysThis incident has been resolved. | 3h 56m | Resolved |
| Jan 29, 2026 | Amazon DSP Data delayThis incident has been resolved. | 8h 11m | Resolved |
| Dec 28, 2025 | Microsoft Reporting API delays 2025-12-28The issue has been resolved, all features are back to normal | 17h 8m | Resolved |
| Dec 4, 2025 | Microsoft Advertising data delayThis incident has been resolved. | 2h 17m | 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 Skai 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 Skai 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 Skai 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 Skai outage in this window ran 17h 8m, against a mean recovery of 7h 57m. If you depend on Skai 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.