Vendor reports: degradedResolved · vendor status “resolved”Vendor incident feed · inferred
Degraded Performance: Uptime and API Checks in us-east-1
Reported by Checkly · Observability & Incident · source last read 2 min ago
- Vendor posted
- Oct 7, 2026, 19:31 UTC
- When the vendor's feed dated it
- Resolved
- Oct 7, 2026, 22:40 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- Not available
- This source does not publish reliable durations
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Regions: us-east-1 (read from the title, so inferred).[E5]
What is unknown
- Which components are affected: the vendor did not say.[E6]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-10-07 22:40 UTC · summary s1, evidence 29218bb5b735973a
Evidence (7)
- E1Checkly reports degraded. (vendor) source (opens in a new tab)
- E2Vendor title: "Degraded Performance: Uptime and API Checks in us-east-1". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor posted it: 2026-10-07 19:31 UTC. (vendor) source (opens in a new tab)
- E5Regions written in the title (inferred): us-east-1. (Statuswall) source (opens in a new tab)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2026-10-07 22:40 UTC. (vendor) source (opens in a new tab)
Affected scope
us-east-1
Components: not stated by the vendor
Read from region codes written in the incident title, so treat it as inferred.
Potential relevance
Checkly 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.
- Oct 7, 2026, 19:31 UTCVendor posted this incidentVendor time
- Oct 7, 2026, 22:40 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.