Contentful incident: Audit logs incomplete for days ranging between 30 of April and 4th of May.

1. resolvedMay 5, 2026, 14:41 UTC

   We've recovered the logs for all customers for the affected dates and these have been sent through to customer storage.

2. identifiedMay 5, 2026, 13:13 UTC

   Due to an internal change in data permissions, some audit logging data was not delivered to customers between April 30 and May 4. The pipeline has since recovered, and today’s logs are being delivered as expected. We are now working to restore the missing logs from the past few days.

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.

• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Linode: (Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]Minor · May 1, 2026, 17:51 UTC
• Upstash: QStash US Region: Schedule DegradationMinor · May 5, 2026, 14:24 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