PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Netlify is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Netlify. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Netlify issues today?

As of Oct 8, 2026 17:15 UTC, 0 users had reported issues with Netlify in the previous 24 hours.

How can I report a Netlify outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Cloud Infrastructure

Is Netlify down right now?

UnknownOfficial status last polled Oct 8, 2026 14:18 UTCnetlify.com Official status page

Netlify web hosting and edge functions

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

Is Netlify down right now?

Unknown. Netlify does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health.

Status as of Oct 8, 2026 17:15 UTC

Unknown

Netlify: status unknown

As of Oct 8, 2026 17:15 UTC

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

Reports 24h

Last incident

Sep 21, 2026 18:04 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 Netlify.

Incident days

No recorded incident

2h 23m

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 Netlify. Hover a day for detail.

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

Days with incidents

1 incident

Busiest day

2h 23m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Netlify outage on August 14 ", 25-minute disruption

Aug 14, 12:53 AM → Aug 14, 01:18 AM · 25 minutes · high

On August 14, Netlify experienced a service disruption. This incident was detected through user reports and lasted for approximately 25 minutes. The issue was resolved on August 14.

Peak reports

in 15 min

Total reports

during the incident

Duration

25 minutes

tracked by PulseWatch

Impact

Users reported experiencing issues with Netlify's services, primarily manifesting as API issues and websites being down. The incident was initially detected through user reports, with a total of 10 reports received during the disruption. At its peak, 6 reports were received within a 15-minute period, indicating a noticeable impact on user access and functionality.

Top reported issues

API issues6
Website down4

Incident timeline

Aug 14, 12:53 AM
PulseWatch detected elevated report volume (high severity)
Aug 14, 01:15 AM
Peak of 0 reports in 15 minutes (baseline 1.3)
Aug 14, 01:18 AM
Report volume returned to baseline — incident resolved

Official updates

Aug 14, 12:53 AM
Netlify status page acknowledged the incident.
View official source
Aug 14, 01:18 AM
Website down clustered from 3 sources across 6 signals. Suppressed 5 redundant alerts and flagged flapping behavior.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

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

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

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

Be the first to post a report.

Incident timeline

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

Full history →

ResolvedHigh

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

9/21/2026, 3:41:24 PM · 2h 23m

03:41 PM06:04 PM

Detection9/21/2026, 3:41:24 PM · 17d ago

Detected — high severity

ResolvedMedium