Skip to main content
Contentstack logo

Is Contentstack Down?

No — Contentstack is up

Reachable from all 8 checked regions

Average response time: 453ms

Last checked · checks run every 6 hours

Official status page: https://status.contentstack.com

Contentstack uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
444ms
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
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: 100.00% uptime, 16 checks
Sep 2: 100.00% uptime, 30 checks
Sep 3: 100.00% uptime, 29 checks
Sep 4: 100.00% uptime, 32 checks
Sep 5: 100.00% uptime, 24 checks
Sep 6: 100.00% uptime, 22 checks
Sep 7: 100.00% uptime, 28 checks
Sep 8: 100.00% uptime, 31 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 39 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 24 checks
Aug 22 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.

lax
449ms
DNS 130ms TCP 1ms TLS 14ms TTFB 429ms
lhr
283ms
DNS 49ms TCP 2ms TLS 15ms TTFB 266ms
nrt
504ms
DNS 229ms TCP 1ms TLS 12ms TTFB 492ms
ord
275ms
DNS 69ms TCP 3ms TLS 16ms TTFB 253ms
sin
321ms
DNS 174ms TCP 1ms TLS 26ms TTFB 301ms
sjc
438ms
DNS 159ms TCP 3ms TLS 15ms TTFB 416ms
syd
1071ms
DNS 149ms TCP 0ms TLS 14ms TTFB 1052ms
yyz
285ms
DNS 86ms TCP 1ms TLS 15ms TTFB 264ms

What Contentstack does

Contentstack is a headless content management system. Editors write in a hosted web application and the content is served to websites and apps over APIs rather than rendered by the CMS itself. Because the reading and writing sides are separate services, a site in production and the team editing it depend on different parts of the platform.

What an outage looks like

Live sites stop receiving content and fall back to cached or empty responses when the Content Delivery API is affected, while editors sign in and work normally. The opposite is equally common: the web application and Content Management API fail so nobody can publish, and the public site keeps serving the last delivered content with no visible sign of a problem.

What to do about it

Check status.contentstack.com and match the entry to the symptom. Contentstack tracks the Web Application, Content Management API, Content Delivery API, GraphQL Delivery API, Image Delivery API, Assets API and Webhook Dispatcher separately, plus its Launch, Personalize, Automation, Marketplace and Lytics products. A broken site and a broken editor are usually different incidents and need different entries read.

Is it down for everyone, or just you?

If this page says Contentstack 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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Contentful
Contentful
Sanity
Sanity
Strapi
Strapi
Webflow
Webflow

Contentstack outage FAQ

My website is fine but I cannot publish. Is Contentstack down?
Very likely, on the authoring side. The Content Management API and Web Application are separate components from the Content Delivery API that serves your live site. When authoring is affected, the published site keeps serving content that was already delivered while editors cannot log in or save. Readers notice nothing, which is why the outage often gets reported internally first.
My site shows no content but editors are working. What broke?
Look at the delivery components. Contentstack separates the Content Delivery API, GraphQL Delivery API, Image Delivery API and Assets API from the editing surface. If your front end fetches at request time rather than at build time, a delivery incident empties the page immediately while the editorial team sees a perfectly healthy CMS.
Why did my integrations stop firing during an outage?
The Webhook Dispatcher is its own component. When it is affected, content changes still save but the downstream systems that listen for them never hear about it, so builds are not triggered and connected services fall behind. Nothing errors in the editor, which makes this the quietest failure on the platform. Verify downstream systems caught up after an incident.
Are images served separately from content?
Yes. Contentstack lists the Image Delivery API and the Assets API as components distinct from the Content Delivery API. A page can render its text correctly while images fail to load, or the reverse, so a partly broken page is a recognised shape rather than a sign that something is wrong with your own caching layer.
Does an outage affect Launch and Personalize too?
They are tracked separately. Contentstack reports Launch, its hosting product, with its own web application, management API, CDN and edge services entries, and Personalize with its own management API, edge API and analytics. An incident in one of those does not imply the core content APIs are affected, so read the entry for the product you actually use.

How we measure this

  • We request Contentstack'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 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 Contentstack 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 Contentstack goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required