Is Progress Telerik down?

Last checked 12m ago
Current status
Progress Telerik is up

No incidents right now.

Progress Telerik is operational right now. Last checked 12m ago, with no incidents reported in the last 90 days.

Real-time Progress Telerik status, recent outages, and incident history: pulled directly from Progress Telerik's official status page at status.telerik.com every 5 minutes. Pingoru tracks 9 Progress Telerik services and has captured 0 incidents in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment Progress Telerik reports a new incident, free for 3 monitors, no credit card.

Users who monitor Progress Telerik also follow these CI/CD services: PDQ Depot AppVeyor ServiceRocket Subsplash Jellyfish Happo PactFlow Qlty Software SimplyQ View all 8,000+ providers
Progress Telerik uptime 100.00% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

No incidents reported for Progress Telerik in the last 90 days.

Quiet provider, but we'll still email you the instant something changes.

Incident record

Since April 2026 · Statuspage by Atlassian · 9 components checked every 5 minutes
27incidents recorded
3last 12 months
0last 90 days
4 daystypical duration, 12 months

The longest incident in the last year, NuGet Performance on November 19, 2025, ran for 12 days.

Most affected components, last 12 months

  • Telerik NuGet v33

Latest incidents

  • Degraded Performance - High Demand July 8, 2026 · 66 minutes · degraded service

    The Telerik NuGet server is under extremely high demand today, resulting in degraded performance. This may surface to you as a "503 (Service Unavailable)"…

  • API Key Infrastructure February 25, 2026 · 43 minutes · major outage

    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…

  • NuGet Performance November 19, 2025 · 12 days · notice

    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…