I was ordering fiber optic internet from Frontier Communications—my doctor said I should consume more fiber—but their system said my credit check failed and was demanding an equipment deposit. I pushed back. They ran it three times.
Then they got word in a group chat that Equifax’s consumer and business portals are down, so they can’t process any credit checks.
Woe be unto you if you work in finance or support a business that depends on this service. I hope they didn’t have another breach. Maybe they will need a tiny excavator to dig them out of this mess like that freighter stuck in the Suez canal<https://www.reddit.com/r/CatastrophicFailure/comments/mcw8og/new_pictures_f…> for the last two days...
Cheers,
Brad
https://health.aws.amazon.com/health/status
Service
Multiple services
Severity
Degraded
RSS
Increased Error Rates
Mar 01 7:09 AM PST We wanted to provide some additional information on
the isolated power issue. At this time, most AWS Services have
weighted away from the affected Availability Zone (mec1-az2) and are
seeing recovery for their affected operations and workflows. For EC2
Instances, EBS Volumes, and other resources that are impacted in the
affected Zone, we will have a longer tail of recovery. At this time,
power has not yet been restored to the affected AZ. For now, we
recommend continuing to retry any failed API requests. If immediate
recovery is required, we recommend customers restore from EBS
Snapshots and/or replace affected resources by launching replacement
resources in one of the unaffected zones, or an alternate region. As
of this time, recovery is still several hours away. We will provide an
update by 8:30 AM PST, or sooner if we have additional information to
share.
Mar 01 6:09 AM PST We can confirm that a localized power issue has
affected a single Availability Zone in the ME-CENTRAL-1 Region
(mec1-az2). EC2 Instances, DB Instances, EBS Volumes, and others
resources are currently unavailable and will experience connectivity
issues at this time. Other AWS Services are also experiencing error
rates and latencies for some workflows. We have weighed away traffic
for most services at this time. We recommend customers utilize one of
the other Availability Zones in the ME-CENTRAL-1 Region at this time,
as existing instances in other AZ's remain unaffected by this issue.
We are actively working to restore power and connectivity, at which
time we will begin to work to recover affected resources. As of this
time, we expect recovery is multiple hours away. We will provide an
update by 7:15 AM PST, or sooner if we have additional information to
share.
Mar 01 5:19 AM PST We are investigating connectivity and power issues
affecting APIs and instances in a single Availability Zone (mec1-az2)
in the ME-CENTRAL-1 Region due to a localized power issue. Existing
instances in this zone will also be affected. Other AWS Services may
also be experiencing increased errors and latencies for their
workflows, and we are working to route requests away from this
affected Availability Zone. We recommend customers make use of other
Availability Zones at this time. Targeting new launches using
RunInstances in the remaining AZs should succeed. Existing instances
in the other AZs are not affected.
Mar 01 4:51 AM PST We are investigating issues with AWS services in
the ME-CENTRAL-1 Region.
