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 Vercel is down?

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

How many people have reported Vercel issues today?

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

How can I report a Vercel 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 Vercel down right now?

NormalOfficial status last polled Oct 8, 2026 16:18 UTCvercel.com Official status page

Frontend hosting and serverless deployment platform.

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

Is Vercel down right now?

No. Vercel has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 8, 2026 17:15 UTC

Normal

Vercel is operating normally

As of Oct 8, 2026 17:15 UTC

No elevated reports in the last 15 minutes. Baseline 4 reports/hour.

Reports 24h

Last incident

Sep 19, 2026 00:14 UTC

Trend

0/15m

Baseline

4/hr

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 Vercel.

Incident days

No recorded incident

3h 38m

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 Vercel. 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

3h 38m

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

Vercel outage on September 18 ","summary": "Vercel experienced a service disruption. The incident lasted for 3 hours and 38 minutes. Service was fully restored on September 19, 2026, at 00:14 UTC.","impactDescription": "During the 3-hour and 38-minute disruption, Vercel services experienced a medium severity incident. The incident was detected through automated monitoring systems and the vendor's status page. No user-reported data was collected for this incident, and therefore no specific user-reported issue types or affected regions were recorded."}

Sep 18, 08:36 PM → Sep 19, 12:14 AM · 3h 38m · medium

Vercel experienced a service disruption. The incident lasted for 3 hours and 38 minutes. Service was fully restored on September 19, 2026, at 00:14 UTC.

Duration

3h 38m

tracked by PulseWatch

Impact

During the 3-hour and 38-minute disruption, Vercel services experienced a medium severity incident. The incident was detected through automated monitoring systems and the vendor's status page. No user-reported data was collected for this incident, and therefore no specific user-reported issue types or affected regions were recorded.

Incident timeline

Sep 18, 08:36 PM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
Sep 18, 08:36 PM
Status updated: possible issue
Sep 19, 12:14 AM
Signals cleared — incident resolved

Official updates

Sep 18, 08:36 PM
Vercel status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.50%

90-day uptime

0.0%

Calculated from Vercel's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

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 →

ResolvedMedium

Vercel: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/18/2026, 8:36:12 PM · 3h 38m

08:36 PM12:14 AM

Detection9/18/2026, 8:36:12 PM · 19d ago

Detected — medium severity

Vercel: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium