User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Correction: On Nov 10, 2026 we retracted an incident report for Elicit published in error on Nov 8, 2026. No outage occurred. Read the retraction →
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 309 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 09:30 | 0 | 0.0 | 172 ms | 0 |
| 11:30 | 0 | 0.0 | 204 ms | 0 |
| 13:30 | 0 | 0.0 | 222 ms | 0 |
| 15:30 | 0 | 0.0 | 347 ms | 0 |
| 17:45 | 0 | 0.0 | 405 ms | 0 |
| 19:45 | 0 | 0.0 | 189 ms | 0 |
| 21:45 | 0 | 0.0 | 322 ms | 0 |
| 23:45 | 0 | 0.0 | 270 ms | 0 |
| 02:00 | 0 | 0.0 | 281 ms | 0 |
| 04:00 | 0 | 0.0 | 130 ms | 0 |
| 06:00 | 0 | 0.0 | 309 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 Elicit 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 Elicit goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Elicit alerts to Slack, Discord or a webhook — free.
We track Elicit (elicit.com) as part of the Productivity group. Elicit helps you synthesize evidence, understand the landscape, design programs and experiments, draft proposals, and weigh tradeoffs. Trusted by over 7 million researchers and 8 of the top 20 pharmaceutical companies
Elicit publishes an official status page at status.elicit.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 259 ms average, 130–405 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 Elicit incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
259 ms on average over the last 24 hours (130–405 ms).
Yes, at https://status.elicit.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Elicit here at once, the problem is on Elicit'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 Elicit. 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.