outages.live
Live
ContentfulIncident ·

Delays in locale updates

ResolvedOfficial update
0

Contentful had delays in locale updates on the Content Management API. Contentful identified the cause and rolled out a fix. The incident is resolved and lasted about 113 minutes.

State

Resolved

Started

Lasted

1 h 53 min

Worst impact

Partial outage

Timeline

3 updates
11:4912:1812:4613:1413:42
Partial outageUpdate postedTimes in UTC

Investigating

1 h 2 min 54%

Identified

52 min 46%

Updates

Times in UTC

As posted by Contentful

Resolved

We have rolled out a fix and this should now be resolved.

Identified

We have identified the cause and are working to mitigate the issue.

Investigating

There may be delays with changes made to locales being reflected. We are investigating the issue.

Affected components

1
Content Management API

Contentful in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

12

Days with an incident

14

Median duration

2 h 31 min

This incident

25% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

24 h 16 min
median 2 h 31 min
90 days agoToday

Other Contentful incidents

All incidents

Contentful·Optimization Agent shows elevated error rate

Contentful reports an elevated error rate on the Optimization Agent. Contentful resolved the incident. The outage lasted about 12 minutes.

Resolved

Contentful·Insights Dashboard failing to load

This incident has been resolved.

Resolved

Contentful·[INCIDENT] https://www.contentful.com/developers/docs/ is not working

We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Resolved

Contentful·Issues with advanced caching on Content Delivery API

This issue has been resolved.

Resolved

Contentful·CORS errors on CDA

The issue has been resolved.

Resolved

Follow Contentful

Your coding agent knows when Contentful is down, and tells you when a failure is theirs, not yours. You can also get Contentful incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "contentful" and tell me if Contentful has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=contentful
Slack
/feed subscribe https://outages.live/feed.xml?providers=contentful

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane