minor impact Vercel โœ“ Resolved

Elevated Errors on Middleware Invocations

Started
2026-03-06 15:25 UTC
Resolved
2026-03-06 21:38 UTC
Duration
373 minutes
Date
2026-03-06

Incident Timeline

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 15:25 UTC

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

identified 2026-03-06 19:18 UTC

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

monitoring 2026-03-06 21:20 UTC

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

resolved 2026-03-06 21:38 UTC

This incident has been resolved.

โ† All Vercel incidents Other incidents on 2026-03-06