Contentful incident: Cache not invalidating

Affected components

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

1. resolvedFeb 6, 2026, 17:19 UTC

   The issue is now resolved.

2. monitoringFeb 6, 2026, 16:46 UTC

   We think the impact from the issue is over.

3. monitoringFeb 6, 2026, 14:25 UTC

   We have deployed a fix which has resolved the issue. We will continue to monitor.

4. identifiedFeb 6, 2026, 14:09 UTC

   We are still working to mitigate the issue and expect to have a fix in place within the next 30 minutes

5. identifiedFeb 6, 2026, 11:35 UTC

   We have identified the cause of the issue and are working on a fix

6. investigatingFeb 6, 2026, 11:03 UTC

   We are investigating an issue where cache purges are not being processed (which may result in customers seeing stale data).

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.

• 1Password: Sign-in failure in some cases due to 2FA prompt not appearingMinor · Jan 23, 2026, 20:33 UTC

How often does Contentful have incidents?

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