Minor impactResolvedCMS

Contentful incident: 500 errors on Contentful APIs

Contentful reported this minor-impact incident on its official status page on Apr 23, 2026, 11:38 UTC. It was resolved after 20 min.

Right now Contentful is operational. Live Contentful status →

🔔 Get alerted when Contentful has issuesFree · email alerts · no credit card
Apr 23, 2026, 11:38 UTC
started
Apr 23, 2026, 11:57 UTC
resolved
20 min
duration
Minor
impact

Affected components

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

Timeline

updates from Contentful's status page ↗
  1. resolvedApr 23, 2026, 11:57 UTC

    The issue has been resolved.

  2. monitoringApr 23, 2026, 11:52 UTC

    The situation has improved. We will continue to monitor.

  3. investigatingApr 23, 2026, 11:38 UTC

    Some customers are experiencing 500 errors on our APIs. We are investigating.

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

← Previous: Customer's content not surfacing in the Contentful web app (Apr 13, 2026)Next: Customers experiencing issues with Workflows (Apr 23, 2026) →
Contentful incident on Apr 23, 2026: 500 errors on Contentful APIs · APIStatus.watch