Loading status…
Loading status…
Contentful status · Data & Backend · checked (5s ago)
No — Contentful is not down. All Contentful systems are reported operational.
According to Contentful's official status page, Contentful was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Contentful's feed reported no outage in 100.00% of our checks.
Everything above is read from Contentful's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Contentful in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Contentful is a headless CMS: content is edited in its web app and read by applications through delivery APIs. Sites built on it fetch content at build time, at request time, or both, and those paths fail differently.
Contentful's status page separates the Content Delivery API — the read path production sites depend on, served from a CDN — from the Content Management API and the web app. The delivery API is deliberately the most heavily cached and the most resilient, so editors can be locked out of the web app while every published site keeps serving normally.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Contentful's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Contentful was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 5s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Contentful's status endpoint.
Contentful has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Contentful posted itself — not every problem users hit.
resolved · Sep 11, 03:46 PM (8d ago)
resolved · Sep 3, 07:45 AM (16d ago)
resolved · Aug 27, 04:26 PM (23d ago)
resolved · Aug 24, 12:12 PM (26d ago)
resolved · Aug 17, 09:05 AM (33d ago)
resolved · Aug 13, 09:34 AM (37d ago)
resolved · Aug 10, 11:08 AM (40d ago)
resolved · Jul 3, 09:32 AM (78d ago)
resolved · Jul 2, 07:53 AM (79d ago)
resolved · Jun 30, 10:53 AM (81d ago)
resolved · Jun 28, 10:00 PM (83d ago)
resolved · Jun 18, 04:11 PM (93d ago)
resolved · Jun 18, 07:57 AM (93d ago)
resolved · Jun 12, 07:53 AM (99d ago)
resolved · Jun 11, 12:29 PM (100d ago)
resolved · Jun 9, 01:57 PM (102d ago)
resolved · Jun 2, 01:02 PM (109d ago)
resolved · May 26, 05:02 PM (116d ago)
resolved · May 19, 04:57 PM (123d ago)
resolved · May 19, 04:28 PM (123d ago)
Content that will not appear is usually unpublished, or you are querying the preview API instead of the delivery API (or the reverse). Check the environment your access token is scoped to. Statically generated sites will not show new content until they rebuild, no matter how healthy Contentful is — that delay is your build pipeline, not the CMS.
Contentful is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.