Is Contentful down?
Contentful is up
Right now
No. No incidents reported.
Last checked (2026-10-10 07:16 UTC) from www.contentfulstatus.com · every 180s
For agents
proceed
Proceed.
GET upbutler.com/status/contentful/status.agent.json
MCP: upstream_status {"service":"contentful"}
Headless CMS delivery, preview and management APIs.
What Contentful says
Operational
Taken as is from Contentful's own status page API. Incident titles and component names below are theirs.
Open www.contentfulstatus.comWhat UpButler measured
There is no keyless endpoint of Contentful that says anything useful, so UpButler does not probe it. To check your own Contentful account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Contentful components
35 operational
- Content Management APIOperational
- Content Delivery APIOperational
- GraphQL Content APIOperational
- Authentication serviceOperational
- Web AppOperational
- WebsiteOperational
- Assets CDNOperational
- WebhooksOperational
- Scheduled PublishingOperational
- LaunchOperational
- ComposeOperational
- StudioOperational
- Customer Support SystemOperational
- Marketplace AppsOperational
- Image APIOperational
- Transactional EmailsOperational
- Taxonomy Delivery APIOperational
- Enterprise ObservabilityOperational
EU data residency
- Content Management APIOperational
- Content Delivery APIOperational
- GraphQL Content APIOperational
- Authentication ServiceOperational
- Web AppOperational
- Assets CDNOperational
- WebhooksOperational
- Scheduled PublishingOperational
- LaunchOperational
- StudioOperational
- Marketplace AppsOperational
- Image APIOperational
- Enterprise ObservabilityOperational
Ninetailed (Personalization)
- Experience APIOperational
- Insights APIOperational
- Management APIOperational
- Integration APIOperational
Contentful incidents, last 90 days
- 2026-07-13: no record
- 2026-07-14: no record
- 2026-07-15: no record
- 2026-07-16: no record
- 2026-07-17: no record
- 2026-07-18: no record
- 2026-07-19: no record
- 2026-07-20: no record
- 2026-07-21: no record
- 2026-07-22: no record
- 2026-07-23: no record
- 2026-07-24: no record
- 2026-07-25: no record
- 2026-07-26: no record
- 2026-07-27: no record
- 2026-07-28: no record
- 2026-07-29: no record
- 2026-07-30: no record
- 2026-07-31: no record
- 2026-08-01: no record
- 2026-08-02: no record
- 2026-08-03: no record
- 2026-08-04: no record
- 2026-08-05: no record
- 2026-08-06: no record
- 2026-08-07: no record
- 2026-08-08: no record
- 2026-08-09: no record
- 2026-08-10: no record
- 2026-08-11: no record
- 2026-08-12: no record
- 2026-08-13: no record
- 2026-08-14: no record
- 2026-08-15: no record
- 2026-08-16: no record
- 2026-08-17: no record
- 2026-08-18: no record
- 2026-08-19: no record
- 2026-08-20: no record
- 2026-08-21: no record
- 2026-08-22: no record
- 2026-08-23: no record
- 2026-08-24: no record
- 2026-08-25: no record
- 2026-08-26: no record
- 2026-08-27: no record
- 2026-08-28: no record
- 2026-08-29: no record
- 2026-08-30: no record
- 2026-08-31: no record
- 2026-09-01: no record
- 2026-09-02: no record
- 2026-09-03: no record
- 2026-09-04: no record
- 2026-09-05: no record
- 2026-09-06: no record
- 2026-09-07: no record
- 2026-09-08: no record
- 2026-09-09: no record
- 2026-09-10: no record
- 2026-09-11: no record
- 2026-09-12: no record
- 2026-09-13: no record
- 2026-09-14: no record
- 2026-09-15: no record
- 2026-09-16: no record
- 2026-09-17: no record
- 2026-09-18: no record
- 2026-09-19: no record
- 2026-09-20: no record
- 2026-09-21: no record
- 2026-09-22: no record
- 2026-09-23: no record
- 2026-09-24: no record
- 2026-09-25: no record
- 2026-09-26: no record
- 2026-09-27: no record
- 2026-09-28: no record
- 2026-09-29: major incident
- 2026-09-30: no incident reported
- 2026-10-01: major incident
- 2026-10-02: major incident
- 2026-10-03: no incident reported
- 2026-10-04: no incident reported
- 2026-10-05: no incident reported
- 2026-10-06: no incident reported
- 2026-10-07: no incident reported
- 2026-10-08: no incident reported
- 2026-10-09: no incident reported
- 2026-10-10: no incident reported
Each bar is a day, coloured by the worst incident Contentful reported. It is their incident record, not a measurement of uptime.
- Incidents
- 2
- 2 major or critical
- Typical time to resolve
- —
- median, needs 3 incidents
- Nine in ten within
- —
- 90th percentile
- Longest
- 24 h 16 min
- record since 2026-09-29
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Issues with advanced caching on Content Delivery API | major | 24 h 16 min | |
| CORS errors on CDA | major | 1 h 5 min |
Get alerted when Contentful goes down
No account. One email when Contentful reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.
Or follow the RSS feed. On UpButler? Add Contentful as a dependency to route it to Slack, Teams or a webhook.
Status badge
Show Contentful's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/contentful)Tell your outage from Contentful's
Declare that your project depends on Contentful. When one of your monitors fails while Contentful has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- contentfulcurl -s https://upbutler.com/status/contentful/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "contentful",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Contentful down right now?
- No. As of 2026-10-10 07:16 UTC, Contentful is up. This page reads the status again every 3 minutes.
- Where does this status come from?
- From Contentful's own status page API at https://www.contentfulstatus.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Contentful's words.
- Can I get an alert when Contentful goes down?
- Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Contentful reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/contentful/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
- How can my agent or app check Contentful status?
- Fetch https://upbutler.com/status/contentful/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"contentful"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Contentful's?
- Add "contentful" to the dependencies of your UpButler workspace. When one of your monitors fails while Contentful has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
Also check
UpButler is not affiliated with Contentful. Status and incident text belong to Contentful and are read from their public status source; the probe result is UpButler's own measurement.