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 1 hr ago. Last stored result reached it in 113 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 295 ms | 0 |
| Tue 00 | 0 | 0.0 | 453 ms | 0 |
| Tue 02 | 0 | 0.0 | 420 ms | 0 |
| Tue 05 | 0 | 0.0 | 467 ms | 0 |
| Tue 07 | 0 | 0.0 | 335 ms | 0 |
| Tue 09 | 0 | 0.0 | 298 ms | 0 |
| Tue 11 | 0 | 0.0 | 143 ms | 0 |
| Tue 13 | 0 | 0.0 | 247 ms | 0 |
| Tue 15 | 0 | 0.0 | 250 ms | 0 |
| Tue 18 | 0 | 0.0 | 266 ms | 0 |
| Tue 20 | 0 | 0.0 | 129 ms | 0 |
| Tue 22 | 0 | 0.0 | 77 ms | 0 |
| Wed 00 | 0 | 0.0 | 153 ms | 0 |
| Wed 03 | 0 | 0.0 | 141 ms | 0 |
| Wed 05 | 0 | 0.0 | 330 ms | 0 |
| Wed 07 | 0 | 0.0 | 301 ms | 0 |
| Wed 09 | 0 | 0.0 | 290 ms | 0 |
| Wed 12 | 0 | 0.0 | 336 ms | 0 |
| Wed 14 | 0 | 0.0 | 181 ms | 0 |
| Wed 16 | 0 | 0.0 | 140 ms | 0 |
| Wed 18 | 0 | 0.0 | 233 ms | 0 |
| Wed 20 | 0 | 0.0 | 421 ms | 0 |
| Wed 22 | 0 | 0.0 | 127 ms | 0 |
| Thu 01 | 0 | 0.0 | 188 ms | 0 |
| Thu 03 | 0 | 0.0 | 248 ms | 0 |
| Thu 05 | 0 | 0.0 | 136 ms | 0 |
| Thu 07 | 0 | 0.0 | 244 ms | 0 |
| Thu 09 | 0 | 0.0 | 119 ms | 0 |
| Thu 11 | 0 | 0.0 | 178 ms | 0 |
| Thu 13 | 0 | 0.0 | 393 ms | 0 |
| Thu 15 | 0 | 0.0 | 244 ms | 0 |
| Thu 17 | 0 | 0.0 | 322 ms | 0 |
| Thu 19 | 0 | 0.0 | 112 ms | 0 |
| Thu 21 | 0 | 0.0 | 250 ms | 0 |
| Thu 23 | 0 | 0.0 | 246 ms | 0 |
| Fri 01 | 0 | 0.0 | 400 ms | 0 |
| Fri 03 | 0 | 0.0 | 235 ms | 0 |
| Fri 06 | 0 | 0.0 | 154 ms | 0 |
| Fri 08 | 0 | 0.0 | 315 ms | 0 |
| Fri 10 | 0 | 0.0 | 249 ms | 0 |
| Fri 12 | 0 | 0.0 | 63 ms | 0 |
| Fri 14 | 0 | 0.0 | 156 ms | 0 |
| Fri 16 | 0 | 0.0 | 132 ms | 0 |
| Fri 17 | 0 | 0.0 | 256 ms | 0 |
| Fri 19 | 0 | 0.0 | 292 ms | 0 |
| Fri 20 | 0 | 0.0 | 118 ms | 0 |
| Fri 22 | 0 | 0.0 | 261 ms | 0 |
| Fri 23 | 0 | 0.0 | 113 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 Pangea 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 Pangea goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pangea alerts to Slack, Discord or a webhook — free.
We track Pangea (pangea.cloud) as part of the AI group. Pangea empowers organizations to ship secure AI applications quickly with the industry's broadest set of AI security guardrails that can be added with just a few lines of code.
Pangea publishes an official status page at status.pangea.cloud; 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: 220 ms average, 63–488 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Pangea incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
220 ms on average over the last 24 hours (63–488 ms).
Yes, at https://status.pangea.cloud.
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 Pangea here at once, the problem is on Pangea'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 Pangea. 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.