Progress Telerik Outage History

Started Jul 08, 2026, 02:35 PM UTC· resolved Jul 08, 2026, 03:41 PM UTC

1. monitoring Jul 08, 2026, 02:35 PM UTC

   The Telerik NuGet server is under extremely high demand today, resulting in degraded performance. This may surface to you as a "503 (Service Unavailable)" error response. Just retry again with a modest incremental backoff. For example, retry again immediately, if that fails, wait 20 seconds try again. This is a known, temporary, situation that we are addressing and closely monitoring.

2. resolved Jul 08, 2026, 03:41 PM UTC

   All server updates complete, services available at scale

Read the full incident report →

Started Feb 25, 2026, 01:50 PM UTC· resolved Feb 25, 2026, 02:33 PM UTC

1. identified Feb 25, 2026, 01:50 PM UTC

   We are aware of a problem that is affecting the use/generation of NuGet API keys. The team is currently working on the issue, subscribe to be automatically notified of progress updates.

2. resolved Feb 25, 2026, 02:33 PM UTC

   The API Key system issue has been resolved. The Telerik NuGet server is able to process keys as an authentication method.

Read the full incident report →

Started Nov 19, 2025, 04:14 PM UTC· resolved Dec 01, 2025, 08:15 PM UTC

1. identified Nov 19, 2025, 04:14 PM UTC

   We are aware of degraded performance resulting in a timeout when fetching NuGet packages; this is due to a dependent system, rather than the NuGet Server itself. A fix is currently in testing and is planned to be deployed to those dependent systems within the next 24 hours, Until the fix is implemented, if you experience any timeout errors when searching or restoring packages, please wait a few minutes and try again (we're seeing an average unresponsiveness timeframe of 2-3 minutes per occurrence).

2. monitoring Nov 20, 2025, 03:25 PM UTC

   We have changed the status to Operational as the NuGet service has been stable and performant for over 18 hours. We will be keeping this incident open, closely monitoring performance, until all the dependent services have finished deploying their planned upgrades.

3. resolved Dec 01, 2025, 08:15 PM UTC

   After a lengthy observation period, we can consider this issue resolved.

Read the full incident report →

Started Oct 29, 2025, 08:08 PM UTC· resolved Oct 30, 2025, 12:02 AM UTC

1. identified Oct 29, 2025, 08:08 PM UTC

   Due to an ongoing global Azure outage, the ability to generate new license keys/key files, is currently unavailable. We are closely monitoring the situation and are working to restore the affected services as soon as possible. Note: Your existing license keys and key files will continue to work as expected.

2. monitoring Oct 29, 2025, 09:32 PM UTC

   Microsoft has shared an update informing customers that a configuration change to Azure Front Door has been reverted. As a consequence of this change, we can confirm network traffic and API requests have returned to our backend services. You should now be able to generate new license key files, script keys, and leverage any dynamic license-related features like Page Templates. Out of an abundance of caution, we are only updating this alert to Monitoring, rather than Resolved. We will continue to closely monitor the situation and update our status as the services are fully restored and Microsoft updates their status to Resolved. **************************************************** From https://azure.status.microsoft/en-us/status Updated at 21:27 UTC on 29 October, 2025 **************************************************** Current status: We initiated the deployment of our ‘last known good’ configuration, which has now successfully completed. We are currently recovering nodes and re-routing traffic through healthy nodes. As recovery progresses, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability until more nodes are fully restored. This recovery effort involves reloading configurations and rebalancing traffic across a large volume of nodes to restore full operational scale. The process is gradual by design, ensuring stability and preventing overload as dependent services recover. We expect continued improvement across affected regions. This means we expect recovery to happen by 23:20 UTC on 29 October 2025 ****************************************************

3. resolved Oct 30, 2025, 12:02 AM UTC

   Microsoft has updated their Azure Front Door status to informational, with full mitigation/recovery expected by 00:40 UTC 30 October 2025. - Current Azure Status can be found at https://azure.status.microsoft/en-us/status - Post INcident Review can be found at https://azure.status.microsoft/en-us/status/history/ We have seen fully reliable and stable operation for the past few hours and are updating our status to resolved.

4. postmortem Oct 30, 2025, 12:06 AM UTC

   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._

Read the full incident report →

Started Jun 12, 2025, 06:53 PM UTC· resolved Jun 12, 2025, 08:07 PM UTC

1. monitoring Jun 12, 2025, 06:53 PM UTC

   There is an ongoing incident with Cloudflare that is affecting portions of Telerik websites and services. Specifically, the ability to access www.telerik.com and Your Account pages, is not currently available. See https://www.cloudflarestatus.com/ for up to date information, we will update our status page as the situation evolves.

2. resolved Jun 12, 2025, 08:07 PM UTC

   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/

Read the full incident report →

Started May 21, 2025, 03:20 PM UTC· resolved May 21, 2025, 06:43 PM UTC

1. investigating May 21, 2025, 03:20 PM UTC

   We are currently investigating an issue with the Telerik NuGet service where 503 errors are return to dotnet SDK and nuget.exe requests (pings will succeed, REST requests will not).

2. monitoring May 21, 2025, 04:07 PM UTC

   The issue has been identified and fixed. We will closely monitor for a few hours before marking this resolved.

3. resolved May 21, 2025, 06:43 PM UTC

   After monitoring for a few hours, we are confident the issue has been resolved.

Read the full incident report →

Started Nov 20, 2024, 02:55 PM UTC· resolved Nov 21, 2024, 03:34 PM UTC

1. monitoring Nov 20, 2024, 02:55 PM UTC

   The Telerik NuGet v2 Server has been permanently deprecated. This notice will be posted for a day or two for folks who might have missed the notifications and blog post. For more details, and a quick solution, please see https://www.telerik.com/blogs/sunsetting-nuget-v2-server.

2. resolved Nov 21, 2024, 03:34 PM UTC

   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.

Read the full incident report →