Minor impactResolvedCMS

Contentful incident: Increased latency on the Content Management API (CMA)

Contentful reported this minor-impact incident on its official status page on Dec 4, 2025, 10:33 UTC. It was resolved after 1h 7m.

Right now Contentful is operational. Live Contentful status →

🔔 Get alerted when Contentful has issuesFree · email alerts · no credit card
Dec 4, 2025, 10:33 UTC
started
Dec 4, 2025, 11:40 UTC
resolved
1h 7m
duration
Minor
impact

Affected components

  • Content Management API

Timeline

updates from Contentful's status page ↗
  1. resolvedDec 4, 2025, 11:40 UTC

    This issue is now resolved.

  2. monitoringDec 4, 2025, 11:23 UTC

    This issue has been mitigated and we are monitoring the result.

  3. identifiedDec 4, 2025, 10:54 UTC

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

  4. investigatingDec 4, 2025, 10:33 UTC

    We are investigating spikes of increased latency on our Content Management API (CMA).

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.

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: CMA Usage reporting and Audit Logs missing fields (Dec 2, 2025)Next: Invalid captcha for user registrations and email confirmations (Dec 10, 2025) →
Contentful incident on Dec 4, 2025: Increased latency on the Content Management API (CMA) · APIStatus.watch