Contentful / Headless CMS

Contentful Status: How to Check If Contentful Is Down Right Now (2026)

Q: Why is Contentful content not loading on my site?

Content not loading is most often caused by: (1) CDA (Content Delivery API) being down or degraded — check contentfulstatus.com; (2) your Contentful access token being invalid or expired; (3) your space ID being wrong; (4) a Next.js or framework build caching stale content — trigger a new deployment. If the status page shows green, the issue is almost certainly in your configuration.

Q: Does Contentful CDA downtime take my website down?

It depends on your architecture. Static site generation (SSG/ISR with Next.js, Gatsby, Astro) caches Contentful content at build time — your site stays up during CDA outages, just serving cached content. Server-side rendering (SSR) that fetches Contentful on every request will show errors during CDA outages. Implement ISR or edge caching to make your site resilient to Contentful downtime.

Updated June 9, 2026 · 9 min read · API Status Check

Quick Answer

Check Contentful status at www.contentfulstatus.com (official). If your site is down but Contentful status is green, the issue is almost always your API token, space ID, or framework caching — not Contentful itself.

Staff Pick

📡 Monitor your APIs — know when they go down before your users do

Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.

Start Free →

Affiliate link — we may earn a commission at no extra cost to you

The Official Contentful Status Page

Contentful maintains an official status page at www.contentfulstatus.com. It breaks down status by API and region so you can identify exactly which Contentful service is affected:

Content Delivery API (CDA): cdn.contentful.com — read-only API your website fetches published content from. Most critical for live sites.

Content Management API (CMA): api.contentful.com — read/write API editors use to create, update, and publish content entries

Content Preview API (CPA): preview.contentful.com — fetches draft (unpublished) content for preview environments

Images API: images.ctfassets.net — resizes and transforms images on delivery, similar to a lightweight Cloudinary

Contentful Web App: app.contentful.com — the editorial interface editors use to manage content

Delivery Network: Global CDN layer caching CDA responses for fast global content delivery

What Each Contentful Status Indicator Means

Operational: All Contentful services working normally. If your site is not loading content, the issue is in your API token, space ID, content model, or framework configuration — not Contentful infrastructure.

Degraded Performance: A Contentful API is slower than normal. CDA response times may increase, causing slower page loads for SSR sites. Sites using SSG/ISR with cached content are typically unaffected during degraded periods.

Partial Outage: A specific Contentful service or region is down. The CMA may be unavailable for editors while the CDA continues serving content. Or vice versa. Check which specific component is affected.

Major Outage: A critical Contentful service is fully down. CDA outages directly impact live sites using server-side rendering. CMA outages prevent editorial updates. Both are rare.

Under Maintenance: Scheduled maintenance. Contentful provides advance notice for significant maintenance windows. The CDA is typically unaffected during routine CMA maintenance.

📡

Recommended

Get alerted the instant Contentful goes down

Better Stack monitors your Contentful CDA endpoint every 30 seconds and alerts your team before editors or users notice content delivery issues. Free tier included.

Try Better Stack Free →

Contentful APIs: CDA vs CMA vs CPA — What Can Fail Independently

Contentful has three separate API tiers that can fail independently. Understanding the difference determines how your site and editorial workflow are affected:

Content Delivery API (CDA) — cdn.contentful.com

What it is: Read-only API for fetching published content. This is what your live website calls. Globally cached via CDN for performance.

Signs of issues: Fetch errors from cdn.contentful.com, 503 responses on content requests, empty content arrays returned where entries should exist.

Workaround: Sites built with SSG (Next.js getStaticProps, Gatsby, Astro) serve cached content during CDA outages. SSR sites will show errors. Enable ISR (Incremental Static Regeneration) to limit blast radius.

Content Management API (CMA) — api.contentful.com

What it is: Read/write API used by editors to create, edit, and publish content. Also used by migration scripts and content import tools.

Signs of issues: Contentful web app showing errors when saving entries, editorial team unable to publish content, migration scripts failing.

Workaround: CMA outages do NOT affect your live site if using CDA — your site keeps serving the last published content. Editors should pause content operations until CMA recovers.

Content Preview API (CPA) — preview.contentful.com

What it is: Fetches draft content for preview environments. Used by Next.js preview mode, Gatsby Preview, and custom preview setups.

Signs of issues: Preview URLs returning errors, draft content not appearing in preview builds, Next.js preview mode broken.

Workaround: CPA outages only affect preview environments, not live sites. Teams can pause editorial review until preview is restored.

Contentful Images API — images.ctfassets.net

What it is: CDN layer that resizes and transforms images referenced in content entries. Used for thumbnail generation, format conversion, and responsive images.

Signs of issues: Images in rich text fields not loading, image transformation URLs returning 503, original asset URLs on assets.ctfassets.net may still work.

Workaround: Link directly to the original asset URL (assets.ctfassets.net) as fallback. Implement img onerror handlers to show placeholder images.

Contentful Web App — app.contentful.com

What it is: Editorial interface for managing content, content models, and settings.

Signs of issues: Editors cannot log in or access the Contentful console, content model editing broken, space settings inaccessible.

Workaround: Web app outages do not affect API access. Live sites and content queries via CDA continue normally. Editors should wait for the console to recover.

Does Contentful Downtime Take Your Website Down?

