- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 25of 100
What to do
Check whether your product depends on Prismic. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 26m it lasted.
Anything that failed between 2025-06-27 17:42 UTC and 2025-06-27 18:08 UTC may need a replay.Subscribe to Prismic's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=prismic works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Prismic 4
- investigating
We are currently investigating an issue affecting content service API. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. :rocket: **Next Update Expected:** 30 minutes Thank you for your patience!
provider
- investigating
When the new content relationship feature used in combination with our route resolver it can cause the API to fail and return 500 errors.
provider
- investigating
Root cause identified - a fix is being pushed to production.
provider
- resolved
The issue affecting the content service API has been fully resolved. All systems are now operational.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-b7014b2115
Is Prismic still down?
No, this incident was resolved 2025-06-27 18:08 UTC. For Prismic's live state, see https://down.guide/prismic.
How long did it last?
26m, from 2025-06-27 17:42 UTC to 2025-06-27 18:08 UTC, by the times Prismic posted.
What caused it?
Prismic hasn't published a root cause. If it does, it shows here.
Where does this come from?
Prismic's official status page, https://status.prismic.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.