Is Contentful Down?

No — Contentful is up

Reachable from all 8 checked regions

Average response time: 437ms

Last checked 29 minutes ago · checks run every 6 hours

Official status page: https://www.contentfulstatus.com

Contentful uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

512ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

20-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability 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.

ewr

125ms

DNS 86ms TCP 7ms TLS 9ms TTFB 124ms

fra

368ms

DNS 13ms TCP 86ms TLS 88ms TTFB 367ms

gru

520ms

DNS 15ms TCP 125ms TLS 125ms TTFB 396ms

iad

47ms

DNS 32ms TCP 2ms TLS 3ms TTFB 46ms

jnb

971ms

DNS 2ms TCP 239ms TLS 241ms TTFB 730ms

lax

266ms

DNS 23ms TCP 58ms TLS 60ms TTFB 207ms

lhr

400ms

DNS 87ms TCP 75ms TLS 77ms TTFB 399ms

nrt

809ms

DNS 146ms TCP 163ms TLS 165ms TTFB 808ms

ord

117ms

DNS 21ms TCP 22ms TLS 24ms TTFB 116ms

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 all 18 regions to find out where it breaks.

Test it yourself

Related services

Contentful outage FAQ

Will my website go down if Contentful does?

That depends entirely on when your site fetches content. A statically generated site that built earlier keeps serving from its own host and is unaffected. A site that calls the Content Delivery API on every request will degrade with it. This is the single most useful thing to know about your own setup before an incident, and it is decided by your framework's rendering mode rather than by Contentful.

Can editors keep working during a Contentful outage?

Sometimes. The Web App and the Content Management API are separate components from the Content Delivery API, so reading content on a live site can fail while editing works, or the reverse. If saves are failing, avoid retrying the same entry repeatedly, and copy any substantial unsaved text out of the editor before reloading, because a failed save does not reliably preserve it.

Should I trigger a rebuild while Contentful is having an incident?

No, wait. A build pulls content through the delivery API, so a rebuild during an incident can succeed partially and publish a site with missing or empty sections, replacing a working deployment with a broken one. The safer sequence is to wait for the delivery component to recover and then rebuild, rather than discovering the gap after it is live.

Do webhooks fire for changes made during an outage?

Webhooks is listed as its own component, so it can fail while content operations succeed. That combination is the awkward one: an entry is published in Contentful but the downstream system that reacts to publishing never hears about it. After a webhook incident, reconcile recently published entries against whatever consumes them rather than assuming delivery caught up.

How we measure this

We request Contentful's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means 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 the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required