Is Contentful Down? How to Check Contentful Status Right Now

Contentful is the content layer for thousands of production applications — web apps, mobile apps, digital experiences, and marketing sites all pulling content from Contentful's APIs at runtime. When Contentful is working, it's invisible. When Contentful goes down, your application renders stale content, returns blank pages, or fails completely — and your teams can't push content updates through the web app either.

Here's how to quickly determine whether Contentful is down, understand which API or subsystem is failing, and reduce the blast radius when it happens.

Is Contentful Down Right Now?

Check these sources in order:

1. Statusfield — Contentful status — real-time monitoring across Contentful's Content Delivery API, Content Management API, Preview API, and web app.
2. Twitter/X — search Contentful down or Contentful API error sorted by Latest. Engineering teams notice Contentful API failures immediately and often post within minutes.
3. Downdetector — useful for confirming user-reported spikes but lacks component-level detail for API-specific failures.

What Actually Breaks During a Contentful Outage

Contentful is a multi-API platform. A failure in one API does not automatically affect the others.

Component	What it does	Impact when down
Content Delivery API (CDA)	Read-only REST + GraphQL API for fetching published content	All published content stops loading in production apps; pages render blank or fail
Content Management API (CMA)	Read/write API for managing content, assets, and space configuration	Editors can't create, update, or publish entries; integrations and CI/CD pipelines fail
Preview API	Returns draft/unpublished content for staging environments	Preview environments show stale or blank content; editors can't review before publishing
GraphQL Content API	GraphQL interface over the CDA	GraphQL queries fail; apps using GQL can't fetch content even if REST is partially operational
Webhooks	Delivers content change events to external endpoints	Build triggers, ISR invalidation, and third-party sync jobs stop firing
Asset CDN	Serves images and files via images.ctfassets.net	Images, PDFs, and media files return 404 or time out; pages render with broken assets
Web App	Browser-based content editor at app.contentful.com	Editors can't access the CMS; content operations are completely blocked
Compose / Launch / Studio	Contentful's higher-level editorial tools	Compose/Launch/Studio-based workflows are blocked; underlying APIs may still be operational

Common Contentful Error Symptoms

What you see	What it usually means
CDA returns 503 or times out	Content Delivery API is degraded
GraphQL returns 503 Service Unavailable	GraphQL layer specifically is degraded (CDA may still work via REST)
CMA returns 429 Too Many Requests	You've hit rate limits, not an outage (check your request volume)
CMA returns 503 or times out	Content Management API is degraded
Preview API returns blank or 503	Preview environment degraded; drafts not retrievable
Webhooks not firing after publish	Webhook dispatch degraded; build triggers and sync jobs won't run
Images loading as broken links	Asset CDN (images.ctfassets.net) degraded
app.contentful.com unreachable	Web app degraded; editors blocked
Content loads in staging but not production	API key scope or environment configuration issue, not an outage

Key distinction: The CDA (published content) and the CMA (content management) are separate services. An editorial workflow outage (CMA, web app, webhooks) does not mean your production application is down — the CDA serving live content can remain fully operational. Confirm which API is failing before escalating.

How Contentful's Architecture Affects Outage Scope

The CDA is a read-only CDN-backed API. Contentful's Content Delivery API caches published content at the CDN level. Brief CDA degradations sometimes affect only specific regions or edge nodes, not global delivery. If your app's CDA calls are failing from one geography but not another, suspect a regional edge issue rather than a full outage.

GraphQL and REST share the same content infrastructure but have separate API surfaces. A GraphQL Content API degradation doesn't always coincide with a REST CDA degradation — they can fail independently. If your app uses GraphQL, confirm the issue is at the GraphQL layer specifically before assuming all content delivery is down.

Webhooks run asynchronously after CMA operations. When you publish an entry, Contentful delivers the webhook asynchronously. A webhook delivery failure (your endpoint timing out, returning non-2xx, or being temporarily unreachable) does not cause the publish to fail — the entry is still published to the CDA. Webhook degradations typically manifest as stale builds or delayed ISR invalidation, not content delivery failures.

The Asset CDN is separate from the Content Delivery API. Content fields (text, numbers, references) are served from Contentful's API servers; assets (images, files) are served from images.ctfassets.net. A CDA outage doesn't necessarily take down asset delivery, and an asset CDN degradation doesn't affect text content. Check which is failing specifically — broken images with working text content indicates an asset CDN issue, not a full CDA outage.

Environments are isolated. Contentful's environment system (master, staging, feature branches) means a degradation affecting one environment doesn't automatically affect others. If your staging environment's Preview API is failing while production CDA is operational, the issue may be environment-specific.

Is It Contentful or Your Configuration?

Before escalating to an outage, rule out common configuration issues:

Your API key is scoped to the wrong environment. Contentful access tokens are scoped to specific spaces and environments. A 401 Unauthorized or 404 Not Found response typically means your token doesn't have access to the space or environment you're querying — not that Contentful is down.

