Vendor Status Watch

← all vendors

Progress Telerik status history

Current state: operational — “All Systems Operational” per https://status.telerik.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
1incidents, last 90 days
5incidents on record
Incidents per week, last 12 weeks:
Get Progress Telerik alerts in your Slack — free templateRSS for Progress Telerik

How long do Progress Telerik incidents last?

2.5 hmedian incident duration4 measured
12.2 days90th percentile1 in 10 ran longer
43 minmedian, major/critical only1 incident

From 4 incidents with a vendor-posted start and resolve time. Longest on record: NuGet Performance — 12.2 days (2025-11-19 16:14 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (5)

StartedIncidentStatusImpactDuration
2026-07-08 14:35 UTCDegraded Performance - High Demandresolvedminor1 h 06 min
2026-02-25 13:50 UTCAPI Key Infrastructureresolvedmajor43 min
2025-11-19 16:14 UTCNuGet Performanceresolvednone12 d 4 h
2025-10-29 20:08 UTCCloud Service Outagespostmortemminor3 h 54 min
2025-10-10 19:28 UTCAnnouncement: Planned Outageresolvedmaintenance2 d 12 h

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Progress Telerik with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "progress-telerik"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}