User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
prismic.io · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 4473 ms · 2 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 05:15 | 0 | 0.0 | 1426 ms | 0 |
| 05:30 | 0 | 0.0 | 783 ms | 0 |
| 05:45 | 0 | 0.0 | 1026 ms | 0 |
| 06:00 | 0 | 0.0 | 446 ms | 0 |
| 06:15 | 0 | 0.0 | 776 ms | 0 |
| 06:30 | 0 | 0.0 | 1453 ms | 0 |
| 06:45 | 0 | 0.0 | 1203 ms | 0 |
| 07:00 | 0 | 0.0 | 164 ms | 0 |
| 07:15 | 0 | 0.0 | 1298 ms | 0 |
| 07:30 | 0 | 0.0 | 734 ms | 0 |
| 07:45 | 0 | 0.0 | 447 ms | 0 |
| 08:00 | 0 | 0.0 | 928 ms | 0 |
| 08:15 | 0 | 0.0 | 219 ms | 0 |
| 08:30 | 0 | 0.0 | 1462 ms | 0 |
| 08:45 | 0 | 0.0 | 1114 ms | 0 |
| 09:00 | 0 | 0.0 | 147 ms | 0 |
| 09:15 | 0 | 0.0 | 1193 ms | 0 |
| 09:30 | 0 | 0.0 | 539 ms | 0 |
| 09:45 | 0 | 0.0 | 669 ms | 0 |
| 10:00 | 0 | 0.0 | 632 ms | 0 |
| 10:15 | 0 | 0.0 | 790 ms | 0 |
| 10:30 | 0 | 0.0 | 425 ms | 0 |
| 10:45 | 0 | 0.0 | 606 ms | 0 |
| 11:00 | 0 | 0.0 | 630 ms | 0 |
| 11:15 | 0 | 0.0 | 157 ms | 0 |
| 11:30 | 0 | 0.0 | 528 ms | 0 |
| 11:45 | 0 | 0.0 | 424 ms | 0 |
| 12:00 | 0 | 0.0 | 100 ms | 0 |
| 12:15 | 0 | 0.0 | 688 ms | 0 |
| 12:30 | 0 | 0.0 | 1329 ms | 0 |
| 12:45 | 0 | 0.0 | 689 ms | 0 |
| 13:00 | 0 | 0.0 | 549 ms | 0 |
| 13:15 | 0 | 0.0 | 494 ms | 0 |
| 13:30 | 0 | 0.0 | 1888 ms | 0 |
| 13:45 | 0 | 0.0 | 1341 ms | 0 |
| 14:00 | 0 | 0.0 | 1578 ms | 0 |
| 14:15 | 0 | 0.0 | 1151 ms | 0 |
| 14:30 | 0 | 0.0 | 1114 ms | 0 |
| 14:45 | 0 | 0.0 | 1358 ms | 0 |
| 15:00 | 0 | 0.0 | 3051 ms | 0 |
| 15:15 | 0 | 0.0 | 1408 ms | 0 |
| 15:30 | 0 | 0.0 | 553 ms | 0 |
| 15:45 | 0 | 0.0 | 232 ms | 0 |
| 16:00 | 0 | 0.0 | 1167 ms | 0 |
| 16:15 | 0 | 0.0 | 505 ms | 0 |
| 16:30 | 0 | 0.0 | 1968 ms | 0 |
| 16:45 | 0 | 0.0 | 708 ms | 0 |
| 17:00 | 0 | 0.0 | 4473 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Prismic 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 Prismic goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Prismic alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Prismic is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Prismic's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.