Final update
Following our recent update on the service interruption, we want to provide you with more details about the incident and our ongoing efforts to ensure system stability.
Incident Overview:
As we previously communicated, the outage was a result of a change implemented by our service provider, AWS. Specifically, our Lambda serverless infrastructure was automatically upgraded to a new Node.js version. This unexpected upgrade introduced a breaking change in the way HTTP headers were managed, leading to a series of errors.
Impact and Response:
The change initiated a snowball effect, generating errors that impacted our services. Our response was to roll back our lambda serverless infrastructure to the previous stable version. This action successfully resolved the issue, restoring normal service operations.
Current Status and Monitoring:
We have returned to full operational status and are carefully monitoring the recovery of our infrastructure. Our team is actively working to ensure that all systems remain stable and performant.
Future Safeguards:
To prevent a recurrence of this issue, we are taking corrective measures, including:
- We will review our change management protocols with our service providers.
- We already implemented stricter controls for automatic updates.
We understand the critical importance of our services to your operations and are deeply committed to maintaining the highest standards of reliability and performance. We apologize for the disruption caused and appreciate your understanding and continued trust in Prismic.
If you have any specific question about your repo, please reach out privately in the support portal 