Is Vercel down?

What works right now

• ●UpREST APIYes: the CLI, Git deploys and the dashboard can talk to Vercel.403 in 360 ms
• ●UpEdge networkYes: Vercel-hosted sites are being served.200 in 295 ms

Failing for you? Check whether it is you

1. Is it you?

   If only your deploy fails, read the build log first (vercel inspect URL --logs); a failed build is not an outage. A site that errors after a deploy is usually the deploy: roll back.

What to do while Vercel is down

When Vercel is down, it depends on which part: sites already deployed are served from the edge and often stay up during build or dashboard incidents. Check the components list below.

1. Builds down? Build locally

   Build on your machine and upload the output, skipping Vercel's build step.

   vercel build --prod
   vercel deploy --prebuilt --prod

   Copy

2. Bad deploy? Roll back

   Instant rollback points production at the previous deployment without a rebuild.

   vercel rollback

   Copy

3. One region failing

   The official page lists regions (iad1 is Washington, D.C., the default for functions). Functions can be moved with regions in vercel.json.

Last 24 hours

Last 30 days

Incident timeline

Outages our checks saw, and incidents from the official status page, newest first.

1. OfficialOct 12, 13:35 UTC · 6.6 hIncreased build and deployment failures

   This incident has been resolved.

2. OfficialOct 6, 16:10 UTC · 16 minVercel Auth login failures for pages with Deployment Protection enabled

   This incident has been resolved.

3. OfficialSep 28, 13:44 UTC · 27 minBuild failures and 500 errors for functions using Edge runtime

   This incident has been resolved.

4. OfficialSep 18, 21:36 UTC · 55 minDeployment stuck in initializing state

   This incident has been resolved.

5. OfficialSep 18, 20:32 UTC · 50 minElevated Errors Triggering Deployments

   The issue causing elevated errors triggering deployments has been resolved. Existing deployments and traffic are unaffected and no action is required.

6. OfficialSep 18, 15:14 UTC · 1 minElevated Vercel KMS and Connect Errors

   Customers using Vercel KMS, Connect, Passport, or the Snowflake V0 Integration may have experienced elevated errors. We have resolved the incident and are continuing to monitor.

7. OfficialSep 17, 7:11 UTC · 1 minFailures delivering Logs to Drains

   Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries. An update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into

8. OfficialSep 16, 16:58 UTC · 1 minMissing Web Analytics and Speed Insights data

   Between 14:00 UTC and 15:40 UTC, Web Analytics and Speed Insights were degraded, resulting in some missing data in the dashboard during the affected time period. We identified the issue and landed a fix, and Web Analytics and Speed Insights have recovered. No additional actions

9. OfficialSep 16, 3:21 UTC · 1 minInvoice Generation Paused

   Invoice generation has been re-enabled. --- We've identified the issue and expect to resolve by end-of-day today. --- We've temporarily paused invoice generation. Invoices may arrive later than usual. Product availability and usage are unaffected, and no further action is re

10. OfficialSep 10, 17:42 UTC · 1.6 hElevated error rate on Connect and Passport

    Connect and Passport have fully recovered. This incident has been resolved.

11. OfficialSep 1, 19:59 UTC · 59 minIncreased deployment failures

    This incident has been resolved. Builds have recovered.

12. OfficialAug 26, 3:06 UTC · 1.4 hFailures logging in with Vercel CLI

    This incident has been resolved.

13. OfficialAug 25, 19:27 UTC · 38 minElevated build initialization times

    This incident has been resolved.

14. OfficialAug 20, 17:46 UTC · 47 minNew container functions are failing

    This incident has been resolved.

15. OfficialAug 19, 0:28 UTC · 1 minElevated errors for Workflow streams

    From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.

16. OfficialAug 17, 14:30 UTC · 6.9 hPartial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard

    Services have recovered. We are still working to ingest missing observability data during this period.

17. OfficialAug 14, 13:08 UTC · 1 minDynamic API routes returned 404 errors for some deployments

    This incident has been resolved. Between August 12, 17:12 UTC and August 13, 20:33 UTC, some Vercel deployments could return 404 errors from dynamic API routes. Deployments built on Vercel during this period were affected only if they met all three conditions: used Next.js 16.2

18. OfficialJul 23, 19:00 UTC · 1 minTelemetry data loss for Drains

    Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain acces

19. OfficialJul 23, 7:33 UTC · 45 minTimeouts loading charts and observability data in Dashboard

    This incident has been resolved.

20. OfficialJul 23, 6:47 UTC · 55 minDashboard authentication errors

    This incident has been resolved.

21. OfficialJul 17, 14:12 UTC · 1.1 hIncreased invocation failures for Hobby Team functions

    This incident has been resolved. A subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected.

22. OfficialJul 16, 23:09 UTC · 1.5 hGitHub-linked deployments and authentication affected

    This incident has been resolved.

23. OfficialJul 16, 6:07 UTC · 3.3 hMissing Build CPU Minutes Usage Data

    The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard.

24. OfficialJul 15, 23:04 UTC · 30 minErrors accessing teams that require 2FA

    This incident has been resolved.

25. OfficialJul 10, 21:22 UTC · 2.1 hIncreased Build failure rates

    This incident has been resolved.

Official status

The official page: https://www.vercel-status.com/.

Get alerts, or show it in your README

Follow the RSS feed of Vercel incidents in any reader, or paste this badge into a README; it updates itself.

[![Vercel status](https://tensorust-status.vercel.app/api/badge?id=vercel)](https://tensorust.com/status/vercel/)

How we check Vercel

Every 5 minutes, from Washington, D.C., with no API key. A failed check is retried once after 2 seconds before it counts; Vercel is down when every critical check fails, and degraded when some do or the official page reports a problem.

• https://api.vercel.com/v2/user: api.vercel.com answering (403 without a token is healthy); the CLI and deploys use it.
• https://vercel.com/: A Vercel-hosted site served from the edge.

Other services