Contentful incident: CMA Usage reporting and Audit Logs missing fields

1. resolvedDec 3, 2025, 09:03 UTC

   Audit Logs have returned to their normal state and are fully operational again.

2. monitoringDec 2, 2025, 17:04 UTC

   We've fixed the missing fields for Audit Logs and are now monitoring to ensure normal functionality is restored.

3. investigatingDec 2, 2025, 15:45 UTC

   The root cause has been identified, and a fix is in progress. At this stage, it appears that usage reporting is unaffected.

4. investigatingDec 2, 2025, 15:12 UTC

   We've identified an issue affecting CMA API call usage reporting and Audit Logs since Nov 14, where certain fields are missing and data may be incomplete. As a result, some Audit Log events may be absent, and the CMA usage reports displayed in the web app may not accurately reflect actual usage. We are currently investigating and will provide updates as soon as we understand the full impact.

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.

• Confluent Cloud: Flink job submission and job scale operations are affected in GCP asia-northeast1, europe-west8, europe-north1, southamerica-east1Major · Dec 2, 2025, 21:37 UTC
• Vimeo: increased-bufferingMinor · Nov 27, 2025, 09:06 UTC
• Mux: Elevated errors going liveMinor · Dec 2, 2025, 18:50 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