User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 545 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 371 ms | 0 |
| Mon 21 | 0 | 0.0 | 707 ms | 0 |
| Mon 23 | 0 | 0.0 | 367 ms | 0 |
| Tue 01 | 0 | 0.0 | 333 ms | 0 |
| Tue 04 | 0 | 0.0 | 560 ms | 0 |
| Tue 06 | 0 | 0.0 | 430 ms | 0 |
| Tue 08 | 0 | 0.0 | 200 ms | 0 |
| Tue 10 | 0 | 0.0 | 477 ms | 0 |
| Tue 12 | 0 | 0.0 | 447 ms | 0 |
| Tue 14 | 0 | 0.0 | 500 ms | 0 |
| Tue 16 | 0 | 0.0 | 293 ms | 0 |
| Tue 19 | 0 | 0.0 | 223 ms | 0 |
| Tue 21 | 0 | 0.0 | 399 ms | 0 |
| Tue 23 | 0 | 0.0 | 403 ms | 0 |
| Wed 01 | 0 | 0.0 | 505 ms | 0 |
| Wed 04 | 0 | 0.0 | 381 ms | 0 |
| Wed 06 | 0 | 0.0 | 395 ms | 0 |
| Wed 08 | 0 | 0.0 | 517 ms | 0 |
| Wed 10 | 0 | 0.0 | 668 ms | 0 |
| Wed 13 | 0 | 0.0 | 475 ms | 0 |
| Wed 15 | 0 | 0.0 | 550 ms | 0 |
| Wed 17 | 0 | 0.0 | 453 ms | 0 |
| Wed 19 | 0 | 0.0 | 454 ms | 0 |
| Wed 21 | 0 | 0.0 | 734 ms | 0 |
| Wed 23 | 0 | 0.0 | 828 ms | 0 |
| Thu 01 | 0 | 0.0 | 469 ms | 0 |
| Thu 03 | 0 | 0.0 | 503 ms | 0 |
| Thu 05 | 0 | 0.0 | 378 ms | 0 |
| Thu 08 | 0 | 0.0 | 441 ms | 0 |
| Thu 10 | 0 | 0.0 | 396 ms | 0 |
| Thu 12 | 0 | 0.0 | 498 ms | 0 |
| Thu 14 | 0 | 0.0 | 529 ms | 0 |
| Thu 16 | 0 | 0.0 | 302 ms | 0 |
| Thu 18 | 0 | 0.0 | 269 ms | 0 |
| Thu 20 | 0 | 0.0 | 438 ms | 0 |
| Thu 22 | 0 | 0.0 | 404 ms | 0 |
| Fri 00 | 0 | 0.0 | 570 ms | 0 |
| Fri 02 | 0 | 0.0 | 449 ms | 0 |
| Fri 04 | 0 | 0.0 | 290 ms | 0 |
| Fri 06 | 0 | 0.0 | 444 ms | 0 |
| Fri 08 | 0 | 0.0 | 315 ms | 0 |
| Fri 10 | 0 | 0.0 | 393 ms | 0 |
| Fri 12 | 0 | 0.0 | 521 ms | 0 |
| Fri 14 | 0 | 0.0 | 459 ms | 0 |
| Fri 17 | 0 | 0.0 | 535 ms | 0 |
| Fri 19 | 0 | 0.0 | 478 ms | 0 |
| Fri 21 | 0 | 0.0 | 507 ms | 0 |
| Fri 23 | 0 | 0.0 | 545 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Degreed yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Degreed goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Degreed alerts to Slack, Discord or a webhook — free.
Degreed, at degreed.com, is one of the AI services we monitor. It's time to rethink AI-powered learning. Degreed is your upskilling platform partner with end-to-end learning, targeted skill-building, & real-time data.
Degreed publishes an official status page at status.degreed.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 449 ms average, 290–545 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Degreed incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
449 ms on average over the last 24 hours (290–545 ms).
Yes, at https://status.degreed.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Degreed here at once, the problem is on Degreed's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Degreed. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.