Twingly Outage History
2 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 Twingly Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 28, 2026 | News LiveFeed and Search API delaysThe system has caught up with the delayed article deliveries and we are back to normal operational status. | 3h 11m | Resolved |
| Jul 14, 2026 | Service downtime for News Search and Livefeed (260713-260714)On 2026-07-13, at approximately 22:40, the News Search and Livefeed APIs started experienced service disruptions due to disk issues with one of our servers. On 2026-07-14, at 08:40, the issues were resolved, and the… | -663 min | 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 Twingly 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 Twingly 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 Twingly 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 Twingly outage in this window ran 3h 11m, against a mean recovery of 3h 11m. If you depend on Twingly 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.