ContentfulCustomers experiencing issues with Workflows
The issue has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The issue has been resolved.
Resolved
Vercel confirmed we have not been impacted, but we have still taken the necessary steps and rotated credentials in environment variables that were not marked as “sensitive” as mentioned in the security bulletin.
Resolved
We want to share an update on a recent automation issue, including what happened, how it was resolved, and the steps we’ve taken to prevent it from happening again. **Date/Time:** April 21, 2026, **1:40 PM – 4:39 PM PDT** **Duration:** **2 hours 59 minutes** ### Customer Impact During this window, customers using Microsoft Office365 were unable to retrieve interviewer availability or schedule interviews. Existing data was not lost, but new scheduling actions failed until service was restored. ### Root Cause An internal encryption key rotation was completed for several services, but a related dependency used by the calendar service was not updated. As a result, the calendar service was unable to read newly issued Microsoft access tokens, causing scheduling requests to fail for Office365-connected accounts. ### Resolution The calendar service was updated to use the correct dependency compatible with the new encryption keys. Once deployed, scheduling functionality was fully restored and verified in production. ### Preventative Actions * Expand automated test coverage to explicitly validate scheduling flows for Microsoft Office365 accounts. * Improve internal validation and service dependency checks during encryption key rotations.
Resolved
The issue has been successfully resolved. Please refresh your browser to access the platform. Thank you for your patience
Resolved
Latency and service health has stabalized after a period of monitoring. Incident is considered resolved. More details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/21867
Resolved
The issue has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved. The system is operating normally.
Resolved
The issue with the Switches and DEX client connections for UK South 1 has been resolved.
Resolved
This incident has now been resolved.
Resolved
This incident has been resolved.
Resolved
The root cause has been identified and addressed, and monitoring shows the incident to be resolved.
Resolved
All application features are now operating as normal.
Resolved
This incident is resolved. Thank you for patience and understanding.
Resolved
This incident has been resolved. Our Engineering team has fully resolved the Spice Console access issue on Linux VPS Servers. Access has been restored, and workflows are operating normally. Corrective measures have been implemented to address the root cause and help prevent recurrence. Thank you for your patience and understanding throughout this process.
Resolved
The issue is resolved.
Resolved
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Resolved
The fix has been deployed and the Bitbucket integration is connecting normally again. Customers who previously encountered the "unknown error" while trying to connect Bitbucket should now be able to successfully complete the connection flow by retrying.
Resolved
Conversations start normally again.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
Between 17:39 UTC and 18:01 UTC April 22 2026, some endpoints in Azure germanywestcentral were temporarily unavailable due to failure to start new instances after scaling to zero. This issue is now resolved. No further updates are planned.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Issues with admin requests have been resolved.
Resolved
This incident has been resolved.
Resolved
We have confirmed full issue resolution.
Resolved
This incident has been resolved.
Resolved
We have identified and resolved the issue, this should be working correctly now for all. Thank you for your patience while we worked on this.
Resolved
This incident has been fully resolved. All platform features, including document signing and document downloads, are now fully operational. All affected documents have been successfully processed and PDF versions are now available. We apologize for any inconvenience caused and thank you for your patience throughout this incident.
Resolved
Between 07:25 UTC and 07:28 UTC, customers sending data to the legacy ingestion endpoint in our US region experienced a brief ingestion disruption lasting approximately 3 minutes. The issue has been fully resolved and ingestion is operating normally. Customers using modern DSN endpoints (`*.ingest.us.sentry.io`) were not affected. The disruption occurred during a scheduled configuration change. We're investing in additional tooling to detect and mitigate this class of issue faster. We apologize for the inconvenience and appreciate your patience.
Resolved
This incident has now been resolved.
Resolved
All Platform API functionality has been fully restored.
Resolved
This incident has been resolved.
Resolved
The backlog has been cleared and all systems are fully operational. Thank you for your patience.
Resolved
This incident has been resolved.
Resolved
Fix has been implemented and performance has stabilized.
Resolved
All impacted services have now fully recovered.
Resolved