No, Vercel is up right now

Both signals agree: the official status feed and our own check.

Official status
All Systems Operational

From www.vercel-status.com, read 3 min ago.

Our check, from Germany
Answered in 87 ms

Request to vercel.com, 4 min ago. 288 of 288 checks in the last 24 hours succeeded, median 80 ms.

Is Vercel working for you?

One click, no account. It helps others see whether the problem is widespread.

We are still collecting reports. The numbers appear once 20 people have answered within 24 hours.

Response time, last 24 hours

measured from our server in Germany
0 ms375 ms750 ms20:0000:0004:0008:0012:0016:00
Time to first responseFailed check
One request every 5 minutes from a single location (Falkenstein, Germany). It shows how the answer time changes; it is not the speed you will see on your own connection.

Works for everyone else? Fix it on your side

  1. Check whether it is only this device. Open the service on your phone using mobile data instead of Wi-Fi. If it works there, the problem is your home network or this computer, not the service.
  2. Test from the command line. Check name resolution and the route, to see where the connection stops.
    nslookup vercel.com tracert vercel.com
  3. Check your tokens and rate limits. An expired token or a rate limit returns errors that look like an outage. Read the exact HTTP status code and message before assuming the service is down.
  4. Restart the router and the device. Unplug the router for 30 seconds, plug it back in, wait until it is online again, then restart the computer. This clears stuck connections and gives you a fresh route to the service.
  5. Flush the DNS cache. Windows may still remember an old address for the service. Open Command Prompt as administrator and run the command below, then try again.
    ipconfig /flushdns
  6. Turn off VPN and proxy for a moment. VPN exit servers are often rate-limited or blocked. Disconnect the VPN, and in Settings > Network & internet > Proxy make sure no manual proxy is set.
  7. Change the DNS server. If the name still does not resolve, switch DNS in Settings > Network & internet > your connection > DNS server assignment to a public resolver such as 1.1.1.1 or 8.8.8.8.

Recent incidents

from the official feed, read 27 min ago
ResolvedStarted Oct 12, 13:35 UTCResolved Oct 12, 20:11 UTC
ResolvedStarted Oct 10, 00:15 UTCResolved Oct 10, 01:37 UTC

All services have recovered.

ResolvedStarted Oct 6, 16:10 UTCResolved Oct 6, 16:26 UTC
ResolvedStarted Oct 6, 09:12 UTCResolved Oct 6, 09:36 UTC
ResolvedStarted Sep 28, 13:44 UTCResolved Sep 28, 14:11 UTC
ResolvedStarted Sep 18, 21:36 UTCResolved Sep 18, 22:31 UTC
ResolvedStarted Sep 18, 20:32 UTCResolved Sep 18, 21:22 UTC

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

ResolvedStarted Sep 18, 15:14 UTCResolved Sep 18, 12:00 UTC

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.

Questions and experiences

Ask about this page: members and our editors answer. Reading is open; writing needs a free account.

0 comments

…

4,322 members already hereThey read, write, comment and vote. 0 verified · 31 joined this year