
Is Vercel down?
No, Vercel is up right now
Both signals agree: the official status feed and our own check.
Request to vercel.com, 3 min ago. 258 of 288 checks in the last 24 hours succeeded, median 169 ms.
Is Vercel working for you?
One click, no account. It helps others see whether the problem is widespread.
Response time, last 24 hours
measured from our server in GermanyWorks for everyone else? Fix it on your side
- 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.
- Test from the command line. Check name resolution and the route, to see where the connection stops.
nslookup vercel.com tracert vercel.com - 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.
- 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.
- 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 - 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.
- 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 21 min agoThe issue causing elevated errors triggering deployments has been resolved. Existing deployments and traffic are unaffected and no action is required.
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.
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 smaller payloads before delivery. Affec…
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 are required.
Questions and experiences
Ask about this page: members and our editors answer. Reading is open; writing needs a free account.
…