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

AWS US-East-1 connectivity issues

Reported by Engine Yard · Cloud & Infrastructure · source last read 2 min ago

Vendor start
Jul 27, 2017, 14:11 UTC
Vendor's clock
Resolved
Jul 27, 2017, 14:20 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 03:40 UTC
Statuswall's clock
Duration
10 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

  • Engine Yard reports degraded: "AWS US-East-1 connectivity issues".[E1, E2]
  • The vendor marked it resolved at 2017-07-27 14:20 UTC.[E3, E7]

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-11-11 03:40 UTC · summary s1, evidence 15b1377eff584dd0

Evidence (8)
  1. E1Engine Yard reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "AWS US-East-1 connectivity issues". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2017-07-27 14:11 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. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2017-07-27 14:20 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 03:40 UTC. (Statuswall)

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

Engine Yard 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. Jul 27, 2017, 14:11 UTCVendor-reported startVendor time
  2. Jul 27, 2017, 14:20 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 03:40 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall