Vendor reports: degradedResolved · vendor status “resolved”Official status API
API Routes Degradation
Reported by Snyk · Developer Tools & CI/CD · source last read 3 min ago
- Vendor start
- Jul 14, 2026, 17:56 UTC
- Vendor's clock
- Resolved
- Jul 14, 2026, 20:14 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 2 h 19 min
- From vendor start and resolution
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-07-14 20:14 UTC · summary s1, evidence c4512f0f11a733f4
Evidence (7)
- E1Snyk reports degraded. (vendor) source (opens in a new tab)
- E2Vendor title: "API Routes Degradation". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-07-14 17:56 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-07-14 20:14 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
Snyk 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.
- Jul 14, 2026, 17:56 UTCVendor-reported startVendor time
- Jul 14, 2026, 20:14 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.