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 50 min ago. Last stored result reached it in 230 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 267 ms | 0 |
| Tue 04 | 0 | 0.0 | 254 ms | 0 |
| Tue 06 | 0 | 0.0 | 311 ms | 0 |
| Tue 09 | 0 | 0.0 | 206 ms | 0 |
| Tue 11 | 0 | 0.0 | 203 ms | 0 |
| Tue 13 | 0 | 0.0 | 301 ms | 0 |
| Tue 15 | 0 | 0.0 | 274 ms | 0 |
| Tue 17 | 0 | 0.0 | 172 ms | 0 |
| Tue 20 | 0 | 0.0 | 248 ms | 0 |
| Tue 22 | 0 | 0.0 | 312 ms | 0 |
| Wed 00 | 0 | 0.0 | 259 ms | 0 |
| Wed 02 | 0 | 0.0 | 162 ms | 0 |
| Wed 05 | 0 | 0.0 | 234 ms | 0 |
| Wed 07 | 0 | 0.0 | 338 ms | 0 |
| Wed 09 | 0 | 0.0 | 300 ms | 0 |
| Wed 11 | 0 | 0.0 | 219 ms | 0 |
| Wed 13 | 0 | 0.0 | 275 ms | 0 |
| Wed 16 | 0 | 0.0 | 275 ms | 0 |
| Wed 18 | 0 | 0.0 | 360 ms | 0 |
| Wed 20 | 0 | 0.0 | 256 ms | 0 |
| Wed 22 | 0 | 0.0 | 155 ms | 0 |
| Wed 23 | 0 | 0.0 | 165 ms | 0 |
| Thu 01 | 0 | 0.0 | 290 ms | 0 |
| Thu 03 | 0 | 0.0 | 174 ms | 0 |
| Thu 05 | 0 | 0.0 | 231 ms | 0 |
| Thu 07 | 0 | 0.0 | 253 ms | 0 |
| Thu 09 | 0 | 0.0 | 198 ms | 0 |
| Thu 11 | 0 | 0.0 | 272 ms | 0 |
| Thu 14 | 0 | 0.0 | 255 ms | 0 |
| Thu 16 | 0 | 0.0 | 249 ms | 0 |
| Thu 18 | 0 | 0.0 | 150 ms | 0 |
| Thu 20 | 0 | 0.0 | 268 ms | 0 |
| Thu 22 | 0 | 0.0 | 199 ms | 0 |
| Fri 00 | 0 | 0.0 | 174 ms | 0 |
| Fri 02 | 0 | 0.0 | 195 ms | 0 |
| Fri 04 | 0 | 0.0 | 403 ms | 0 |
| Fri 06 | 0 | 0.0 | 234 ms | 0 |
| Fri 08 | 0 | 0.0 | 234 ms | 0 |
| Fri 10 | 0 | 0.0 | 176 ms | 0 |
| Fri 11 | 0 | 0.0 | 246 ms | 0 |
| Fri 12 | 0 | 0.0 | 259 ms | 0 |
| Fri 14 | 0 | 0.0 | 271 ms | 0 |
| Fri 15 | 0 | 0.0 | 320 ms | 0 |
| Fri 17 | 0 | 0.0 | 253 ms | 0 |
| Fri 18 | 0 | 0.0 | 316 ms | 0 |
| Fri 19 | 0 | 0.0 | 187 ms | 0 |
| Fri 21 | 0 | 0.0 | 388 ms | 0 |
| Fri 23 | 0 | 0.0 | 230 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 Paragon 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 Paragon goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Paragon alerts to Slack, Discord or a webhook — free.
We track Paragon (useparagon.com) as part of the AI group. Integration infrastructure for AI agents and SaaS products. Connect to the tools your customers use for tool-calling and RAG ingestion, and ship 10x faster.
Paragon publishes an official status page at status.useparagon.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 262 ms average, 176–403 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Paragon incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
262 ms on average over the last 24 hours (176–403 ms).
Yes, at https://status.useparagon.com.
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 Paragon here at once, the problem is on Paragon'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 Paragon. 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.