Vendor reports: operationalResolved · vendor status “resolved”Official status API
Failures delivering Logs to Drains
Reported by Vercel · Hosting, CDN & Edge · source last read just now
- Vendor start
- Sep 17, 2026, 07:11 UTC
- Vendor's clock
- Resolved
- Sep 17, 2026, 07:11 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- Not available
- Needs both vendor times
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
What is unknown
Last update in these facts: 2026-09-17 07:11 UTC · summary s1, evidence 8cc136e39fa5b6cc
Evidence (7)
- E1Vercel reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Failures delivering Logs to Drains". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-09-17 07:11 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2026-09-17 07:11 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
The vendor's feed gives no region for this incident. It is not assumed to be global.
Potential relevance
Vercel is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Sep 17, 2026, 07:11 UTCVendor-reported startVendor time
- Sep 17, 2026, 07:11 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.