Is Vercel Down?

If Prismix shows Vercel as "Operational" but you're having issues:

• Build failures with missing environment variables — Environment variables set in the Vercel dashboard are scoped to "Production", "Preview", or "Development" separately. A variable present in Production may not be available in Preview builds; double-check scope in Project Settings → Environment Variables and re-deploy after adding missing values.
• Edge Function cold start latency — Edge Functions run in Vercel's global edge runtime (V8 isolates), which has a cold-start on first invocation per region. If a region has low traffic, the isolate may be evicted and the next request experiences a latency spike of several hundred milliseconds even when the platform is healthy.
• DNS propagation delay after domain change — After adding or switching a custom domain, DNS TTLs mean the change can take minutes to hours to propagate globally. Vercel's certificate provisioning also needs DNS resolution to succeed before HTTPS works, so your site may show an SSL error during this window.
• Deployment queue backlog during incidents — During Vercel platform incidents or high-traffic events, the deployment queue can grow, causing pushes to stay in "Queued" state for many minutes. The deployment will eventually complete; cancelling and re-triggering rarely helps and resets your position in the queue.
• Preview URL not reflecting latest commit — Git integrations with GitHub/GitLab can sometimes fail silently if the webhook is misconfigured or if Vercel's GitHub App loses permissions. Check Project Settings → Git → Connected Git Repository to confirm the integration is healthy and re-authorize if needed.
• Serverless Function timeout (default 10s, max 900s) — Vercel Serverless Functions time out at 10 seconds on the Hobby plan and up to 900 seconds on Pro/Enterprise. Long-running tasks (large file processing, slow database queries) silently return a 504. Upgrade the plan or refactor to stream responses to avoid the limit.