https://approjects-vendor-status-watch.static.hf.space/v/vercel.htmlIncidents from Vercel's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/zbs4ktd26fb0vercel:2026-09-10T17:42:15.875ZThu, 10 Sep 2026 17:42:15 +0000Connect and Passport have fully recovered. This incident has been resolved.https://stspg.io/qjy1j78m6sscvercel:2026-09-04T19:11:44.000ZFri, 04 Sep 2026 19:11:44 +0000Blob has fully recovered. This incident has been resolved.https://stspg.io/01mntryqfgdjvercel:2026-09-01T19:59:37.473ZTue, 01 Sep 2026 19:59:37 +0000This incident has been resolved. Builds have recovered.https://stspg.io/119clbk6991svercel:2026-08-26T03:06:11.564ZWed, 26 Aug 2026 03:06:11 +0000This incident has been resolved.https://stspg.io/xd3cnhctqkw3vercel:2026-08-25T19:27:23.387ZTue, 25 Aug 2026 19:27:23 +0000This incident has been resolved.https://stspg.io/shj8f589lgh9vercel:2026-08-20T17:46:33.310ZThu, 20 Aug 2026 17:46:33 +0000This incident has been resolved.https://stspg.io/fhw5075cj82rvercel:2026-08-20T11:14:32.032ZThu, 20 Aug 2026 11:14:32 +0000The system is operating normally and fully recovered.https://stspg.io/2szns4x5lfs2vercel:2026-08-18T23:00:00.000ZTue, 18 Aug 2026 23:00:00 +0000From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.https://stspg.io/sqztsdm8bq4dvercel:2026-08-17T14:30:28.000ZMon, 17 Aug 2026 14:30:28 +0000Services have recovered. We are still working to ingest missing observability data during this period.https://stspg.io/s34qc7lrx9dbvercel:2026-08-14T13:08:12.835ZFri, 14 Aug 2026 13:08:12 +0000This incident has been resolved. Between August 12, 17:12 UTC and August 13, 20:33 UTC, some Vercel deployments could return 404 errors from dynamic API routes. Deployments built on Vercel during this period were affected only if they met all three conditions: used Next.js 16.2 or earlier, used the Pages Router with internationalization (i18n configured in next.config.js), and used dynamic API routes, such as pages/api/[slug].ts or pages/api/[...path].ts. Deployments built outside Vercel (with vercel deploy --prebuilt) were not affected, and existing deployments not rebuilt during this period were not affected. If your project matches the conditions above and you deployed during the impact window, redeploy your project. Affected deployments are not fixed automatically; a new deployment https://stspg.io/jygyd62lmmdxvercel:2026-08-06T16:37:10.291ZThu, 06 Aug 2026 16:37:10 +0000This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.https://stspg.io/nc6n7dnn8nz7vercel:2026-07-25T18:57:40.420ZSat, 25 Jul 2026 18:57:40 +0000Maintenance on Vercel Community has concluded. We thank you for your patience, and apologize for any inconvenience.https://stspg.io/b2wb9x4qkqwqvercel:2026-07-23T19:00:00.000ZThu, 23 Jul 2026 19:00:00 +0000Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain accessible in the Logs UI dashboard, where they can also be exported. We have deployed a fix and are 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.https://stspg.io/pcy9pldzdfqwvercel:2026-07-23T07:33:48.200ZThu, 23 Jul 2026 07:33:48 +0000This incident has been resolved.https://stspg.io/k5mrp1pc2l00vercel:2026-07-23T06:47:01.252ZThu, 23 Jul 2026 06:47:01 +0000This incident has been resolved.https://stspg.io/qcpsy7kj6dlcvercel:2026-07-17T14:12:58.000ZFri, 17 Jul 2026 14:12:58 +0000This incident has been resolved. A subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected.https://stspg.io/yht3lc3nr2g8vercel:2026-07-16T23:09:29.838ZThu, 16 Jul 2026 23:09:29 +0000This incident has been resolved.https://stspg.io/yzqkkrl8lw0mvercel:2026-07-16T08:39:35.000ZThu, 16 Jul 2026 08:39:35 +0000This incident has been resolved.https://stspg.io/v9m67w60bdjkvercel:2026-07-16T06:07:15.195ZThu, 16 Jul 2026 06:07:15 +0000The 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.https://stspg.io/dz3d8c79b47jvercel:2026-07-15T23:04:43.157ZWed, 15 Jul 2026 23:04:43 +0000This incident has been resolved.https://stspg.io/7r7v7fr4bhbpvercel:2026-07-10T21:22:09.000ZFri, 10 Jul 2026 21:22:09 +0000This incident has been resolved.https://stspg.io/274dc78rzc6qvercel:2026-07-10T19:15:53.346ZFri, 10 Jul 2026 19:15:53 +0000We have unpaused all impacted deployments. We will continue to monitor the situation.https://stspg.io/lwv762xftprnvercel:2026-07-09T13:16:00.000ZThu, 09 Jul 2026 13:16:00 +0000The 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.https://stspg.io/6p93bsts8r9yvercel:2026-07-08T18:05:09.202ZWed, 08 Jul 2026 18:05:09 +0000This incident has been resolved.https://stspg.io/k50rhwbpqxwqvercel:2026-07-02T16:31:55.765ZThu, 02 Jul 2026 16:31:55 +0000This incident has been resolved.https://stspg.io/q6nb60k20jgdvercel:2026-07-01T16:57:02.933ZWed, 01 Jul 2026 16:57:02 +0000The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected. Affected workflow runs have been recovered where possible. Runs that could be resumed safely were resumed and runs that could not be resumed safely were transitioned to a cancelled state.https://stspg.io/mv7d6s5y2w5qvercel:2026-06-26T13:08:09.000ZFri, 26 Jun 2026 13:08:09 +0000This incident has been resolved.https://stspg.io/6rjcs694wc3svercel:2026-06-25T07:45:00.625ZThu, 25 Jun 2026 07:45:00 +0000This incident has been resolved.https://stspg.io/4wq1dnwtkzfgvercel:2026-06-23T23:24:24.620ZTue, 23 Jun 2026 23:24:24 +0000This incident has been resolved.https://stspg.io/clqq0f551l8mvercel:2026-06-19T17:54:16.000ZFri, 19 Jun 2026 17:54:16 +0000Between Jun 19 09:09 and 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.