Degreed Outage History
9 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Degreed Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 21, 2026 | Site Slowness - US RegionService has been restored. This incident is now closed. | 4 min | Resolved |
| Sep 16, 2026 | Sitewide slowness - EU regionThis incident has been resolved. | 49 min | Resolved |
| Aug 31, 2026 | Sitewide Slowness - US RegionThis incident has been resolved, and site performance has returned to normal. A Root Cause Analysis is currently in progress and will be published in the Knowledge Center by the end of the week. Customers with open… | 2h 46m | Resolved |
| Jun 23, 2026 | Login Issues on Degreed Web (US)The US Degreed platform has been fully restored. Our engineering team implemented a fix to our underlying infrastructure, and we will continue to closely monitor the systems to ensure ongoing stability. A full root… | 2h 28m | Resolved |
| Apr 8, 2026 | Search Intermittent DegradationSearch has been restored to full performance. Our team has completed the necessary mitigation steps and the system is stable. We will continue to monitor closely to ensure everything remains healthy. Thank you for your… | 3h 45m | Resolved |
| Feb 26, 2026 | Search Performance DegradationSearch Performance and Integration Data Sync We’re pleased to share that Degreed Search services have been fully restored, and Search functionality is now operating at normal performance levels. Our engineering teams… | 65h 23m | Resolved |
| Dec 5, 2025 | Zendesk Service DisruptionThe Zendesk issue caused by the Cloudflare outage has now been resolved and all services are operating normally. | 48 min | Resolved |
| Nov 25, 2025 | Search Performance DegradationWe have resolved the issue affecting search performance. Response times and result consistency have returned to normal. We continue to monitor closely for any anomalies to ensure full stability. | 4h 52m | Resolved |
| Nov 18, 2025 | Login issues with US and CA production environmentsThis incident has been resolved. | 3h 38m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Degreed incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Degreed Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Degreed acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Degreed outage in this window ran 2d 17h, against a mean recovery of 9h 24m. If you depend on Degreed in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.