Skip to main content
Vendor reliability

Vendor record

Vercel

Vendor reports Operational

Checked

Front door check counts and Vercel’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Vercel endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.vercel.com
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Vercel product, region or your app worked.

How we count front door checks

Vercel says

Incident posts from Vercel’s status page, with its titles, impact levels and times. They say what Vercel chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

2

incidents Vercel posted, last 7 days

All vendors’ incidents

Most recent records · all dates

  • Increased build and deployment failures

    Major

    Started, per Vercel

    Closed in our record(6h 40m)

    Vercel’s post

  • Delays in Drains, Observability, and Workflow in Washington (iad1)

    Major

    Started, per Vercel

    Closed in our record(1h 24m)

    Vercel’s post

  • Vercel Auth login failures for pages with Deployment Protection enabled

    Major

    Started, per Vercel

    Closed in our record(19m)

    Vercel’s post

  • Elevated Sandbox error rates in Paris (cdg1)

    Minor

    Started, per Vercel

    Closed in our record(28m)

    Vercel’s post

  • Build failures and 500 errors for functions using Edge runtime

    Minor

    Started, per Vercel

    Closed in our record(35m)

    Vercel’s post
15 older records

  • Deployment stuck in initializing state

    Minor

    Started, per Vercel

    Closed in our record(1h 3m)

    Vercel’s post

  • Elevated Errors Triggering Deployments

    Major

    Started, per Vercel

    Closed in our record(52m)

    Vercel’s post

  • Elevated error rate on Connect and Passport

    Major

    Started, per Vercel

    Closed in our record(1h 42m)

    Vercel’s post

  • Elevated latency in VCR, Blob, and Sandbox API

    Minor

    Started, per Vercel

    Closed in our record(1h 23m)

    Vercel’s post

  • Increased deployment failures

    Major

    Started, per Vercel

    Closed in our record(1h 1m)

    Vercel’s post

  • Failures logging in with Vercel CLI

    Major

    Started, per Vercel

    Closed in our record(1h 24m)

    Vercel’s post

  • Elevated build initialization times

    Minor

    Started, per Vercel

    Closed in our record(43m)

    Vercel’s post

  • New container functions are failing

    Major

    Started, per Vercel

    Closed in our record(53m)

    Vercel’s post

  • Logs unavailable to query in Dashboard

    Major

    Started, per Vercel

    Closed in our record(20m)

    Vercel’s post

  • Partial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard

    Minor

    Started, per Vercel

    Closed in our record(6h 59m)

    Vercel’s post

  • Delays delivering log drains

    Minor

    Started, per Vercel

    Closed in our record(1h 53m)

    Vercel’s post

  • Vercel Community temporarily unavailable

    Not specified

    Started, per Vercel

    Closed in our record(22h 57m)

    Vercel’s post

  • Timeouts loading charts and observability data in Dashboard

    Major

    Started, per Vercel

    Closed in our record(46m)

    Vercel’s post

  • Dashboard authentication errors

    Critical

    Started, per Vercel

    Closed in our record(1h 3m)

    Vercel’s post

  • Increased invocation failures for Hobby Team functions

    Minor

    Started, per Vercel

    Closed in our record(1h 12m)

    Vercel’s post

Your code, your dependencies

See which of your code paths call Vercel

Connect GitHub or GitLab to find where your public or private repository uses Vercel. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Vercel status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · VercelStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/vercel?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Vercel status badge"></iframe>

Frequently Asked Questions

Is Vercel currently down?

Vercel's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Vercel last have an outage?

The most recent closed incident record began 4 days ago and spans 6h 40m. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Vercel?

No. CheckUpstream checks Vercel’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Vercel in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Vercel?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors