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 31 min ago. Last stored result reached it in 246 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 520 ms | 0 |
| Nov 7 | 0 | 0.0 | 347 ms | 0 |
| Nov 7 | 0 | 0.0 | 284 ms | 0 |
| Nov 7 | 0 | 0.0 | 323 ms | 0 |
| Nov 8 | 0 | 0.0 | 303 ms | 0 |
| Nov 8 | 0 | 0.0 | 358 ms | 0 |
| Nov 8 | 0 | 0.0 | 346 ms | 0 |
| Nov 8 | 0 | 0.0 | 295 ms | 0 |
| Nov 9 | 0 | 0.0 | 368 ms | 0 |
| Nov 9 | 0 | 0.0 | 306 ms | 0 |
| Nov 9 | 0 | 0.0 | 359 ms | 0 |
| Nov 9 | 0 | 0.0 | 422 ms | 0 |
| Nov 10 | 0 | 0.0 | 341 ms | 0 |
| Nov 10 | 0 | 0.0 | 301 ms | 0 |
| Nov 10 | 0 | 0.0 | 347 ms | 0 |
| Nov 10 | 0 | 0.0 | 361 ms | 0 |
| Nov 11 | 0 | 0.0 | 277 ms | 0 |
| Nov 11 | 0 | 0.0 | 324 ms | 0 |
| Nov 11 | 0 | 0.0 | 300 ms | 0 |
| Nov 11 | 0 | 0.0 | 420 ms | 0 |
| Nov 12 | 0 | 0.0 | 420 ms | 0 |
| Nov 12 | 0 | 0.0 | 339 ms | 0 |
| Nov 12 | 0 | 0.0 | 357 ms | 0 |
| Nov 12 | 0 | 0.0 | 384 ms | 0 |
| Nov 13 | 0 | 0.0 | 428 ms | 0 |
| Nov 13 | 0 | 0.0 | 387 ms | 0 |
| Nov 13 | 0 | 0.0 | 312 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for paperguide 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 paperguide goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send paperguide alerts to Slack, Discord or a webhook — free.
paperguide is listed in our AI category and checked at paperguide.ai. AI-native platform for literature reviews and auditable systematic reviews, with reference management and research agents.
paperguide publishes an official status page at status.paperguide.ai; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 379 ms average, 246–613 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public paperguide incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
379 ms on average over the last 24 hours (246–613 ms).
Yes, at https://status.paperguide.ai.
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 paperguide here at once, the problem is on paperguide'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 paperguide. 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.