User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Education
semanticscholar.org · 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 53 min ago. Last stored result reached it in 96 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:30 | 0 | 0.0 | 173 ms | 0 |
| 15:45 | 0 | 0.0 | 80 ms | 0 |
| 17:45 | 0 | 0.0 | 110 ms | 0 |
| 19:45 | 0 | 0.0 | 184 ms | 0 |
| 21:45 | 0 | 0.0 | 208 ms | 0 |
| 23:45 | 0 | 0.0 | 104 ms | 0 |
| 00:00 | 0 | 0.0 | 127 ms | 0 |
| 00:15 | 0 | 0.0 | 93 ms | 0 |
| 02:15 | 0 | 0.0 | 86 ms | 0 |
| 04:30 | 0 | 0.0 | 89 ms | 0 |
| 06:30 | 0 | 0.0 | 164 ms | 0 |
| 08:45 | 0 | 0.0 | 89 ms | 0 |
| 10:45 | 0 | 0.0 | 96 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 Semantic Scholar API 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 Semantic Scholar API goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Semantic Scholar API alerts to Slack, Discord or a webhook — free.
Semantic Scholar API is listed in our Education category and checked at semanticscholar.org. Semantic Scholar uses groundbreaking AI and engineering to understand the semantics of scientific literature to help Scholars discover relevant research.
Semantic Scholar API publishes an official status page at status.api.semanticscholar.org; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 123 ms average, 80–208 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Semantic Scholar API incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
123 ms on average over the last 24 hours (80–208 ms).
Yes, at https://status.api.semanticscholar.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 Semantic Scholar API here at once, the problem is on Semantic Scholar API'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 Semantic Scholar API. 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.