Is Contentful Down?
Reachable from 7 of 8 checked regions — 1 region answered but refused our checks
Average response time: 445ms
Last checked · checks run every 6 hours
Official status page: https://www.contentfulstatus.com
Contentful uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 71 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
71-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
Answered in 15001ms — the origin is serving traffic, it just refused our client.
What Contentful does
Contentful is a headless content management system: editors manage content in a web app, and sites and applications pull it through APIs rather than rendering from a coupled template. Marketing sites, mobile apps and ecommerce front ends use it as a content source, which means an outage can affect either the people editing content or the sites reading it, and the two are separate failures.
What an outage looks like
The web app fails to load entries, or saves hang and content locks up mid-edit. Sites that fetch content at request time return errors or fall back to empty sections. Builds that pull content at deploy time fail outright. Images served through the Assets CDN or Image API may not load while text content is fine. Webhooks to downstream systems stop arriving.
What to do about it
Check www.contentfulstatus.com, which lists the Content Delivery API, Content Management API and GraphQL Content API separately from the Web App, so a delivery incident and an editing incident look different there. Assets CDN, Image API, Webhooks and Scheduled Publishing are listed individually. Statically generated sites that already built are usually unaffected, so avoid triggering a rebuild during a delivery incident.
Is it down for everyone, or just you?
If this page says Contentful is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Contentful outage FAQ
Will my website go down if Contentful does?
Can editors keep working during a Contentful outage?
Should I trigger a rebuild while Contentful is having an incident?
Do webhooks fire for changes made during an outage?
How we measure this
- We request Contentful's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Contentful publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Contentful goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring