Skip to content
PulseWatchOUTAGE.INTEL
Contentful logo

Other

Is Contentful down right now?

UnknownOfficial status last polled Oct 4, 2026 06:18 UTCwww.contentful.comOfficial status page

Are you on the Contentful team and see something inaccurate? Report it to us. We respond within one business day.

Is Contentful down right now?

Unknown. Contentful does not have a conclusive current status. The vendor reports operational; no fresh independent reachability check confirms it.

Status as of Oct 4, 2026 07:34 UTC

Unknown

Contentful: status unknown

As of Oct 4, 2026 07:34 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

0

Last incident

Oct 2, 2026 10:41 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Contentful.

2

Incident days

28

No recorded incident

23h 56m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Contentful. Hover a day for detail.

Sep 5Sep 10Sep 15Sep 20Sep 25Sep 3001234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

2

Days with incidents

1 incident

Busiest day

23h 56m

Recorded duration

Report volume

0 reports in last 24H

07:30 AM11:00 AM02:30 PM06:00 PM09:30 PM01:00 AM04:30 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Contentful: vendor-reported major incident on October 1 (tracked 23h 55m)

Oct 1, 10:45 AM → Oct 2, 10:41 AM · 23h 55m · high

Contentful reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 23h 55m, from Thu, 01 Oct 2026 10:45:41 GMT to Fri, 02 Oct 2026 10:41:31 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
23h 55m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Oct 1, 10:45 AM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Oct 1, 10:45 AM

    Status updated: possible issue

  3. Oct 2, 10:41 AM

    PulseWatch closed the incident

Official updates

  1. Oct 1, 10:45 AM

    Contentful reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Contentful is unknown, so there is no incident history to measure and no uptime figure is shown.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

Contentful: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Contentful or have an alert rule on it can be alerted, labelled vendor-reported.

10/1/2026, 10:45:41 AM · 23h 55m

10:45 AM10:41 AM
Detection10/1/2026, 10:45:41 AM · 2d ago

Detected — high severity

Contentful: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Contentful or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Contentful incident correlated across 1 signal group: official/vendor.

9/3/2026, 8:00:01 AM · 5h 32m

08:00 AM01:32 PM
Detection9/3/2026, 8:00:01 AM · 1mo ago

Detected — medium severity

Contentful incident correlated across 1 signal group: official/vendor.

ResolvedMedium

Contentful incident correlated across 1 signal group: official/vendor.

8/17/2026, 9:09:40 AM · 3h 3m

09:09 AM12:12 PM
Detection8/17/2026, 9:09:40 AM · 1mo ago

Detected — medium severity

Contentful incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Contentful enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Unknown
Monitoring
The vendor reports operational; no fresh independent reachability check confirms it.
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

www.contentful.com