API Key Infrastructure
The API Key system issue has been resolved. The Telerik NuGet server is able to process keys as an authentication method.
Home
/
Status
/
Service
.NET and JavaScript UI components, reporting, testing, and developer tools.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 18m ago
9
Components
0
Active incidents
0
Maintenance
100%
90d uptime
API Key Infrastructure
Feb 25, 1:50 PM
Normalized official status-page data for incidents, maintenance, components, and history.
100%
Known uptime
1 known history days
9
Components tracked
0 outage, 0 degraded
29
Incidents indexed
0 active right now
0
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Kendo UI CDN
Operational
Kendo UI Dojo
Operational
Telerik Bower
Operational
Telerik Demos
Operational
Telerik Documentation
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
0
outage days
0
maintenance days
89
unknown days
Latest outages and degradations detected from the official status page.
The API Key system issue has been resolved. The Telerik NuGet server is able to process keys as an authentication method.
After a lengthy observation period, we can consider this issue resolved.
Many of our systems rely on Azure Front Door \(AFD\) for its ability to handle high-volume, high regional availability, fast scalability, DDOS protection and much more. There was a global outage of AFD today, this has a significant cascading effect on almost every corner of the ecosystem, including some of the Telerik systems. Here below is a quoted description from Microsoft’s Azure Status [https://azure.status.microsoft/en-us/status](https://azure.status.microsoft/en-us/status) page. You can read more after they’ve finalized their post-incident review on the [https://azure.status.microsoft/en-us/status/history/](https://azure.status.microsoft/en-us/status/history/) page. _**Azure Front Door - Connectivity issues - Observing recovery**_ _Starting at approximately 16:00 UTC on 29 October 2025, customers and Microsoft services leveraging Azure Front Door \(AFD\) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue._ _Affected Azure services may have included, but were not limited to:_ _App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Azure Virtual Desktop, Container Registry, Media Services, Microsoft Defender External Attack Surface Management, Microsoft Entra ID \(Mobility Management Policy Service, Identity & Access Management, and User Management UX\), Microsoft Purview, Microsoft Sentinel \(Threat Intelligence\), and Video Indexer._
This incident has been resolved.
Maintenance is complete
Access to www.telerik.com and Your Account is available again, but may be intermittent depending on your location as caches are restored. If you are still experiencing issues, you can check Cloudflare's status page for more detail https://www.cloudflarestatus.com/
After monitoring for a few hours, we are confident the issue has been resolved.
This is the final status page update regarding the NuGet v2 Server deprecation. the trackers will also be removed, but this item will remain in the incident history for anyone looking back.
We have concluded the planned brownout of the v2 NuGet service and it is available again. Important Note: The v2 NuGet service will be PERMANENTLY discontinued in one month, on November 20th, 2024. For more details, see our announcement blog post https://www.telerik.com/blogs/sunsetting-nuget-v2-server.
The incident has been resolved, all services are available. Although it has been repaired, we will continue to closely monitor for several additional hours.
Scheduled and completed maintenance windows are separated from incidents.
No recent maintenance windows recorded.
Uptimus tracks the official Progress Telerik status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.telerik.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 9 of 9 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Kendo UI CDN | Operational | Component | Not recorded |
Kendo UI Dojo | Operational | Component | Not recorded |
Telerik Bower | Operational | Component | Not recorded |
Telerik NuGet v3 | Operational | Component | Not recorded |
Telerik Forums | Operational | Component | Not recorded |
Telerik Documentation | Operational | Component | Not recorded |
Telerik Demos | Operational | Component | Not recorded |
Telerik Unpkg CDN | Operational | Component | Not recorded |
Telerik Reporting CDN The content delivery network (CDN) for Telerik Reporting front-end components, such as the HTML5 Report Viewer. | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Progress Telerik is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.