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.