You're hitting CMA rate limits. The CMA has rate limits that kick in for high-volume operations. A 429 Too Many Requests response is a rate limit, not an outage. Implement exponential backoff in your integration and reduce concurrent CMA operations.

Your webhook endpoint is failing, not Contentful. Contentful retries webhook delivery, but if your endpoint consistently returns errors or times out, Contentful may suspend deliveries. Check your endpoint's response logs before concluding Contentful's webhook system is degraded.

Your space is on a plan that doesn't include the failing feature. Some Contentful features (Compose, Environments, certain API rate tiers) are plan-specific. If a feature suddenly stops working, verify your space's current plan before assuming an outage.

Content changes via CMA aren't appearing via CDA because of CDN caching. The CDA caches content with a default TTL. If you publish a change via CMA and it doesn't appear via CDA immediately, it may be a cache miss, not a delivery outage. Force an uncached request with the ?nocache=true query parameter or check the X-Contentful-Request-Id response header.

When these are ruled out and failures persist, the evidence points to a Contentful infrastructure issue. Confirm at Statusfield.

Hardening Your Application Against Contentful Outages

1. Implement stale-while-revalidate for CDA responses

Cache CDA responses in your application layer or at your CDN (Vercel, Cloudflare, Next.js ISR) with a stale-while-revalidate policy. During a CDA degradation, your application serves cached content instead of returning errors. Configure a reasonable TTL — 60 seconds for content that changes frequently, longer for stable reference content — and treat cache hits as a degraded-but-functional state.

2. Build a fallback render path for CDA failures

In your data-fetching layer, catch CDA timeouts and 5xx responses and fall back to a cached snapshot stored in your own database or static JSON. This requires an upstream cache-warming job that writes content snapshots on successful fetches. During a Contentful outage, your application renders the snapshot version rather than a blank page.

3. Use webhook retries and a build-trigger queue for ISR

Don't rely on a single webhook delivery to trigger builds or ISR invalidation. Implement a queue-backed build trigger that retries on failure and de-duplicates rapid publish events. This ensures that a brief webhook degradation doesn't leave your site running indefinitely on stale content once Contentful recovers.

4. Monitor the CDA, not just your application

Your application's error rate can look normal even when the CDA is partially degraded — if you're serving from cache, your app is healthy while Contentful is struggling. Monitor the CDA directly from the outside. Statusfield monitors Contentful's API endpoints continuously and alerts you before your cache TTL expires and content starts failing.

5. Separate editorial and delivery dependencies in your architecture

Design your application so that a CMA or web app outage doesn't cascade to your content delivery. Editorial workflows (content creation, publishing) and content delivery (CDA calls from production) should use separate API tokens with minimum necessary scopes — this also limits the blast radius of a compromised token.

How to Stay Ahead of Contentful Outages

The goal is to know Contentful is degraded before your application starts serving blank pages or before editors discover they can't publish.

Statusfield monitors Contentful continuously and delivers alerts the moment a degradation is detected — through Slack, Discord, email, or webhook. On the free plan you get 3 monitors and 10 alerts/month, no credit card required.

→ Monitor Contentful on Statusfield — free, no credit card required

FAQ

Contentful CDA is returning errors but the web app works. What's happening?

The Content Delivery API and the web app (which uses the CMA) are separate services. A CDA degradation takes down content delivery for your production application without affecting editorial access in app.contentful.com. Check Statusfield for CDA-specific status. If you have CDN caching enabled, your application may continue to serve content from cache even while the CDA is degraded.

Is Contentful down for everyone or just my space?

Check Statusfield first. If Statusfield shows a degradation, it's affecting the shared infrastructure. If Statusfield shows operational, the issue is likely scoped to your space — check API key validity, environment access, rate limits, and plan-specific feature availability before concluding it's an outage.

My Contentful webhooks stopped firing. Is Contentful down?

Not necessarily — webhook dispatch is asynchronous and can fail independently of content delivery. Check Statusfield for webhook status. If Statusfield shows operational, check your webhook endpoint's response logs — Contentful suspends deliveries to endpoints that consistently return errors. Also verify in your Contentful space's webhook settings that the webhook is still active.

Contentful images are broken but text content loads fine. What's happening?

Contentful serves text content via its Content Delivery API and assets via a separate CDN (images.ctfassets.net). Broken images with working text content indicates an asset CDN degradation — not a full CDA outage. Check Statusfield for asset CDN status specifically.

How long do Contentful outages typically last?

Most Contentful degradations are partial — affecting one API (CMA, webhooks) while the CDA remains operational, or affecting a specific region's edge delivery while others continue normally. These typically resolve within 15–60 minutes. Full CDA outages that affect all content delivery are rare and usually resolve within 1–2 hours. Monitor Statusfield for live updates during an incident.