Vendor reports: degradedResolved · vendor status “resolved”Official status API

Elevated connection errors in us-east-1

Reported by Ably · Communication & Messaging · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Oct 25, 2026, 21:24 UTC
Vendor's clock
Resolved
Oct 26, 2026, 11:45 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
14 h 21 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

  • Ably reports degraded: "Elevated connection errors in us-east-1".[E1, E2]
  • The vendor marked it resolved at 2026-10-26 11:45 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east-1 (read from the title, so inferred).[E5]
  • Components: US East (Northern Virginia).[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-10-26 11:45 UTC · summary s1, evidence a5f88e0f86f6a8ee

Evidence (7)
  1. E1Ably reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Elevated connection errors in us-east-1". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-10-25 21:24 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-east-1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: US East (Northern Virginia). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-10-26 11:45 UTC. (vendor) source (opens in a new tab)

Affected scope

us-east-1

Components: US East (Northern Virginia)

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

Ably 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.

  1. Oct 25, 2026, 21:24 UTCVendor-reported startVendor time
  2. Oct 26, 2026, 11:45 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.