Skip to main content
Chrome icon

New! Check service status instantly with our Chrome extension

Add to Chrome External link icon
Firefox icon

New! Check service status instantly with our Firefox extension

Add to Firefox External link icon
magnifying glass icon
magnifying glass icon
  • Can't find service? Request service
    Sign up
    Vercel icon
    Vercel icon

    Vercel outage history

    Frontend cloud platform for fast, personalized web development.

    There were 138 Vercel outages since January 2025 which are summarized below, including incident details, duration, and resolution information.

    Not working for you?

    minor icon Minor

    : Vercel observability and billing data delays affect dashboards

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (3 hours and 9 minutes)

    Vercel reported delays in observability and billing data starting at . Workflow runs could appear as “pending” even after starting or finishing, while AI Gateway dashboards showed delayed observability data and potentially lower-than-actual traffic. Vercel also reported an issue affecting Queues.

    Vercel identified the cause and began implementing a fix, then reported recovery was underway. The affected components were marked recovered by , roughly three hours after the issue was first reported.

    minor icon Minor

    : Vercel builds and dashboard degraded briefly

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (25 minutes)

    Impact began around as users reported apps not loading and deployments taking unusually long. Customers saw delayed builds and slower page loads in the Vercel Dashboard, with Vercel CI also affected. The official status page acknowledged the issue at and indicated that Build & Deploy and Dashboard were impacted while investigation continued.

    minor icon Minor

    : Vercel Logs and Observability data delayed

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour)

    Vercel experienced delays in delivering Logs and Observability data, affecting users relying on real-time monitoring and log access. The issue impacted the Observability / Logs and Observability components, causing data latency for about an hour. The incident began at and was resolved by .

    Vercel issued updates indicating engineers identified the cause and were applying a fix, with services returning to normal after the investigation. The event represents degraded data delivery rather than a full outage, and dashboards may have shown delayed information during the window.

    major icon Major

    : Vercel build and deploy outages tied to GitHub incident

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (6 hours and 40 minutes)

    Vercel experienced a multi-hour disruption affecting builds and deployments. The issue began around with increased build failures and deployments failing to start, impacting the CI/CD / Git Integrations and Build & Deploy / Builds components. The team identified the issue and stated they were working on a fix, with failure rates decreasing later in the afternoon but some builds still queued or slow to start. A GitHub upstream incident was later identified as contributing to ongoing failures for GitHub-connected projects, noted at . Over the next hours, deployment event backlog was processed, and by the backlog had been cleared. The service returned to normal for the affected components at .

    major icon Major

    : Vercel iad1 outage disrupts drains, logs, and workflows

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 20 minutes)

    An outage in Vercel's Washington region (iad1) affected a broad portion of the Observability stack and the Workflow system, causing delays in drains delivery and in collecting logs, metrics, and traces, with some Workflow runs remaining pending. The incident began at when users in the iad1 region started experiencing degraded observability and delivery delays.

    major icon Major

    : Vercel auth login failures affect Deployment Protection pages

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (13 minutes)

    Users attempting to log in to or access pages that use Deployment Protection experienced authentication failures, disrupting access to protected deployments. The issue was traced to the Routing Middleware and began at . The outage was brief, impacting protected pages for roughly a dozen minutes before a fix was deployed.

    minor icon Minor

    : Vercel Sandbox in Paris shows elevated error rates

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (25 minutes)

    Vercel reported elevated error rates for Sandbox in Paris (cdg1) starting . The issues appeared localized to the Paris Sandbox environment, impacting developers attempting to run tests or deployments there. Other regions were not indicated as affected in the status updates, and users in that area may have experienced intermittent failures or slower responses when using Sandbox features.

    major icon Major

    : Vercel builds and deployments hit 500 errors; recovery underway

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (31 minutes)

    From around to , Vercel reported elevated build failure rates and deployments returning 500 errors for customers deploying during that window. Some builds progressed but resulted in failed deployments, and users invoking pages or APIs backed by the Edge runtime could also see 500 responses. The impact touched the Build & Deploy pipeline and edge functions, disrupting automated deployments and live edge executions for affected projects.

    According to Vercel's status updates, the issue expanded from builds to include edge runtime functions, with initial notices moving from a degraded state to a broader warning before gradually resolving. By , the status returned to normal as builds and deployments recovered, and guidance to re-deploy Edge runtime functions helped accelerate remediation.

    minor icon Minor

    : Vercel deployments stuck initializing, then recovered

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (55 minutes)

    Developers attempting to deploy on Vercel faced delays as builds became stuck in the initializing state, interrupting the deployment workflow. The issue affected the Build & Deploy / Builds component and hindered new deployments for a period around . Some user reports also indicated issues earlier, around , signaling impact before official acknowledgment.

    minor icon Minor

    : Vercel outage: Elevated errors triggering deployments impact builds

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (50 minutes)

    Users deploying on Vercel were affected as the Build & Deploy / Builds component experienced an outage driven by elevated errors that triggered deployments unexpectedly. The incident began at and deployments faced failures or unusual behavior for about fifty minutes, with reports from multiple regions indicating broad impact. Vercel's status page initially showed ongoing investigation as the cause and scope were assessed.

    Vercel icon

    Looking for more Vercel outage stats?

    Get real-time insights and historical data on Vercel outages.

    Vercel outage stats