Increased Error Rates and Latencies

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 2h 31m it lasted.

  Anything that failed between 2025-10-20 07:30 UTC and 2025-10-20 10:02 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 12

1. investigatingOct 20, 2025, 7:30 AM UTC

   We are currently investigating an issue affecting all our services. The disruption appears to be related to an ongoing incident with our cloud provider. Our team is actively monitoring the situation and working closely with the provider to identify the root cause and mitigate the impact. We will provide updates as soon as more information becomes available.

   provider

2. identifiedOct 20, 2025, 7:35 AM UTC

   We are currently experiencing an issue affecting the publication of new documents. The root cause has been identified as an ongoing incident with our cloud provider, which is impacting our services. Our team is actively monitoring the situation and exploring possible mitigation options to minimize disruption while the provider works on a resolution.

   provider

3. identifiedOct 20, 2025, 7:56 AM UTC

   We are currently experiencing a major outage affecting our platform. Users are unable to connect or perform any actions at this time. The issue has been traced to an ongoing incident with our cloud provider, which is impacting multiple services. Our team is actively monitoring the situation and exploring all possible mitigation steps while the provider works toward a resolution.

   provider

4. identifiedOct 20, 2025, 8:26 AM UTC

   We are currently experiencing partial issues affecting our Content API. Some requests may fail or experience degraded performance. Our team is actively investigating the problem, which is linked to an ongoing incident with our cloud provider, and we are working to mitigate the impact as quickly as possible.

   provider

5. identifiedOct 20, 2025, 8:28 AM UTC

   We are currently experiencing issues where **Slice Machine** and the **Migration API** are unable to update content. These components are also affected by the ongoing incident with our cloud provider, which is impacting several of our services. Our team is actively monitoring the situation and working to mitigate the impact while the provider works toward a resolution.

   provider

6. monitoringOct 20, 2025, 9:35 AM UTC

   We are observing signs of recovery from our cloud provider, and **all our services**. Our team is closely monitoring the situation to ensure full stability and confirm that all systems are performing as expected.

   provider

7. resolvedOct 20, 2025, 10:02 AM UTC

   The issue affecting our services has been fully resolved, and all systems are now operational. 🔹 **Root Cause:** The incident was caused by an issue from our cloud provider, which has now been resolved. We apologize for any inconvenience caused and sincerely appreciate your patience during this period. If you experience any further issues, please contact our support team. 🚀 **Thank you for your continued support!**

   provider

8. investigatingOct 20, 2025, 3:22 PM UTC

   We are currently observing an **increase in error rates** across our platform. This is causing **partial outages** affecting the **publication of new documents** and the **Content API**. Our team is actively investigating the issue to identify the root cause and implement mitigation measures as quickly as possible.

   provider

9. monitoringOct 20, 2025, 5:14 PM UTC

   To protect our **users and data**, we have temporarily **restricted access to the Page Builder, Migration API, and Slice Machine** to prevent further errors while the issue is being investigated. Our team is **closely monitoring the situation** and working with our **cloud provider** to restore full functionality as soon as possible.

   provider

10. monitoringOct 20, 2025, 5:20 PM UTC

    To protect our **users and data**, we have temporarily **restricted access to the Page Builder, Migration API, and Slice Machine** to prevent further errors while the issue is being investigated. Our team is **closely monitoring the situation** and working with our **cloud provider** to restore full functionality as soon as possible.

    provider

11. monitoringOct 20, 2025, 7:27 PM UTC

    We are seeing **signs of recovery** on our side and are **progressively reopening the Page Builder and other services**. **Prismic platform** is gradually returning to normal operation. Our team will continue to **monitor the situation closely** to ensure full stability. Thank you for your continued patience and support.

    provider

12. resolvedOct 20, 2025, 8:02 PM UTC

    The issue affecting **Prismic Platform** has been **fully resolved**, and all systems are now **operational**. We sincerely apologize for any inconvenience caused and greatly appreciate your patience during this time. If you experience any further issues, please contact our support team at **[Support center]**. 🚀 **Thank you for your continued support!**

    provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.