Live  /  Contentful  /  Incident

Contentful: Issues with advanced caching on Content Delivery API

Contentful · contentful.comMajor incidentResolved2026-10-02 09:43 UTC
Public — what happened

Summary

Contentful reported a major problem with advanced caching on its Content Delivery API, specifically the feature that serves older cached content while fetching fresh copies (Stale While Revalidate), beginning on 2026-10-01 at 09:27 UTC. The company said it had pinpointed the problem at the outset but did not describe a cause. By 11:29 UTC that day, Contentful said most customers were no longer affected, and on 2026-10-02 at 08:43 UTC it said its fix had covered the remaining customers and it was watching the results. The incident was marked resolved on 2026-10-02 at 09:43.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Contentful against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Contentful: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Contentful report →

More from Contentful

Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.

The full archive is on the Contentful status & history page.

Related: Contentful status & history. SquidGrid is not affiliated with Contentful.