低效-高需求
Issues轻微事件
受影响的组件
Telerik NuGet v3
- monitoring
Telerik Nuget服务器目前需求极高,导致性能退化. 这可能是一个“ 503 (服务不可用) ” 错误响应 。 再试一次再做一次,再做一次 例如,再试一次,如果失败,请等待20秒再试一次。 这是一个众所周知的、暂时的、我们正在处理和密切监测的局势.
- resolved
所有服务器更新完成, 服务可按规模提供
自动翻译自官方事件更新。
27 Progress Telerik incidents · 2020年3月 — official updates, affected components, duration and resolution details.
Telerik Nuget服务器目前需求极高,导致性能退化. 这可能是一个“ 503 (服务不可用) ” 错误响应 。 再试一次再做一次,再做一次 例如,再试一次,如果失败,请等待20秒再试一次。 这是一个众所周知的、暂时的、我们正在处理和密切监测的局势.
所有服务器更新完成, 服务可按规模提供
自动翻译自官方事件更新。
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.
The API Key system issue has been resolved. The Telerik NuGet server is able to process keys as an authentication method.
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).
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.
After a lengthy observation period, we can consider this issue resolved.
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.
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 ****************************************************
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.
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._
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.
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/
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).
The issue has been identified and fixed. We will closely monitor for a few hours before marking this resolved.
After monitoring for a few hours, we are confident the issue has been resolved.
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.
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 are actively responding to an outage of a datacenter cluster that affects the selected components.
We have identified the issue and are implementing mitigations. There may be intermittent availability of specific services as the rollout continues.
A fix has been implemented and we are monitoring the results.
The incident has been resolved, all services are available. Although it has been repaired, we will continue to closely monitor for several additional hours.
Network protection is currently active to protect the servers from becoming unavailable for all customers. [Edit] Removed request for individual build machine IPs, this is no longer a valid mitigation approach.
We have widened the network pipeline to the Telerik NuGet servers significantly, this should unblock many folks in those regions. Please try your builds again, Tips: - MAJOR TIP - Use a packageSourceMapping in your nuget.config to only use the Telerik NuGet Server for Telerik packages. A cross-product example can be found here => https://github.com/LanceMcCarthy/DevOpsExamples/blob/main/src/NuGet.Config (lines 31-47). This can significantly speed up your builds as a bonus. - If you are triggering it immediately after this update notice and it fails, please consider that others teams may be trying at the same time as well. Add a short delay and try it again, avoid immediately retry it to let the post-update congestion tail off. This is more relevant if you have many parallel builds.
We are still continuing to monitor the situation. The service itself is fully operational, however the servers are still behind additional networking protection services and a connection failure may be experienced. This is temporary, but make sure you're using a backoff interval that grows in duration upon each retry attempt. It is still recommended that you add a packageSourceMapping to any nuget.config(s) in your project(s). This is a long term approach that will dramatically reduce the number of network requests your build is performing against the Telerik servers. See the previous update for a link to a code example.
The network protection is still in place to ensure server availability throughout the incident. We are actively working with the datacenter's networking team and are continuing to monitor the situation. Although his doesn't affect most users, it is very disruptive to the folks it does affect. For these folks, we have prepared recommend solutions to use during the event. Please visit https://gist.github.com/LanceMcCarthy/a79a14f6f8b20db335c639e16d0e6cfe#file-suggestions-md
The Telerik NuGet Server is back to full availability, even for affected environments. We will share a postmortem as soon as possible.
We have completed our investigation into the recent issue that only affected customers using high-network-rate sources \(e.g., Azure DevOps, on-prem build servers, etc.\). We have worked with the cloud vendor to implement a solution. If you experience any further trouble, our recommendations are: 1. Subscribe to [https://status.telerik.com](https://status.telerik.com) for updates on any ongoing incidents. 2. Review these suggestions [Offline Options for NuGet Server](https://gist.github.com/LanceMcCarthy/a79a14f6f8b20db335c639e16d0e6cfe#file-suggestions-md). 3. Contact Technical Support at [https://prgress.co/DevToolsSupport](https://prgress.co/DevToolsSupport).
We are investigating some reports of dotnet restore being unable to connect to nuget.telerik.com in certain circumstances. Although we are currently unable to replicate the issue, we're closely working with the responsible teams to monitor specific incidents.
The incident affecting certain customers has been resolved.
The Telerik NuGet servers are operating nominally. However, we are investigating reports of networking issues that are only affecting some customers who are using hosted Azure DevOps agents and AWS build hosts that are located in the West US region. This problem results in a timeout, but only in that environment's networking. At this time, we have not been able to replicate the problem, so we are working with affected customers to try and isolate the issue and determine a solution. This status item will be updated as we learn more information.
We have confirmed there are no issues with the Telerik NuGet services or their firewalls, so the components statuses will revert to Operational for the remainder of this investigation. If you are affected by this issue, please open a support ticket (or reply to your existing case) with your build agent's public IP address. This will allow us to speed up the investigation with the vendor and help restore their connection to your build machines.
We have investigated this with the datacenter vendor and they are unable to determine any possible cause with the available information. This status has been moved to Monitoring, both the datacenter and Progress teams will be monitoring closely over the next several days. If you experience this again, please provide us with all of the following information from the affected machine: ping, traceroute, and public IP address.
After several days of monitoring and investigation, the cloud-to-cloud networking problem from South Central US and West US appears to be resolved. As we were not able to determine a specific root cause, we ask that you please open a support ticket if you experience the problem again. In the ticket, include the results of a ping and tracert for nuget.telerik.com, along with the machine's public IP address. This will allow us to directly investigate that specific connection.
We are currently investigating an issue where attempting to load any page under Your Account (licenses, downloads, support tickets) are unavailable.
This incident has been resolved. If you are still experiencing a problem, please perform a hard refresh of the page. Most browsers perform this if you A) hold the Shift key while clicking the browser's refresh button, or B) use Shift + Ctrl + R key combination.
Some customers may experience issues connectivity to the Telerik NuGet server when searching, restoring or downloading packages. This has been resolved, but we are closely monitoring performance throughout the day.
This incident has been resolved.
The NuGet feed experienced service degradation between 8:18 and 9:20 UTC today. The service is stable now and we are monitoring the performance.
On Sept 19th, 2023 there was a small period inaccessibility to the Telerik NuGet servers due to a DDoS attack. Our DDoS protection was triggered and mitigated the issue: Mitigation Start Time (UTC): 2023-09-15T05:36:14.351560+00:00 Mitigation Stop Time (UTC): 2023-09-15T05:41:43.805230+00:00 All services have returned to normal operation.
We are current investigating an issue where the Kendo Dojo (dojo.telerik.com) runner is not executing code from the editor.
The conditions that cause the problem have been identified; this issue only affects a very small segment of users and only under a very specific circumstance. The issue is still in effect and we are continuing to investigate potential solutions.
Public use of Kendo dojo is verified available and stable.
This event is unrelated to the dojo’s services or it’s client-side implementation. The public status incident was marked resolved as it does not affect the wider audience, while a parallel investigation is continuing for the affected internal audience’s networking configuration.
We have identified an issue with the NuGet v3 server and are working to resolve it. Possible workarounds are: - Use the NuGet v2 server https://nuget.telerik.com/nuget - Download the required NuGet packages from http://telerik.com/account/downloads/ and use them from a local NuGet feed.
All nodes appear to be healthy. We are monitoring the performance.
This incident has been resolved.
You may occasionally get an error "unable to load the service index" when restoring NuGet packages from the Telerik NuGet server. We are currently investigating and will keep you informed.
The issue has been resolved. We'll be closely monitoring the performance for the next few hours to ensure stability.
Downgrading to Degraded Performance => When authenticating with or listing packages from the NuGet Server you may receive a timeout or an error stating "unable to load service index". Tips: - If you are experiencing this, wait a few minutes before attempting again. - If you're using automatic retry, try adding a backoff delay.
Upgrading to Operational. We are continuing to closely monitor systems so that we can act quickly in the event of any unstable behavior.
The service feed has returned to normal operation. Package listing, search and restore are back at full capacity. Important Note: If you are using UI for Blazor, the Telerik.DataSource package requires an additional update. This will occur approximately ~9AM UTC.
We are investigating a newly observed degraded performance issue with the Telerik NuGet servers.
The servers are operational. We are monitoring the traffic to ensure stability over the next 24 hours.
The service has been operating as expected throughout the monitoring period.
We are investigating transient issues that affect a small fraction of users whom are receiving either service index errors from the v3 server; or are getting a 404 from the v2 server. Note: For mission-critical builds, you can always download the .nupkg file of any product from https://www.telerik.com/account/downloads and restore offline.
Notices: 1) The v2 server is operational, we will continue to monitor this endpoint. 2) We are continuing to investigate the v3 service index issue.
We have identified some issues and are working on fixes for them now. Over the next 24 hours, we will be internally testing and validating the fixes before a potential production roll-out tomorrow afternoon.
A fix has been implemented and we are monitoring the results.
We are observing some degraded performance when searching and restoring packages. We are continuing to monitor the situation and taking appropriate actions.
This incident has been resolved.