← Back to the carnage
CONTENTFUL
🟡 Contentful's Frankfurt gateway decided to play 'guess the latency' with customer requests this morning. After pretending to be a broken vending machine for a couple hours, it graciously returned to normal levels. Still keeping one eye open just in case it gets any more creative ideas. (Auto-resolved: no updates in 24h)
// The official story
Errors on requests to Contentful from Frankfurt (FRA) region
// Status page says
Jul 3 , 11:29 UTC Update - Error rates have dropped back down again to normal levels. We are continuing to monitor the situation. Jul 3 , 09:32 UTC Identified - We are seeing elevated errors and latency for some customer requests which are routing through the Frankfurt (FRA) region for Content Management, Preview and the Contentful WebApp. We are working with our
🔗 Official status page (for the PR-approved version)
https://www.contentfulstatus.com/incidents/ftgt19x5nrlrContentful's Greatest Hits
🟢 CONTENTFUL
1d ago
🔴 Contentful's developer docs vanished like a ghost in the machine. Monitoring caught the body, investigation underway. Apparently 'headless CMS' now includes headless documentation—no brain required. (Auto-resolved: no updates in 24h)
🟢 CONTENTFUL
Aug 27, 2026
🟠 Contentful's daily audit logs decided to ghost everyone except EU customers. Engineers are now playing detective with the logging system, having discovered the problem exists in a parallel dimension where they can actually see it. (Auto-resolved: no updates in 24h)
🟢 CONTENTFUL
Aug 22, 2026
{
"skip": true
}
```
This is scheduled maintenance, which we're skipping per the rules. (Auto-resolved: no updates in 24h)
🟢 CONTENTFUL
Jun 18, 2026
🟠 Contentful's Management and Preview APIs decided to ghost some customers with 500 errors, though most folks are blissfully unaware their content delivery infrastructure is having a localized meltdown. Engineers found the culprit lurking in specific CDN nodes and are currently performing digital archaeology to fix it. (Auto-resolved: no updates in 24h)