Skip to main content
Prismic

Service Disruption

Major outage Lasted 0m · started · Prismic's page

Level
confirmed
Worst impact
Major outage
Down Index
30of 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 0m it lasted.

    Anything that failed between 2026-02-11 10:38 UTC and 2026-02-10 22:30 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 2

  1. investigating

    Prismic customers experienced difficulties logging in and accessing their repositories

    provider

  2. resolved

    **Incident Summary** On February 10, 2026, between approximately 10:15 PM and 11:30 PM CET, some Prismic customers experienced difficulties logging in and accessing their repositories. These issues were caused by a DNS resolution failure on [AWS CloudFront](https://health.aws.com/health/status), one of the infrastructure providers Prismic relies on. **What Happened** • AWS identified the root cause and progressively restored normal operations. • All Prismic services returned to full availability by late evening CET. • We identified gaps in our alerting that delayed our awareness of the issue. **What We Are Doing Next** To improve our response to similar events in the future, we are taking the following actions: • **Improving our alerting**: We are enhancing our monitoring to detect upstream infrastructure issues faster and more reliably. • **Better support readiness**: We are putting in place clearer escalation processes so our support team can assist customers more effectively during incidents. • **Faster communication**: We are improving our status page update process to ensure customers are informed promptly when an issue is identified. We apologize for the inconvenience and appreciate your patience. If you have any questions, please don't hesitate to reach out to our support team.

    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-64bda190e7

Is Prismic still down?

No, this incident was resolved 2026-02-10 22:30 UTC. For Prismic's live state, see https://down.guide/prismic.

How long did it last?

0m, from 2026-02-11 10:38 UTC to 2026-02-10 22:30 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.