Contentful incident: Experience API experiencing issues on upsert operations

Affected components

• Experience API

1. resolvedAug 17, 2026, 11:56 UTC

   The incident is resolved

2. monitoringAug 17, 2026, 10:19 UTC

   We have mitigated the issue and are seeing improvements on the error rates. We will continue monitoring the situation.

3. identifiedAug 17, 2026, 09:37 UTC

   We have identified the issue and are working with our upstream provider to provide a fix.

4. investigatingAug 17, 2026, 09:05 UTC

   We are investigating an issue where customers are experiencing errors with upsert operations on the Personalization Experience API.

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.

• Elasticsearch: Increased error rates for microsoft-multilingual-e5-largeMajor · Aug 13, 2026, 08:32 UTC
• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• HashiCorp Vault: Delayed HCP Terraform RunsMinor · Aug 15, 2026, 17:08 UTC
• Cursor: Investigating service degradationMinor · Aug 17, 2026, 09:32 UTC
• LaunchDarkly: Flag Updates via Polling API delayedMinor · Aug 17, 2026, 10:36 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