Telerik Outage History
3 incidents recorded over the last 365 days, 3 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 Telerik Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 8, 2026 | Degraded Performance - High DemandAll server updates complete, services available at scale | 1h 6m | Resolved |
| Feb 25, 2026 | API Key InfrastructureThe API Key system issue has been resolved. The Telerik NuGet server is able to process keys as an authentication method. | 43 min | Resolved |
| Nov 19, 2025 | NuGet PerformanceAfter a lengthy observation period, we can consider this issue resolved. | 292h 1m | 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 Telerik 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 Telerik 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 Telerik 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 Telerik outage in this window ran 12d 4h, against a mean recovery of 4d 1h. If you depend on Telerik 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.