Contentful reported this minor-impact incident on its official status page on Jul 2, 2026, 07:53 UTC. It was resolved after 6h 34m.
Right now Contentful is operational. Live Contentful status →
This issue has been resolved.
Routing traffic away from the affected POP (FRA) has been effective in mitigating this issue. We are continuing to monitor the situation.
Traffic has been routed away from the affected POP (FRA) and error rates have dropped as a result.
We are continuing to work with our upstream CDN provider on mitigating this issue with traffic routing through the Frankfurt region. Some customers have been able workaround the issue by using a VPN when connecting to Contentful (which routes traffic to a different Point of Presence (POP) other than the affected FRA one).
We are continuing to work with one of our upstream CDN providers on resolving this issue.
We are continuing to investigate this issue. Note: This is mostly affecting customer requests routed through the Frankfurt region.
We are investigating an issues where some customers are seeing increased errors and latency when trying to access Contentful Management and Preview APIs (CMA and CPA) - this issue also affects the Contentful WebApp.
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.
Overlapping incidents aren't necessarily related.
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