- Detected by Pingoru
- Jul 23, 2026, 07:00 PM UTC
- Resolved
- Jul 23, 2026, 07:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 24, 2026, 05:26 PM UTC
Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Log Drains was not delivered. Logs, traces, and events emitted via drains during this window were dropped and are unrecoverable. Customers with one or more Log Drains configured on their Vercel projects lost telemetry emitted during the affected window. Data emitted outside the 19:12 and 19:18 UTC window was not dropped. We have deployed a fix and adding additional monitoring to detect and prevent this failure mode from happening in the future. We know how much you rely on this data, and we sincerely apologize for the disruption.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 07:33 AM UTC
- Resolved
- Jul 23, 2026, 08:18 AM UTC
- Duration
- 45m
Affected: FirewallSandboxSpeed InsightsWeb AnalyticsWorkflowObservability
Timeline · 3 updates
-
investigating Jul 23, 2026, 07:33 AM UTC
We are currently investigating timeouts loading observability data for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. This impacts charts in the Dashboard.
-
monitoring Jul 23, 2026, 07:55 AM UTC
The team identified the source of the issue and a fix has been implemented. We are starting to see recovery. Charts and observability data should be loading again for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. We continue to monitor.
-
resolved Jul 23, 2026, 08:18 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 06:47 AM UTC
- Resolved
- Jul 23, 2026, 07:41 AM UTC
- Duration
- 54m
Affected: Dashboard
Timeline · 3 updates
-
investigating Jul 23, 2026, 06:47 AM UTC
We are investigating an issue causing the dashboard to be inaccessible for some users.
-
monitoring Jul 23, 2026, 07:08 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 23, 2026, 07:41 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2026, 02:12 PM UTC
- Resolved
- Jul 17, 2026, 03:19 PM UTC
- Duration
- 1h 6m
Affected: Functions
Timeline · 4 updates
-
investigating Jul 17, 2026, 02:12 PM UTC
There are elevated rates of invocation failures for Hobby Team functions in new deployments. Existing deployments are unaffected. We are investigating. Mitigation is possible by rolling back to a previous deployment.
-
identified Jul 17, 2026, 02:19 PM UTC
We have identified the source of errors and are implementing a fix.
-
monitoring Jul 17, 2026, 02:27 PM UTC
We have deployed a fix and are continuing to monitor. Function invocations for new Hobby Team deployments should no longer fail. If you are still experiencing function invocation errors, redeploy or rollback to a previous deployment.
-
resolved Jul 17, 2026, 03:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 11:09 PM UTC
- Resolved
- Jul 17, 2026, 12:42 AM UTC
- Duration
- 1h 32m
Affected: DashboardBuildsGit Integrations
Timeline · 4 updates
-
investigating Jul 16, 2026, 11:09 PM UTC
We are investigating elevated error rates for users logging in to Vercel using their GitHub account and connecting their GitHub accounts to Vercel. Login with email or other sign-in methods is unaffected.
-
identified Jul 16, 2026, 11:39 PM UTC
We've identified an issue affecting deployments for projects linked to GitHub repositories, as well as GitHub login, signup, and account connections. CLI deployments and other sign-in methods are unaffected. We will share updates as they become available.
-
monitoring Jul 17, 2026, 12:07 AM UTC
Deployments for projects linked to GitHub repositories are recovering. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available. GitHub login, signup, and account connections are recovered.
-
resolved Jul 17, 2026, 12:42 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 08:39 AM UTC
- Resolved
- Jul 16, 2026, 10:45 AM UTC
- Duration
- 2h 5m
Affected: SAML Single Sign-On
Timeline · 3 updates
-
investigating Jul 16, 2026, 08:39 AM UTC
We are investigating SAML Single Sign-On (SSO) errors, leading to inability to login using SAML/SSO or access SSO-protected teams through the Vercel dashboard and CLI.
-
monitoring Jul 16, 2026, 10:23 AM UTC
The root cause of the SAML Single Sign-On (SSO) errors has been identified and a fix has been implemented. We are seeing error rates decrease. Users should be able to login with SAML/SSO or access their SSO-protected teams through the Vercel dashboard and CLI again. We are continuing to monitor.
-
resolved Jul 16, 2026, 10:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 06:07 AM UTC
- Resolved
- Jul 16, 2026, 09:27 AM UTC
- Duration
- 3h 20m
Affected: Builds
Timeline · 2 updates
-
monitoring Jul 16, 2026, 06:07 AM UTC
We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.
-
resolved Jul 16, 2026, 09:27 AM UTC
The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 11:04 PM UTC
- Resolved
- Jul 15, 2026, 11:34 PM UTC
- Duration
- 30m
Affected: DashboardAI GatewayAPI
Timeline · 3 updates
-
identified Jul 15, 2026, 11:04 PM UTC
We have identified an increase in erroneous 2FA (two-factor authentication) challenges and errors when accessing the Vercel dashboard and multiple API services for teams that require 2FA. We will share more information once we have it.
-
monitoring Jul 15, 2026, 11:16 PM UTC
A fix has been implemented and services have recovered. We are continuing to monitor to ensure that the services remain stable. We will provide additional updates as they become available.
-
resolved Jul 15, 2026, 11:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 09:22 PM UTC
- Resolved
- Jul 10, 2026, 11:28 PM UTC
- Duration
- 2h 6m
Affected: Builds
Timeline · 2 updates
-
monitoring Jul 10, 2026, 09:25 PM UTC
We've identified an issue where some customers may experience failed Builds beginning at 21:05 UTC. A rollback is in progress to mitigate this issue. We will provide additional updates as they become available.
-
resolved Jul 10, 2026, 11:28 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 07:53 PM UTC
- Resolved
- Jul 10, 2026, 10:36 PM UTC
- Duration
- 2h 42m
Affected: DashboardBuilds
Timeline · 5 updates
-
investigating Jul 10, 2026, 07:15 PM UTC
We've identified an issue where some customers may receive erroneous spend management budget notifications due to a spend management budget miscalculation. Affected teams with spend management budgets configured to pause projects may also experience paused deployments. We are currently investigating this issue. We will provide additional updates as they become available.
-
identified Jul 10, 2026, 07:53 PM UTC
We've identified and fixed the underlying issue, which was caused by a third-party SaaS provider. Our team is now unpausing deployments that were inadvertently paused as a result.
-
identified Jul 10, 2026, 08:50 PM UTC
We've compiled a list of deployments that were paused due to this incident and are now unpausing them in batches. If your deployment was paused, you can also navigate to the Vercel dashboard and click the unpause button in the banner.
-
identified Jul 10, 2026, 09:32 PM UTC
We are still working to unpause affected teams that were erroneously paused due to the spend management budget miscalculation. We will provide additional updates as they become available.
-
resolved Jul 10, 2026, 10:36 PM UTC
We have unpaused all impacted deployments. We will continue to monitor the situation.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 05:44 PM UTC
- Resolved
- Jul 09, 2026, 01:16 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 10, 2026, 05:44 PM UTC
The issue affecting Build Logs has been resolved. Between Jul 8 19:05 UTC and Jul 9 13:16 UTC, some Pro customers using standard machine types may have experienced missing Build Logs. New builds after the impact period are unaffected.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 07:13 PM UTC
- Resolved
- Jul 08, 2026, 07:13 PM UTC
- Duration
- 10s
Affected: Builds
Timeline · 5 updates
-
investigating Jul 08, 2026, 06:05 PM UTC
We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are currently investigating this issue and will provide additional updates as they become available.
-
investigating Jul 08, 2026, 06:40 PM UTC
We are seeing signs of recovery and the affected build queue has started to drain. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available.
-
monitoring Jul 08, 2026, 07:13 PM UTC
Build queues have returned to normal levels, and build processing should be restored. We are monitoring to ensure the service remains stable. We will provide additional updates as they become available.
-
monitoring Jul 08, 2026, 09:35 PM UTC
The issue affecting build queue processing has been resolved, and build queues have returned to normal. Builds are now processing as expected. We are continuing our internal root cause analysis.
-
resolved Jul 08, 2026, 10:23 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 04:31 PM UTC
- Resolved
- Jul 02, 2026, 04:46 PM UTC
- Duration
- 14m
Affected: DashboardCLE1 - Cleveland, East USIAD1 - Washington DC, USAFunctions
Timeline · 4 updates
-
investigating Jul 02, 2026, 04:31 PM UTC
We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.
-
identified Jul 02, 2026, 04:33 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 02, 2026, 04:39 PM UTC
A fix has been implemented and we are observing recovery across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor.
-
resolved Jul 02, 2026, 04:46 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 04:57 PM UTC
- Resolved
- Jul 01, 2026, 06:30 PM UTC
- Duration
- 1h 33m
Affected: Workflow
Timeline · 3 updates
-
identified Jul 01, 2026, 04:57 PM UTC
We've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available.
-
identified Jul 01, 2026, 05:49 PM UTC
We are continuing to work on recovering affected workflow runs that may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted.
-
resolved Jul 01, 2026, 06:30 PM UTC
The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected. We are continuing to work on recovering affected workflow runs that may be stuck in a pending state or have reached a failed state.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 01:08 PM UTC
- Resolved
- Jun 26, 2026, 03:14 PM UTC
- Duration
- 2h 5m
Affected: Dashboard
Timeline · 7 updates
-
investigating Jun 26, 2026, 01:08 PM UTC
We are currently investigating this issue.
-
investigating Jun 26, 2026, 01:23 PM UTC
We are continuing to investigate this issue.
-
investigating Jun 26, 2026, 02:08 PM UTC
We are continuing to investigate this issue and will provide an update as soon as we have more information.
-
identified Jun 26, 2026, 02:11 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Jun 26, 2026, 02:29 PM UTC
Login is recovering for most users. We're monitoring to ensure stability.
-
monitoring Jun 26, 2026, 03:03 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 26, 2026, 03:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2026, 07:45 AM UTC
- Resolved
- Jun 25, 2026, 01:43 PM UTC
- Duration
- 5h 58m
Affected: Workflow
Timeline · 7 updates
-
investigating Jun 25, 2026, 07:45 AM UTC
We are currently investigating an issue where some recently deployed Workflow projects are stuck as pending and not delivering queued messages as expected.
-
identified Jun 25, 2026, 08:27 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Jun 25, 2026, 09:25 AM UTC
The issue has been identified. We are continuing to work on a fix for this issue.
-
identified Jun 25, 2026, 10:42 AM UTC
We are still working on a fix for this issue. While we fix the issue, users experiencing pending Workflow runs can trigger an instant rollback to a working deployment created before Jun 24 21:00 UTC to resume operation on new runs.
-
identified Jun 25, 2026, 12:15 PM UTC
We are currently rolling a fix for the issue. We are monitoring the results.
-
monitoring Jun 25, 2026, 01:30 PM UTC
The fix has been fully rolled out and we are monitoring the results.
-
resolved Jun 25, 2026, 01:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2026, 11:24 PM UTC
- Resolved
- Jun 23, 2026, 11:34 PM UTC
- Duration
- 10m
Affected: Domain Registration
Timeline · 4 updates
-
investigating Jun 23, 2026, 11:24 PM UTC
We're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.
-
identified Jun 23, 2026, 11:26 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 23, 2026, 11:28 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 23, 2026, 11:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 05:54 PM UTC
- Resolved
- Jun 19, 2026, 05:54 PM UTC
- Duration
- —
Affected: Functions
Timeline · 1 update
-
resolved Jun 19, 2026, 05:54 PM UTC
Between Jun 19 09:09 and Jun 20 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE. As part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989 We have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the Node.js upgrade once the upstream issue is fixed.
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 01:39 PM UTC
- Resolved
- Jun 16, 2026, 03:39 PM UTC
- Duration
- 2h
Affected: DashboardFirewallSpeed InsightsWeb AnalyticsObservability
Timeline · 5 updates
-
investigating Jun 16, 2026, 01:39 PM UTC
We are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features.
-
investigating Jun 16, 2026, 02:45 PM UTC
We are continuing to investigate partial disruption to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are also investigating delayed usage alerts.
-
identified Jun 16, 2026, 03:16 PM UTC
The team has identified the source of the issue and is preparing a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard.
-
monitoring Jun 16, 2026, 03:26 PM UTC
The team has deployed a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to monitor.
-
resolved Jun 16, 2026, 03:39 PM UTC
The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 14, 2026, 09:03 PM UTC
- Resolved
- Jun 15, 2026, 01:24 AM UTC
- Duration
- 4h 20m
Affected: FRA1 - Frankfurt, Germany, Europe
Timeline · 6 updates
-
investigating Jun 14, 2026, 09:03 PM UTC
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.
-
identified Jun 14, 2026, 09:07 PM UTC
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
-
identified Jun 14, 2026, 09:26 PM UTC
The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
-
identified Jun 14, 2026, 11:15 PM UTC
The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished.
-
monitoring Jun 15, 2026, 12:25 AM UTC
All traffic has been restored to the FRA1 Vercel Region.
-
resolved Jun 15, 2026, 01:24 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 02:09 PM UTC
- Resolved
- Jun 09, 2026, 02:46 PM UTC
- Duration
- 36m
Affected: Builds
Timeline · 4 updates
-
investigating Jun 09, 2026, 02:09 PM UTC
We are currently investigating this issue.
-
identified Jun 09, 2026, 02:33 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 09, 2026, 02:39 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 09, 2026, 02:46 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 06:57 PM UTC
- Resolved
- Jun 08, 2026, 08:00 PM UTC
- Duration
- 1h 2m
Affected: Functions
Timeline · 5 updates
-
identified Jun 08, 2026, 06:57 PM UTC
The issue has been identified and a fix is being implemented. A small number of requests may have seen elevated error rates in function invocations during this period.
-
identified Jun 08, 2026, 07:04 PM UTC
We're continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region.
-
monitoring Jun 08, 2026, 07:36 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jun 08, 2026, 07:36 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 08, 2026, 08:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 07:21 PM UTC
- Resolved
- Jun 01, 2026, 08:02 PM UTC
- Duration
- 40m
Affected: Builds
Timeline · 4 updates
-
investigating Jun 01, 2026, 07:21 PM UTC
We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.
-
identified Jun 01, 2026, 07:50 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 01, 2026, 07:55 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 01, 2026, 08:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 04:00 PM UTC
- Resolved
- May 28, 2026, 04:59 PM UTC
- Duration
- 59m
Affected: Edge FunctionsRouting MiddlewareFunctions
Timeline · 4 updates
-
investigating May 28, 2026, 04:00 PM UTC
We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.
-
identified May 28, 2026, 04:18 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 28, 2026, 04:37 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 28, 2026, 04:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 04:50 AM UTC
- Resolved
- May 27, 2026, 05:02 AM UTC
- Duration
- 11m
Affected: Dashboard
Timeline · 2 updates
-
investigating May 27, 2026, 04:50 AM UTC
We are currently investigating this issue.
-
resolved May 27, 2026, 05:02 AM UTC
This incident has been resolved.
Read the full incident report →
