27 Prismic incidents · 2025年4月 — official updates, affected components, duration and resolution details.
我们正在调查一个影响API和编辑的问题。 我们的小组正在积极努力查明根源,并将在获得更多信息后立即提供最新情况。 谢谢你的耐心!
我们确定了影响API和编辑的问题的原因。 我们的小组目前正在落实一项固定措施,我们期望很快恢复。 我们赞赏你的耐心,并将很快进一步介绍最新情况.
已经执行了一项措施,我们正在监测局势,以确保全面恢复。 谢谢你的耐心!
影响Api和编辑的问题已经完全解决. 所有系统现已投入使用。 我们为这期间造成的任何不便表示歉意并感谢你的耐心。 如遇到进一步的问题,请与[支助中心]联系。 谢谢你的支持
自动翻译自官方事件更新。
We are currently investigating an issue affecting Publication system . Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. Thank you for your patience!
A fix has been implemented, and we are currently monitoring the situation to ensure full recovery. Thank you for your patience!
The issue affecting publication system has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Center]. 🚀 **Thank you for your support!**
We are currently investigating an issue affecting Prismic Writing room. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. Thank you for your patience!
A fix has been implemented, and we are currently monitoring the situation to ensure full recovery. Thank you for your patience!
The issue affecting Prismic Writing Room has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Center]. 🚀 **Thank you for your support!**
We are currently investigating an issue affecting authentication. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. Thank you for your patience!
We have identified the cause of the issue affecting authentication. An upstream provider we rely on is currently experiencing downtime, which is impacting our services as well. 🔹 **Issue:** Users may be unable to sign in or authenticate successfully. 🔹 **Impact:** Authentication-related actions across the platform are unavailable for some users. We appreciate your patience and will share further updates soon.
The issue affecting an upstream provider has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Center]. 🚀 **Thank you for your support!**
We are currently investigating an issue affecting access to Prismic. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. 🚀 **Next Update Expected:** As soon as we have more details. Thank you for your patience!
A fix has been implemented, and we are currently monitoring the situation to ensure full recovery. Thank you for your patience!
The issue affecting the dashboard has been fully resolved. All systems are now operational. 🚀 **Thank you for your support!**
We are investigating an issue affecting the Media Library, which currently returns an error screen. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. 🚀 **Next Update Expected:** As soon as we have more details. Thank you for your patience!
We have identified the cause of the issue affecting media library
A fix has been implemented, and we are currently monitoring the situation to ensure full recovery. Thank you for your patience!
The issue affecting media-library has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Center]. 🚀 **Thank you for your support!**
We are currently investigating an issue affecting the creation of repositories for newer users. Reports indicate users are getting stuck at the onboarding page. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. 🚀 **Next Update Expected:** As soon as we have more details. Thank you for your patience!
**New users are encountering issues when creating repositories** We are aware of an issue affecting billing subscription data for a subset of repositories. Some users may encounter errors when accessing billing information. We have identified the likely cause and are working on a fix. Further updates will follow as our investigation progresses. 🔹 **Issue:** Some repositories are experiencing errors when loading billing subscription data We appreciate your patience and will share further updates soon.
A fix has been implemented, and we are currently monitoring the situation to ensure full recovery. 🚀 **Next Update Expected:** 15-20 minites Thank you for your patience!
The issue affecting repository creation has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Center]. 🚀 **Thank you for your support!**
We are currently investigating an issue affecting Media Library. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. Thank you for your patience!
We have identified the cause of the issue affecting Media Library. Our team is currently implementing a fix, and we expect recovery shortly. We appreciate your patience and will share further updates soon.
A fix has been implemented, and we are currently monitoring the situation to ensure full recovery. Thank you for your patience!
The issue affecting Media Library has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Center]. 🚀 **Thank you for your support!**
We are currently investigating an issue affecting the Media Library. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. 🚀 **Next Update Expected:** As soon as we have more details. Thank you for your patience!
The issue affecting the Media Library has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact Support via our [Help Center](https://prismic.io/docs/help-center). 🚀 **Thank you for your support!**
We are currently investigating an issue affecting the Media Library. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. 🚀 **Next Update Expected:** As soon as we have more details. Thank you for your patience!
We are currently investigating an issue affecting the Media Library. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. 🚀 **Next Update Expected:** As soon as possible. Thank you for your patience!
A fix has been implemented, and we are currently monitoring the situation to ensure full recovery. Thank you for your patience!
The issue affecting Media Library has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Center]. 🚀 **Thank you for your support!**
We are currently investigating an issue affecting new sign-ups. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. Thank you for your patience!
The issue affecting sign-ups has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Center]. 🚀 **Thank you for your support!**
Prismic customers experienced difficulties logging in and accessing their repositories
**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.
We are currently investigating an issue affecting the feature oEmbed in our Page Builder. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. Thank you for your patience!
A fix has been implemented, and we are currently monitoring the situation to ensure full recovery. Thank you for your patience!
The issue affecting oEmbed feature has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Center]. 🚀 **Thank you for your support!**
We are currently experiencing an issue with our provider affecting the **Real Time Collaboration** feature in our Editor. In the meantime, you can continue working and **save your document manually**. We are actively monitoring the provider’s status and will provide updates as soon as the issue is resolved. Thank you for your patience.
The issue affecting **Real Time Collaboration** has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Center]. 🚀 **Thank you for your support!**
We are currently investigating an issue affecting some users trying to authenticate via SSO and GitHub. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available.
A fix has been implemented, and we are currently monitoring the situation to ensure full recovery. Thank you for your patience!
The issue affecting new users authenticating via SSO and GitHub has now been fully resolved, and all systems are operating normally. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact our Support. 🚀 Thank you for your support!
We are currently observing an **increase in error rates** affecting our **Content API**. Some requests may fail or experience delays. The issue originates from an 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.
We have **applied changes to our infrastructure** that have **mitigated the issue** affecting the **Content API**. Error rates have **dropped significantly**, and most operations are now **functioning normally**. Our team continues to **monitor system behavior** to ensure full stability before marking the incident as resolved.
The issue affecting Content API has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Contact]. 🚀 **Thank you for your support!**
We are currently experiencing issues with **webhook triggers** and **synchronization of push items for integration fields**. These features may not function reliably at this time. The issue originates from our **cloud provider**, and we continue to monitor their recovery while implementing mitigation measures on our side.
Both **Webhooks** and **push items for Integration Fields** remain in a **degraded state**. However, we are observing **partial recovery** some webhooks are now triggering successfully, and some items are becoming available again. Our team continues to monitor the situation and work toward full restoration of normal operations.
**Webhooks** are now **fully functional** and operating normally. However, **Integration Fields** are still experiencing **degraded performance**, which may cause delays or incomplete synchronization for some items. Our team is actively working to **restore full functionality** as soon as possible and continues to monitor the situation closely.
The issue affecting Webhooks and Integration Fields has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Contact]. 🚀 **Thank you for your support!**
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.
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.
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.
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.
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.
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.
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!**
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.
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.
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.
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!**
We are currently investigating an issue affecting the Page Builder. This issue is due to an incident on one of our key provider, we are working toward mitigation :rocket: **Next Update Expected:** Mitigation of provider incident Thank you for your patience!
A fix has been implemented, and we are currently monitoring the situation to ensure full recovery. Thank you for your patience!
The issue seems to be resolved for all users. We are still on monitoring stage, and will be for the next hour, to ensure there is no regression.
The issue has been fully resolved. All systems have been operational from 7am CET. We have been monitoring the situation closely and we are now in a position to resolve the incident. The root cause has been the failing of one of our external proiders. We have taken the necessary preventative steps to avoid a similar situation in the future.
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!
When the new content relationship feature used in combination with our route resolver it can cause the API to fail and return 500 errors.
Root cause identified - a fix is being pushed to production.
The issue affecting the content service API has been fully resolved. All systems are now operational.
