Also confirmed. I'm unable to load the S3 management console for at
least one of my accounts. I just get:
{
"errorCode" : "InternalError"
}
Amazon has updated their status page to read "We've identified the issue
as high error rates with S3 in US-EAST-1, which is also impacting
applications and services dependent on S3. We are actively working on
remediating the issue."
On 2/28/2017 1:07 PM, Byron Ellis via Outages wrote:
Confirmed. We are experiencing a complete S3 outage and have confirmed
with several other companies as well that their buckets are also
unavailable. At last check S3 status pages were showing green on AWS,
but it isn't even available through the AWS console.
On Tue, Feb 28, 2017 at 9:55 AM, Carlos Alvarez via Outages
<outages@outages.org <mailto:outages@outages.org>> wrote:
We are unable to reach it from Cox cable, Highwinds, or Cogent
from the Phoenix area. Also several of the outage testing sites
say it's down.
--
Carlos Alvarez
602-368-6403 <tel:%28602%29%20368-6403>
_______________________________________________
Outages mailing list
Outages@outages.org <mailto:Outages@outages.org>
https://puck.nether.net/mailman/listinfo/outages
<https://puck.nether.net/mailman/listinfo/outages>
--
Byron Ellis (byron.el...@gmail.com <mailto:byron.el...@gmail.com>)
"Oook" -- The Librarian
_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
