CheckWebsiteNow

Live status check

Is Vercel down right now?

We check vercel.com from one measurement point when you open this page. This shows what we saw, not a worldwide verdict.

A fresh check of vercel.com runs in your browser. If no result appears, run the check on the start page.

Our last check

Not checked yet — a fresh check starts when you open this page.

About Vercel problems

Vercel problems can concern deployments that fail, builds that stop, serverless functions that time out or custom domains. Check the Vercel status page first, then open the build and function logs of the affected deployment in the Vercel dashboard. If one site fails while the dashboard works, the cause is more likely that project's code, configuration or domain settings.

Official information

Vercel official status page (verified )

Our check and Vercel's own status page can disagree. We test from one location and read only the homepage response. The provider reports what it knows about its own systems, such as sign-in, apps or single regions. A site can answer our check while one feature is broken, and a regional problem can affect one location but not another.

Vercel help pages

How this check works

  • One measurement location (single-self-hosted-probe), not a worldwide test.
  • We read only the response headers of the HTTPS homepage; page content and features are not tested.
  • We follow at most 5 HTTPS redirects and check every new address again.
  • The whole check stops after 10 seconds.
  • Results are reused for 60 seconds; this page refreshes its saved check at most every 10 minutes.

Full method and limits

Typical Vercel problems

An editorial list of typical problems, not based on live user reports.

  • Builds fail A failed Vercel build can be caused by the project's own build command, dependencies or environment variables, so read the build log from the first error.
  • Functions time out Vercel serverless functions that run longer than their allowed time end with a 504 timeout, so speed up the slow work or raise the configured duration where your plan allows it. Guide: 504 Gateway Timeout
  • Functions return server errors A 500 from a Vercel function means the code threw an error, so look at the function's runtime logs for the stack trace. Guide: 500 Internal Server Error
  • Page not found after a deploy A 404 on a Vercel deployment can mean the route or output directory does not match what the framework produced, so check the framework preset and output settings. Guide: 404 Not Found
  • Custom domain cannot be found A custom domain that cannot be found may lack the DNS records Vercel asks for, so compare them with the values in the project's domain settings. Guide: DNS_PROBE_FINISHED_NXDOMAIN
  • Certificate warning on a custom domain By default Vercel issues the certificate once the domain points to Vercel, so a name mismatch can mean the DNS change has not been made or has not spread yet. Guide: NET::ERR_CERT_COMMON_NAME_INVALID

General fixes: Cloud and hosting

  1. Read the logs first Cloud dashboards keep logs for each deploy, function or sync. The first error in the log is a good place to start looking for the cause.
  2. Verify the DNS records If a custom domain fails, compare its DNS records with the values the provider shows. DNS changes can take time to reach every network.
  3. Check storage and quotas A full storage plan or a used-up quota stops syncs, uploads and deploys even when the service itself works.
  4. Separate one site from the provider If a single website shows an error page from its hosting or CDN provider, the cause can be that website's own server rather than a problem with the provider for everyone.

Check another website

One measurement point. Results explain what we saw, not a worldwide verdict.