Whether Contentful downtime affects your live site depends entirely on your rendering strategy:

Static Site Generation (SSG)None during outage

Content is baked at build time. Contentful CDA outages have zero impact on live sites. New builds will fail until CDA recovers.

Incremental Static Regeneration (ISR)Minimal — serves stale cache

Pages revalidate in the background. During CDA outages, ISR serves stale cached content instead of erroring. New content won't appear until revalidation succeeds.

Server-Side Rendering (SSR)Site returns errors

SSR fetches Contentful on every request. CDA outages cause every page render to fail. Implement error boundaries and cached fallbacks to show graceful error states.

Client-Side Fetching (SPA)Content area shows error

CDA calls from the browser will fail. Implement loading states and error boundaries to show a graceful fallback instead of blank content areas.

Check Contentful Status Programmatically

Contentful uses Atlassian Statuspage, so you can check Contentful status via API for automated monitoring:

# Check overall Contentful status

curl https://www.contentfulstatus.com/api/v2/status.json

# Get active incidents

curl https://www.contentfulstatus.com/api/v2/incidents/unresolved.json

# Test your CDA endpoint directly (replace space_id and access_token)

curl "https://cdn.contentful.com/spaces/<space_id>/environments/master/entries?limit=1" \
  -H "Authorization: Bearer <access_token>" -o /dev/null -w "%{http_code}"

The status API returns an indicator field: none (all operational), minor, major, or critical. Use this in your monitoring dashboards or CI/CD pipelines.

📡

Recommended

Monitor your Contentful CDA automatically

Better Stack creates synthetic monitors for your Contentful delivery endpoints — alerts your team the instant content queries start failing. Free for small teams.

Try Better Stack Free →

Contentful Error Codes During Outages

When Contentful is down or degraded, your app or build pipeline sees specific HTTP errors:

503Service UnavailableContentful API is down. Check contentfulstatus.com. For CDA: serves cached content if using ISR/SSG. For CMA: editors must wait.

500Internal Server ErrorUnexpected Contentful server error. Retry with exponential backoff. Persistent 500s indicate an active incident.

429Rate LimitedToo many API calls per second. Not an outage — implement request throttling. Free tier has lower CDA rate limits than paid plans.

401UnauthorizedInvalid access token or wrong API key for the environment (CDA vs CMA tokens are different). Not an outage — verify credentials.

404 on entryEntry Not FoundEntry does not exist, is not published (CDA only serves published), or the space/environment ID is wrong. Not an outage.

ECONNREFUSEDConnection RefusedNetwork-level failure reaching Contentful CDN. Check DNS resolution for cdn.contentful.com and verify network connectivity.

What to Do When Contentful Is Down

Immediate Triage

Check contentfulstatus.com for CDA vs CMA status
Test your CDA endpoint directly (curl or browser)
Verify your API token is for the right environment (CDA ≠ CMA token)
Check if SSG cache is serving content normally
Alert your editorial team to pause publishing if CMA is down

Engineering Response

Migrate to ISR if using SSR — dramatically reduces CDA outage impact
Implement error boundaries for graceful content-fetch failures
Cache CDA responses at the edge (Vercel Edge, Cloudflare Workers)
Use webhook-triggered builds so CDA is called only at build time
Monitor CDA response times, not just uptime, to catch degraded states early

Frequently Asked Questions

Where is the official Contentful status page?

Contentful's official status page is at www.contentfulstatus.com. It shows component-level status for the Content Delivery API (CDA), Content Management API (CMA), Content Preview API (CPA), Images API, and the web app. Subscribe to email, SMS, or webhook notifications for incident updates.

Why is Contentful content not loading on my site?

Most content loading failures are configuration issues, not Contentful outages: (1) Wrong API token — CDA and CMA use different tokens; (2) Wrong space ID or environment; (3) Content not published — CDA only returns published entries; (4) Framework caching serving stale data. Check contentfulstatus.com first, then verify your credentials and content publication status.

What is the difference between Contentful CDA and CMA status?

The Content Delivery API (CDA) at cdn.contentful.com is the read-only public API your website fetches content from. The Content Management API (CMA) at api.contentful.com is used by editors to create and publish content. They run on separate infrastructure — CMA being down affects editorial work but not your live site.

Does Contentful CDA downtime take my website down?

Only if you use server-side rendering (SSR). Static sites (SSG) serve cached content during CDA outages. Incremental Static Regeneration (ISR) serves stale cached pages. Server-side rendered pages will error during CDA outages. Implementing ISR in Next.js is the most common way to protect against Contentful downtime.

How do I get alerts when Contentful goes down?

Subscribe to notifications at www.contentfulstatus.com via email, SMS, or webhook. For production sites, use Better Stack or API Status Check to monitor your specific Contentful CDA endpoint — independent monitoring catches incidents before the official status page updates. Monitor CDA response latency, not just status codes, to catch degraded performance early.

Alert Pro

14-day free trial

Stop checking — get alerted instantly

Next time Contentful goes down, you'll know in under 60 seconds — not when your users start complaining.

Email alerts for Contentful + 9 more APIs
$0 due today for trial
Cancel anytime — $9/mo after trial

Start Free Trial →Compare all plans →

Also recommended:

Better Stack — all-in-one monitoring 1Password — secure your API keys