Minor impactResolvedCMS

Contentful incident: Errors on requests to Contentful from Frankfurt (FRA) region

Contentful reported this minor-impact incident on its official status page on Jul 3, 2026, 09:32 UTC. It was resolved after 7h 54m.

Right now Contentful is operational. Live Contentful status →

🔔 Get alerted when Contentful has issuesFree · email alerts · no credit card
Jul 3, 2026, 09:32 UTC
started
Jul 3, 2026, 17:26 UTC
resolved
7h 54m
duration
Minor
impact

Affected components

  • Content Management API
  • Web App
  1. resolvedJul 3, 2026, 17:26 UTC

    We have taken action and error rates have returned to normal.

  2. identifiedJul 3, 2026, 11:29 UTC

    Error rates have dropped back down again to normal levels. We are continuing to monitor the situation.

  3. identifiedJul 3, 2026, 09:32 UTC

    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 upstream CDN provider to mitigate the issue. Customers affected by this can temporarily 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).

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.

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

Contentful incident on Jul 3, 2026: Errors on requests to Contentful from Frankfurt (FRA) region · APIStatus.watch