User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Education
semanticscholar.org · Education
Is Semantic Scholar API down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → semanticscholar.org—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 98 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 100 ms | 0 |
| Mon 22 | 0 | 0.0 | 71 ms | 0 |
| Tue 01 | 0 | 0.0 | 110 ms | 0 |
| Tue 03 | 0 | 0.0 | 184 ms | 0 |
| Tue 05 | 0 | 0.0 | 86 ms | 0 |
| Tue 07 | 0 | 0.0 | 90 ms | 0 |
| Tue 09 | 0 | 0.0 | 76 ms | 0 |
| Tue 11 | 0 | 0.0 | 233 ms | 0 |
| Tue 13 | 0 | 0.0 | 138 ms | 0 |
| Tue 16 | 0 | 0.0 | 109 ms | 0 |
| Tue 18 | 0 | 0.0 | 91 ms | 0 |
| Tue 20 | 0 | 0.0 | 125 ms | 0 |
| Tue 22 | 0 | 0.0 | 82 ms | 0 |
| Wed 01 | 0 | 0.0 | 105 ms | 0 |
| Wed 03 | 0 | 0.0 | 223 ms | 0 |
| Wed 05 | 0 | 0.0 | 90 ms | 0 |
| Wed 07 | 0 | 0.0 | 132 ms | 0 |
| Wed 10 | 0 | 0.0 | 86 ms | 0 |
| Wed 12 | 0 | 0.0 | 99 ms | 0 |
| Wed 14 | 0 | 0.0 | 106 ms | 0 |
| Wed 16 | 0 | 0.0 | 92 ms | 0 |
| Wed 18 | 0 | 0.0 | 119 ms | 0 |
| Wed 20 | 0 | 0.0 | 195 ms | 0 |
| Wed 23 | 0 | 0.0 | 199 ms | 0 |
| Thu 01 | 0 | 0.0 | 122 ms | 0 |
| Thu 03 | 0 | 0.0 | 127 ms | 0 |
| Thu 05 | 0 | 0.0 | 158 ms | 0 |
| Thu 07 | 0 | 0.0 | 88 ms | 0 |
| Thu 09 | 0 | 0.0 | 57 ms | 0 |
| Thu 11 | 0 | 0.0 | 96 ms | 0 |
| Thu 13 | 0 | 0.0 | 173 ms | 0 |
| Thu 15 | 0 | 0.0 | 80 ms | 0 |
| Thu 17 | 0 | 0.0 | 110 ms | 0 |
| Thu 19 | 0 | 0.0 | 184 ms | 0 |
| Thu 21 | 0 | 0.0 | 208 ms | 0 |
| Thu 23 | 0 | 0.0 | 104 ms | 0 |
| Fri 00 | 0 | 0.0 | 110 ms | 0 |
| Fri 02 | 0 | 0.0 | 86 ms | 0 |
| Fri 04 | 0 | 0.0 | 89 ms | 0 |
| Fri 06 | 0 | 0.0 | 164 ms | 0 |
| Fri 08 | 0 | 0.0 | 89 ms | 0 |
| Fri 10 | 0 | 0.0 | 96 ms | 0 |
| Fri 12 | 0 | 0.0 | 73 ms | 0 |
| Fri 14 | 0 | 0.0 | 83 ms | 0 |
| Fri 16 | 0 | 0.0 | 105 ms | 0 |
| Fri 18 | 0 | 0.0 | 95 ms | 0 |
| Fri 19 | 0 | 0.0 | 179 ms | 0 |
| Fri 21 | 0 | 0.0 | 98 ms | 0 |
Reliability
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.
Embed this status: free live Semantic Scholar API badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Semantic Scholar API yet. Outages of 10 minutes or more get their own page here.
Having trouble with Semantic Scholar API?
One report per service every 10 minutes from this network. No account.
Follow Semantic Scholar API
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.
About Semantic Scholar API
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: 105 ms average, 73–179 ms range across 15 successful checks.
Questions
Is Semantic Scholar API down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Semantic Scholar API last down?
We have not recorded a public Semantic Scholar API incident since monitoring began 8 days ago.
What is Semantic Scholar API's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Semantic Scholar API respond?
105 ms on average over the last 24 hours (73–179 ms).
Does Semantic Scholar API have an official status page?
Yes, at https://status.api.semanticscholar.org.
Semantic Scholar API not working for me but the status is fine. What now?
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.