Tickaroo Liveblog Outage History
4 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 Tickaroo Liveblog Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 30, 2026 | Content Streams Syndication StalledWhat happened: Liveblogs that automatically pull in content from another liveblog stopped updating on time. Posts were still being created at the source, but they reached the connected liveblogs with growing delays… | 5h 25m | Resolved |
| Jul 16, 2026 | Service Disruption – Tickaroo Liveblog Platform**Resolved** Hi, The incident has been fully resolved. The service disruption was caused by an upstream outage affecting **AWS CloudFront**, which impacted the delivery of parts of the Tickaroo platform. To… | 53 min | Resolved |
| Jun 24, 2026 | Introduction of Dedicated Tickaroo Bot User-AgentsThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jun 1, 2026 | Authentication Infrastructure Upgrade (Descope Migration)The scheduled maintenance has been completed. | 12h 0m | 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 Tickaroo Liveblog 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 Tickaroo Liveblog 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 Tickaroo Liveblog 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 Tickaroo Liveblog outage in this window ran 12h, against a mean recovery of 5h 5m. If you depend on Tickaroo Liveblog 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.