Contentful
All Systems Operational
Content Management API   ? Operational
Content Delivery API   ? Operational
Web App   ? Operational
Website   ? Operational
Assets CDN   Operational
Authentication Service   ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Content Management API ?
Fetching
Content Delivery API ?
Fetching
Content Delivery API response time
Fetching
Content Management API Writes
Fetching
Past Incidents
Jan 15, 2019
Resolved - This incident has been resolved.
Jan 15, 23:05 UTC
Monitoring - We have rolled out a fix for the underlying issue and are monitoring the situation. All content received from the Content Delivery API should be up-to-date again and there is no additional publishing required.
Jan 15, 21:45 UTC
Investigating - We received reports that our Content Delivery API is returning outdated content versions and are investigating.
Jan 15, 20:52 UTC
Jan 14, 2019
Resolved - This incident has been resolved.
Jan 14, 17:45 UTC
Monitoring - Our alerting detected a build-up of queued webhook calls on one of our application server clusters affecting a subset of our customers. We have taken steps to remediate the situation, which has returned to normal and is being monitored.
Jan 14, 16:20 UTC
Jan 13, 2019

No incidents reported.

Jan 12, 2019

No incidents reported.

Jan 11, 2019
Resolved - The affected shard fully recovered and all metrics are back to normal.
Jan 11, 09:32 UTC
Monitoring - We have identified a stuck database replication as the cause and after restarting the replication don't see any further errors.
Jan 11, 09:11 UTC
Investigating - We have detected an increased error rate for customers on a specific shard and are investigating potential causes.
Jan 11, 08:39 UTC
Jan 10, 2019

No incidents reported.

Jan 9, 2019

No incidents reported.

Jan 8, 2019

No incidents reported.

Jan 7, 2019
Resolved - Issue resolved. All APIs back to normal.
Jan 7, 16:44 UTC
Monitoring - The rollout went through, all APIs should be back to normal.
Jan 7, 16:29 UTC
Update - outage on CMA is over.
we are making some modifications for the fix to roll out faster
Jan 7, 16:24 UTC
Identified - The issue has been identified and a fix is being implemented.
Jan 7, 16:08 UTC
Investigating - Users may experience 5XX error responses on content APIs.
We are already aware of the root cause and applying a fix.
Jan 7, 16:08 UTC
Jan 6, 2019

No incidents reported.

Jan 5, 2019

No incidents reported.

Jan 4, 2019

No incidents reported.

Jan 3, 2019

No incidents reported.

Jan 2, 2019

No incidents reported.

Jan 1, 2019

No incidents reported.