There's a chicken/egg joke here somewhere, with regards to the status page relying on S3.
I'll take my comments off the air. On Tue, Feb 28, 2017 at 2:30 PM Grant Ridder via Outages < outages@outages.org> wrote: > Appears that the outage started at 9:45am pacific time. > > -Grant > > On Tue, Feb 28, 2017 at 10:07 AM, Byron Ellis via Outages < > outages@outages.org> 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> 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 <(602)%20368-6403> > > > _______________________________________________ > Outages mailing list > Outages@outages.org > https://puck.nether.net/mailman/listinfo/outages > > > > > -- > Byron Ellis (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 >
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages