Is Tickaroo Liveblog Down?

What 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 instead of near‑instantly. Impact: Only liveblogs using the "content stream from another liveblog" feature were affected. Direct posting and the editor worked normally. No content was lost, and no error was shown to editors — which is why it took a while to spot. Cause: One very high‑volume liveblog was syndicating to a large number of connected liveblogs at once. The system that copies each update to all of them couldn't keep up. Worse, when it fell behind it kept retrying the same work and re‑doing the entire distribution each time — an amplification effect that multiplied the load and made the backlog grow much faster than the incoming updates alone would explain. Resolution: We added processing capacity and fixed the underlying inefficiency and the retry amplification in how updates are distributed. The backlog began clearing and syndication is returning to normal timing. Prevention: We shipped a permanent fix so the distribution step scales properly and no longer amplifies under load, and added monitoring that alerts us early if syndication starts falling behind again — before customers notice. --- [2026-08-30T19:40:07.952+02:00] (resolved) What 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 instead of near‑instantly. Impact: Only liveblogs using the "content stream from another liveblog" feature were affected. Direct posting and the editor worked normally. No content was lost, and no error was shown to editors — which is why it took a while to spot. Cause: One very high‑volume liveblog was syndicating to a large number of connected liveblogs at once. The system that copies each update to all of them couldn't keep up. Worse, when it fell behind it kept retrying the same work and re‑doing the entire distribution each time — an amplification effect that multiplied the load and made the backlog grow much faster than the incoming updates alone would explain. Resolution: We added processing capacity and fixed the underlying inefficiency and the retry amplification in how updates are distributed. The backlog began clearing and syndication is returning to normal timing. Prevention: We shipped a permanent fix so the distribution step scales properly and no longer amplifies under load, and added monitoring that alerts us early if syndication starts falling behind again — before customers notice. --- [2026-08-30T16:16:12.656+02:00] (monitoring) What 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 instead of near‑instantly. Impact: Only liveblogs using the "content stream from another liveblog" feature were affected. Direct posting and the editor worked normally. No content was lost, and no error was shown to editors — which is why it took a while to spot. Cause: One very high‑volume liveblog was syndicating to a large number of connected liveblogs at once. The system that copies each update to all of them couldn't keep up. Worse, when it fell behind it kept retrying the same work and re‑doing the entire distribution each time — an amplification effect that multiplied the load and made the backlog grow much faster than the incoming updates alone would explain. Resolution: We added processing capacity and fixed the underlying inefficiency and the retry amplification in how updates are distributed. The backlog began clearing and syndication is returning to normal timing. Prevention: We shipped a permanent fix so the distribution step scales properly and no longer amplifies under load, and added monitoring that alerts us early if syndication starts falling behind again — before customers notice. Current status: Mitigations are live and the backlog is draining steadily. Remaining delays are shrinking, and we expect syndication timing to be fully back to normal within a few hours. No further customer action is needed. --- [2026-08-30T14:52:48.975+02:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-08-30T14:14:22.652+02:00] (investigating) We are currently investigating this issue.

**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 minimize customer impact, our engineering team implemented a temporary workaround that restored service while the AWS incident was still ongoing. AWS has since fully resolved the underlying issue, and our services continue to operate normally. We apologize for the disruption and thank all customers for their patience and understanding. Yours, Team Tickaroo --- [2026-07-16T11:20:10.091+02:00] (resolved) The service has been restored. We implemented a workaround to mitigate the impact of the AWS CloudFront incident, and all Tickaroo services are operating normally again. We will continue to monitor the situation closely while AWS works to fully resolve the underlying issue. There may still be intermittent service disruptions while the underlying AWS issue remains unresolved. We apologize for the disruption and thank you for your patience. --- [2026-07-16T10:58:13.767+02:00] (identified) AWS has confirmed an ongoing issue affecting Amazon CloudFront, which is impacting parts of the Tickaroo Liveblog platform. Our engineering team is actively monitoring the situation and will restore normal service as soon as the upstream issue has been resolved. For more information - AWS Health Dashboard: https://health.aws.amazon.com/health/status#openIssuesCategory We will continue to provide updates as more information becomes available. --- [2026-07-16T10:36:32.966+02:00] (identified) Current indications suggest that the issue is related to an outage affecting AWS CloudFront. Our engineering team is actively monitoring the situation and working to restore normal service as quickly as possible. We will provide further updates as soon as more information becomes available. --- [2026-07-16T10:27:35.782+02:00] (investigating) We are continuing to investigate this issue. --- [2026-07-16T10:06:33.899+02:00] (investigating) We are currently investigating an issue affecting parts of the Tickaroo Liveblog platform. Some users may experience service disruptions or degraded performance. Our engineering team is actively working to identify the root cause and restore normal operation as quickly as possible. We will provide further updates as soon as more information becomes available.