CheckUpstream measured Contentful at 100.000% availability across 2833 independent checks (global · api). 27 incidents were recorded in the past 12 months; the most recent resolved 4 days ago after 14 hours. Status signals are polled from Contentful's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2833 · p95 142ms (30d)
Share of our own checks against Contentful endpoints that returned Contentful's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 7 incidents · 25 of 30 days with none posted · 10h 17m of declared impact
Fewer incidents in the last 30 days than 15% of 232 tracked services.
Share of each window with no impact declared by Contentful
7d
97.530%
30d
98.571%
90d
99.524%
180d
99.728%
1y
99.866%
Downtime like this can be refundable
If you're a paying Contentful customer, outages in these windows may count against Contentful's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Contentful entitlement →Does Contentful actually matter to you?
A Contentful outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 7 incidents Contentful published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Contentful takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 27, 16:28 UTC · resolved in 6m · Resolved
Aug 27, 16:26 UTC · resolved in 13h 34m · Resolved
Aug 24, 12:12 UTC · resolved in 9h 27m · Resolved
Aug 24, 12:12 UTC
Live Contentful status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/contentful)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Contentful is currently Operational. CheckUpstream tracks Contentful in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Contentful down" view? See the Contentful Live status page.
Jun 29, 13:30 UTC · resolved in 45m · Resolved
Jun 18, 16:11 UTC · resolved in 4h 49m · Resolved
Jun 12, 07:53 UTC · resolved in 12h 57m · Resolved
Jun 11, 12:29 UTC · resolved in 8h 41m · Resolved
Jun 9, 13:57 UTC · resolved in 22m · Resolved
Jun 2, 13:02 UTC · resolved in 2h · Resolved
May 26, 17:02 UTC · resolved in 17m · Resolved
May 13, 13:47 UTC · resolved in 13m · Resolved
May 5, 13:13 UTC · resolved in 1h 31m · Resolved
May 4, 13:20 UTC · resolved in 3h 19m · Resolved
Contentful's last resolved incident started 4 days ago and lasted 13h 34m (degraded performance).
Contentful's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Contentful endpoints. It is the share of checks that returned the expected response, not a figure taken from Contentful's status page.
Sign up to CheckUpstream and add Contentful to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Contentful's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.