Progress Telerik Outage History

Progress Telerik is up right now

Progress Telerik had 4 outages in the last 2 years totaling 297h 44m of downtime — averaging 0.2 incidents per month.

There were 4 Progress Telerik outages since October 29, 2025 totaling 297h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.telerik.com

Minor July 8, 2026

Degraded Performance - High Demand

Detected by Pingoru
Jul 08, 2026, 02:35 PM UTC
Resolved
Jul 08, 2026, 03:41 PM UTC
Duration
1h 6m
Affected: Telerik NuGet v3
Timeline · 2 updates
  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 →

Major February 25, 2026

API Key Infrastructure

Detected by Pingoru
Feb 25, 2026, 01:50 PM UTC
Resolved
Feb 25, 2026, 02:33 PM UTC
Duration
43m
Affected: Telerik NuGet v3
Timeline · 2 updates
  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 →

Notice November 19, 2025

NuGet Performance

Detected by Pingoru
Nov 19, 2025, 04:14 PM UTC
Resolved
Dec 01, 2025, 08:15 PM UTC
Duration
12d 4h
Affected: Telerik NuGet v3
Timeline · 3 updates
  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 →