Contentful incident: Issues with content editing and publishing for some EU customers

Affected components

• Content Delivery API
• Content Management API
• GraphQL Content API

1. resolvedJun 11, 2026, 21:00 UTC

   We have resolved the issue.

2. identifiedJun 11, 2026, 17:05 UTC

   We continue working on the fix and have already seen resolution for the majority of customers affected by it.

3. identifiedJun 11, 2026, 15:24 UTC

   We continue working on the resolution.

4. identifiedJun 11, 2026, 13:37 UTC

   Editing and publishing errors have been resolved, but some published entries may not yet appear in filtered API requests for a small amount of EU customers. We continue working on the resolution.

5. identifiedJun 11, 2026, 12:29 UTC

   Some customers in the EU might see intermittent problems with editing and publishing content. We have identified the underlying issue and are working to resolve it.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Contentful's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• DigitalOcean: DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"Major · Jun 11, 2026, 14:24 UTC
• Akamai: Edge Delivery - HTTP Content Delivery in EuropeMinor · Jun 5, 2026, 16:36 UTC
• LaunchDarkly: Delays in event ingestionMinor · Jun 9, 2026, 12:08 UTC
• Akamai: Bot Manager Premier IssuesMinor · Jun 10, 2026, 18:38 UTC
• Render: Platform latencyMinor · Jun 11, 2026, 14:37 UTC
• Render: Queued deploys stuckMinor · Jun 11, 2026, 16:01 UTC
• LiveKit: Intermittent errors for Google Gemini models via InferenceMinor · Jun 11, 2026, 17:52 UTC
• Render: Failed or delayed autodeploysMinor · Jun 11, 2026, 18:56 UTC
• Render: Stuck queued deploysMinor · Jun 11, 2026, 19:42 UTC

How often does Contentful have incidents?

Contentful reported 9 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 3h 6m. See Contentful's uptime and incident history