User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Education
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 19 min ago. Last stored result reached it in 139 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 82 ms | 0 |
| Mon 22 | 0 | 0.0 | 1778 ms | 0 |
| Tue 00 | 0 | 0.0 | 474 ms | 0 |
| Tue 03 | 0 | 0.0 | 108 ms | 0 |
| Tue 05 | 0 | 0.0 | 242 ms | 0 |
| Tue 07 | 0 | 0.0 | 198 ms | 0 |
| Tue 09 | 0 | 0.0 | 292 ms | 0 |
| Tue 11 | 0 | 0.0 | 87 ms | 0 |
| Tue 13 | 0 | 0.0 | 582 ms | 0 |
| Tue 16 | 0 | 0.0 | 205 ms | 0 |
| Tue 18 | 0 | 0.0 | 168 ms | 0 |
| Tue 20 | 0 | 0.0 | 213 ms | 0 |
| Tue 22 | 0 | 0.0 | 110 ms | 0 |
| Wed 01 | 0 | 0.0 | 110 ms | 0 |
| Wed 03 | 0 | 0.0 | 107 ms | 0 |
| Wed 05 | 0 | 0.0 | 276 ms | 0 |
| Wed 07 | 0 | 0.0 | 209 ms | 0 |
| Wed 10 | 0 | 0.0 | 254 ms | 0 |
| Wed 12 | 0 | 0.0 | 884 ms | 0 |
| Wed 14 | 0 | 0.0 | 284 ms | 0 |
| Wed 16 | 0 | 0.0 | 158 ms | 0 |
| Wed 18 | 0 | 0.0 | 203 ms | 0 |
| Wed 20 | 0 | 0.0 | 687 ms | 0 |
| Wed 23 | 0 | 0.0 | 168 ms | 0 |
| Thu 01 | 0 | 0.0 | 312 ms | 0 |
| Thu 03 | 0 | 0.0 | 128 ms | 0 |
| Thu 05 | 0 | 0.0 | 132 ms | 0 |
| Thu 07 | 0 | 0.0 | 76 ms | 0 |
| Thu 09 | 0 | 0.0 | 284 ms | 0 |
| Thu 11 | 0 | 0.0 | 82 ms | 0 |
| Thu 13 | 0 | 0.0 | 315 ms | 0 |
| Thu 15 | 0 | 0.0 | 248 ms | 0 |
| Thu 17 | 0 | 0.0 | 268 ms | 0 |
| Thu 19 | 0 | 0.0 | 354 ms | 0 |
| Thu 21 | 0 | 0.0 | 265 ms | 0 |
| Thu 22 | 0 | 0.0 | 157 ms | 0 |
| Fri 00 | 0 | 0.0 | 87 ms | 0 |
| Fri 02 | 0 | 0.0 | 191 ms | 0 |
| Fri 04 | 0 | 0.0 | 89 ms | 0 |
| Fri 06 | 0 | 0.0 | 237 ms | 0 |
| Fri 08 | 0 | 0.0 | 239 ms | 0 |
| Fri 10 | 0 | 0.0 | 465 ms | 0 |
| Fri 12 | 0 | 0.0 | 82 ms | 0 |
| Fri 14 | 0 | 0.0 | 242 ms | 0 |
| Fri 16 | 0 | 0.0 | 275 ms | 0 |
| Fri 17 | 0 | 0.0 | 90 ms | 0 |
| Fri 19 | 0 | 0.0 | 139 ms | 0 |
| Fri 21 | 0 | 0.0 | 277 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 OpenAlex 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 OpenAlex goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send OpenAlex alerts to Slack, Discord or a webhook — free.
We track OpenAlex (openalex.org) as part of the Education group. OpenAlex indexes half a billion scholarly works, with their authors, institutions, sources and topics, and makes them free to search, analyze and reuse through our web app, API and bulk download.
OpenAlex publishes an official status page at status.openalex.org; when we can read it, its incident level is folded into the status shown here.
Common problems for education services: learning management systems and student portals slowing down around assignment deadlines, exams and registration.
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: 205 ms average, 82–465 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public OpenAlex incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
205 ms on average over the last 24 hours (82–465 ms).
Yes, at https://status.openalex.org.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For education services, watch for learning management systems and student portals slowing down around assignment deadlines, exams and registration. If many people report OpenAlex here at once, the problem is on OpenAlex'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 OpenAlex. 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.