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
https://status.aws.amazon.com/ Looks like: We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region. --Anthony Hook On Tue, Feb 28, 2017 at 12:04 PM 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
A German IT site is claiming it's a DDOS but didn't provide evidence. Some others are claiming they get sporadic S3 access. On Tue, Feb 28, 2017 at 11:07 AM, Anthony Hook <anthony.hook3@gmail.com> wrote:
https://status.aws.amazon.com/
Looks like: We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.
--Anthony Hook
On Tue, Feb 28, 2017 at 12:04 PM 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
-- Carlos Alvarez 602-368-6403
TCP connect to us-east-1 endpoints fail from everywhere for everyone, including from an EC2 instance in same region. Not related to location of user or the bucket/key being accessed. https://pulse.turbobytes.com/results/58b5caafecbe402e2100c0bb/ "increased error rates" = 100% error rates. On Wed, Mar 1, 2017 at 1:58 AM Carlos Alvarez via Outages < outages@outages.org> wrote:
A German IT site is claiming it's a DDOS but didn't provide evidence. Some others are claiming they get sporadic S3 access.
On Tue, Feb 28, 2017 at 11:07 AM, Anthony Hook <anthony.hook3@gmail.com> wrote:
https://status.aws.amazon.com/
Looks like: We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.
--Anthony Hook
On Tue, Feb 28, 2017 at 12:04 PM 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
-- Carlos Alvarez 602-368-6403 <(602)%20368-6403>
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Experiencing major issues accessing sites I know to be using S3 from the Chicago area. From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Anthony Hook via Outages Sent: Tuesday, February 28, 2017 12:07 PM To: Carlos Alvarez; outages@outages.org Subject: Re: [outages] Amazon S3 down https://status.aws.amazon.com/ Looks like: We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region. --Anthony Hook On Tue, Feb 28, 2017 at 12:04 PM 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:(602)%20368-6403> _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
Down from San Antonio, TX. ------------------------------- Bruce Orcutt UTSA Libraries: Systems Office: (210) 458-6192 Cell: (210) 338-0557 From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Sneath, Dustin via Outages Sent: Tuesday, February 28, 2017 12:16 PM To: Anthony Hook <anthony.hook3@gmail.com>; Carlos Alvarez <carlos@initiatel.com> Cc: outages@outages.org Subject: Re: [outages] Amazon S3 down Experiencing major issues accessing sites I know to be using S3 from the Chicago area. From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Anthony Hook via Outages Sent: Tuesday, February 28, 2017 12:07 PM To: Carlos Alvarez; outages@outages.org<mailto:outages@outages.org> Subject: Re: [outages] Amazon S3 down https://status.aws.amazon.com/ Looks like: We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region. --Anthony Hook On Tue, Feb 28, 2017 at 12:04 PM 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:(602)%20368-6403> _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
Status page claims S3 errors are resolved, although detail area shows “increased error rates” for several services at this moment. -- TTFN, patrick
On Feb 28, 2017, at 3:12 PM, Bruce Orcutt via Outages <outages@outages.org> wrote:
Down from San Antonio, TX.
------------------------------- Bruce Orcutt UTSA Libraries: Systems Office: (210) 458-6192 Cell: (210) 338-0557
From: Outages [mailto:outages-bounces@outages.org <mailto:outages-bounces@outages.org>] On Behalf Of Sneath, Dustin via Outages Sent: Tuesday, February 28, 2017 12:16 PM To: Anthony Hook <anthony.hook3@gmail.com <mailto:anthony.hook3@gmail.com>>; Carlos Alvarez <carlos@initiatel.com <mailto:carlos@initiatel.com>> Cc: outages@outages.org <mailto:outages@outages.org> Subject: Re: [outages] Amazon S3 down
Experiencing major issues accessing sites I know to be using S3 from the Chicago area.
From: Outages [mailto:outages-bounces@outages.org <mailto:outages-bounces@outages.org>] On Behalf Of Anthony Hook via Outages Sent: Tuesday, February 28, 2017 12:07 PM To: Carlos Alvarez; outages@outages.org <mailto:outages@outages.org> Subject: Re: [outages] Amazon S3 down
https://status.aws.amazon.com/ <https://status.aws.amazon.com/>
Looks like: We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.
--Anthony Hook
On Tue, Feb 28, 2017 at 12:04 PM 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:(602)%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>_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages <https://puck.nether.net/mailman/listinfo/outages>
Amazon finally fixed their status page (which apparently depended on S3!), and it looks like a Christmas tree. http://status.aws.amazon.com
On Feb 28, 2017, at 12:15 PM, Sneath, Dustin via Outages <outages@outages.org> wrote:
Experiencing major issues accessing sites I know to be using S3 from the Chicago area.
From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Anthony Hook via Outages Sent: Tuesday, February 28, 2017 12:07 PM To: Carlos Alvarez; outages@outages.org Subject: Re: [outages] Amazon S3 down
https://status.aws.amazon.com/ <https://status.aws.amazon.com/>
Looks like: We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.
--Anthony Hook
On Tue, Feb 28, 2017 at 12:04 PM 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:(602)%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>_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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.ellis@gmail.com) "Oook" -- The Librarian
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.ellis@gmail.com) "Oook" -- The Librarian
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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.ellis@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
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.ellis@gmail.com <mailto:byron.ellis@gmail.com>) "Oook" -- The Librarian
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Someone's having a bad day: :"Update at 11:35 AM PST: We have now repaired the ability to update the service health dashboard." -A On Tue, Feb 28, 2017 at 10:22 AM, Peter Kristolaitis via Outages <outages@outages.org> wrote:
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> 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Byron Ellis (byron.ellis@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
We are starting to see access. I am able to get access to some of my public buckets. Thanks, Bobin Joseph From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Peter Kristolaitis via Outages Sent: Tuesday, February 28, 2017 10:23 AM To: outages@outages.org Subject: Re: [outages] Amazon S3 down 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 -- Byron Ellis (byron.ellis@gmail.com<mailto:byron.ellis@gmail.com>) "Oook" -- The Librarian _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
Also seeing issues with EC2 Auto Scaling Groups and Lambda functions. Getting fun errors like "Status Reason: Insufficient capacity. Launching EC2 instance failed". From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Peter Kristolaitis via Outages Sent: 28 February 2017 18:23 To: outages@outages.org Subject: Re: [outages] Amazon S3 down 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 -- Byron Ellis (byron.ellis@gmail.com<mailto:byron.ellis@gmail.com>) "Oook" -- The Librarian _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
Causing issues at Hubspot as well... Michael Picher, VP of Product Innovation eZuce, Inc. 300 Brickstone Square Suite 104 Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro> www.ezuce.com Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you. FMS On Tue, Feb 28, 2017 at 1:07 PM, 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.ellis@gmail.com) "Oook" -- The Librarian
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
https://goo.gl/dWYJq4 On Tue, Feb 28, 2017 at 12:35 PM, Michael Picher via Outages < outages@outages.org> wrote:
Causing issues at Hubspot as well...
Michael Picher, VP of Product Innovation eZuce, Inc.
300 Brickstone Square
Suite 104
Andover, MA. 01810 O.978-296-1005 X2015 <(978)%20296-1005> M.207-956-0262 <(207)%20956-0262> @mpicher <http://twitter.com/mpicher> linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro> www.ezuce.com
Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you. FMS
On Tue, Feb 28, 2017 at 1:07 PM, 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.ellis@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
-- *John Steele* Ennis Independent School District Network Administrator 972-872-7055 john.steele@ennis.k12.tx.us
Definitely an issue. My company's platform is down too On Tue, Feb 28, 2017 at 6:06 PM 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
-- [image: “audioBoom]*Jake Hayhurst | IT Support Technician* The world’s leading spoken-word audio platform @audioBoom <https://www.twitter.com/audioBoom> | audioBoom.com <https://www.audioboom.com/>
From status.aws.amazon.com
Increased Error Rates We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region. Get::In.touch( name: 'Andrew Herrington, company: 'DigitalOcean', title: 'Linux Administrator', twitter: ['@digitalocean <https://twitter.com/digitalocean>',' @andrewthetechie <https://twitter.com/andrewthetechie>'] ) On Tue, Feb 28, 2017 at 11: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
https://status.aws.amazon.com/ "We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region." On 2/28/2017 12:55 PM, Carlos Alvarez via Outages 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Chris Bromley Cloud Services Systems Administrator TMW Systems Inc. | A TRIMBLE COMPANY www.tmwsystems.com -- This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited.
$currentclient in us-west-2 is having console and external issues intermittently but the internal API was still working at least as far as testing showed. Sent from my iPhone
On Feb 28, 2017, at 10:10 AM, Chris Bromley via Outages <outages@outages.org> wrote:
https://status.aws.amazon.com/
"We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region."
On 2/28/2017 12:55 PM, Carlos Alvarez via Outages 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Chris Bromley Cloud Services Systems Administrator TMW Systems Inc. | A TRIMBLE COMPANY www.tmwsystems.com
This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Amazon's twitter: "The dashboard not changing color is related to S3 issue. See the banner at the top of the dashboard for updates" Tony On Tue, Feb 28, 2017 at 11:10 AM, Chris Bromley via Outages < outages@outages.org> wrote:
https://status.aws.amazon.com/
"We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region."
On 2/28/2017 12:55 PM, Carlos Alvarez via Outages 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 listOutages@outages.orghttps://puck.nether.net/mailman/listinfo/outages
-- Chris Bromley Cloud Services Systems Administrator TMW Systems Inc. | A TRIMBLE COMPANYwww.tmwsystems.com
This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Tony Gagliardi - https://appliedtrust.com/tony-gagliardi <https://appliedtrust.com/company/bios/tony-gagliardi> AppliedTrust - https://appliedtrust.com - 303.245.4530
Confirmed here in East Texas. Multiple sites down. Amazon S3 in the Eastern US reporting errors. https://status.aws.amazon.com/ On Tue, Feb 28, 2017 at 11: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
-- Thank you, *Erik Lentz* Network Manager Redwater ISD elentz@redwaterisd.org <elentz@redwaterisd.org> P.O. Box 347 Redwater, Texas 75573 Phone: 903-671-3481 x276 Fax: 903-671-2019
Confirmed down from Internet2 to us-west-2. Britton Anderson <blanderson3@alaska.edu> | Lead Network Communications Specialist | University of Alaska <http://www.alaska.edu/oit> | 907.450.8250 On Tue, Feb 28, 2017 at 9:10 AM, Erik Lentz via Outages <outages@outages.org
wrote:
Confirmed here in East Texas. Multiple sites down. Amazon S3 in the Eastern US reporting errors. https://status.aws.amazon.com/
On Tue, Feb 28, 2017 at 11: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
-- Thank you,
*Erik Lentz* Network Manager Redwater ISD elentz@redwaterisd.org <elentz@redwaterisd.org> P.O. Box 347 Redwater, Texas 75573 Phone: 903-671-3481 x276 Fax: 903-671-2019 <(903)%20671-2019>
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
This also seems to be totally hosing Heroku, just their login page dies due to being unable to reach something on S3. — Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet www.bway.net spork@bway.net - 212.982.9800
On Feb 28, 2017, at 1:10 PM, Erik Lentz via Outages <outages@outages.org> wrote:
Confirmed here in East Texas. Multiple sites down. Amazon S3 in the Eastern US reporting errors. https://status.aws.amazon.com/ <https://status.aws.amazon.com/>
On Tue, Feb 28, 2017 at 11: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:(602)%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>
-- Thank you,
Erik Lentz Network Manager Redwater ISD elentz@redwaterisd.org <mailto:elentz@redwaterisd.org> P.O. Box 347 Redwater, Texas 75573 Phone: 903-671-3481 x276 Fax: 903-671-2019
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
We are also seeing timeouts. This is from the status page: Increased Error Rates We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region. On 2/28/17 10:55 AM, Carlos Alvarez via Outages 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
The dashboard not changing color is related to S3 issue. See the banner at the top of the dashboard for updates.
https://twitter.com/awscloud/status/836656664635846656 On Tue, Feb 28, 2017 at 10:11 AM, Geoffrey Mina via Outages < outages@outages.org> wrote:
We are also seeing timeouts. This is from the status page:
Increased Error Rates
We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.
On 2/28/17 10:55 AM, Carlos Alvarez via Outages 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 listOutages@outages.orghttps://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
As one person put it: Unfortunately, AWS choose to host their red X status icon on S3. ☺ (@platypii on twitter) Good news, looks like things are resolved now, and back up. ------------------------------- Bruce Orcutt UTSA Libraries: Systems Office: (210) 458-6192 Cell: (210) 338-0557 From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Samson Yeung via Outages Sent: Tuesday, February 28, 2017 1:50 PM To: Geoffrey Mina <gmina@connectfirst.com> Cc: outages@outages.org Subject: Re: [outages] Amazon S3 down The dashboard not changing color is related to S3 issue. See the banner at the top of the dashboard for updates. https://twitter.com/awscloud/status/836656664635846656 On Tue, Feb 28, 2017 at 10:11 AM, Geoffrey Mina via Outages <outages@outages.org<mailto:outages@outages.org>> wrote: We are also seeing timeouts. This is from the status page: Increased Error Rates We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region. On 2/28/17 10:55 AM, Carlos Alvarez via Outages 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:(602)%20368-6403> _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
http://status.aws.amazon.com/? says high error rates in US-east-1 [cid:58e0dc0f-f217-436e-bfb7-9b1bd0de6c25] Thanks, Bobin Sent from webmail ________________________________ From: Outages <outages-bounces@outages.org> on behalf of Carlos Alvarez via Outages <outages@outages.org> Sent: Tuesday, February 28, 2017 9:55 AM To: outages@outages.org Subject: [outages] Amazon S3 down 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
Also reported by Desk.com (Salesforce) that attachments cannot be opened or downloaded from their platform for the same reason. 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Michael Acosta
From http://status.aws.amazon.com/: Increased Error Rates
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 Tue, Feb 28, 2017 at 1:04 PM 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
Looks like SiriusXM web streaming is down - seems to have went down about same time as I saw this message thread may be related... On Tue, Feb 28, 2017 at 12:55 PM, 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
It appears things are starting to come back online. I tested content I have hosted in S3 and it is now accessible, it was not accessible 10 minutes ago. On Tue, Feb 28, 2017 at 1:28 PM, Rich Davies via Outages < outages@outages.org> wrote:
Looks like SiriusXM web streaming is down - seems to have went down about same time as I saw this message thread may be related...
On Tue, Feb 28, 2017 at 12:55 PM, 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- [image: --] Keith I Myers [image: http://]http://KMyers.me +Keith I Myers <http://plus.kmyers.me/> Mobile : (305)-929-3475
We're beginning to see recovery here. Ryan Prihoda Systems Administrator dynaConnections 512.306.9898 ext 107 1101 S. Capital of TX Hwy. Bldg. H., Suite 130 Austin, Texas 78746 rprihoda@dynaconnections.com www.dynaconnections.com On 02/28/2017 11:55 AM, Carlos Alvarez via Outages 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Same here. We were more or less back up about 2 hours ago. On 1 Mar 2017 12:10 a.m., "Ryan Prihoda via Outages" <outages@outages.org> wrote:
We're beginning to see recovery here.
Ryan Prihoda Systems Administrator
dynaConnections512.306.9898 ext 107 <(512)%20306-9898> 1101 S. Capital of TX Hwy. Bldg. H., Suite 130 Austin, Texas 78746rprihoda@dynaconnections.comwww.dynaconnections.com
On 02/28/2017 11:55 AM, Carlos Alvarez via Outages 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 listOutages@outages.orghttps://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Well, that makes *two* post-mortems I look forward to reading about this month: the Oscar night best picture kerfuffle, and now this Amazon outage. Brad Chapman Mac Systems Engineer NBCUniversal From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Jake Hayhurst via Outages Sent: Tuesday, February 28, 2017 4:12 PM To: Ryan Prihoda <rprihoda@dynaconnections.com> Cc: outages@outages.org Subject: Re: [outages] Amazon S3 down Same here. We were more or less back up about 2 hours ago. On 1 Mar 2017 12:10 a.m., "Ryan Prihoda via Outages" <outages@outages.org<mailto:outages@outages.org>> wrote: We're beginning to see recovery here. Ryan Prihoda Systems Administrator dynaConnections 512.306.9898 ext 107<tel:(512)%20306-9898> 1101 S. Capital of TX Hwy. Bldg. H., Suite 130 Austin, Texas 78746 rprihoda@dynaconnections.com<mailto:rprihoda@dynaconnections.com> www.dynaconnections.com<http://www.dynaconnections.com> On 02/28/2017 11:55 AM, Carlos Alvarez via Outages 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:(602)%20368-6403> _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
RFO: https://aws.amazon.com/message/41926/ On Wed, Mar 1, 2017 at 11:44 AM, Chapman, Brad (NBCUniversal) via Outages < outages@outages.org> wrote:
Well, that makes **two** post-mortems I look forward to reading about this month: the Oscar night best picture kerfuffle, and now this Amazon outage.
Brad Chapman
Mac Systems Engineer
NBCUniversal
*From:* Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Jake Hayhurst via Outages *Sent:* Tuesday, February 28, 2017 4:12 PM *To:* Ryan Prihoda <rprihoda@dynaconnections.com> *Cc:* outages@outages.org *Subject:* Re: [outages] Amazon S3 down
Same here. We were more or less back up about 2 hours ago.
On 1 Mar 2017 12:10 a.m., "Ryan Prihoda via Outages" <outages@outages.org> wrote:
We're beginning to see recovery here.
Ryan Prihoda
Systems Administrator
dynaConnections
512.306.9898 ext 107 <(512)%20306-9898>
1101 S. Capital of TX Hwy.
Bldg. H., Suite 130
Austin, Texas 78746
rprihoda@dynaconnections.com
www.dynaconnections.com
On 02/28/2017 11:55 AM, Carlos Alvarez via Outages 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
_______________________________________________ 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
Our cloud services (Trello, Intelex, etc) seem to be working fine now. — CC On Tue, Feb 28, 2017 at 9:07 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
participants (33)
-
Aaron C. de Bruyn -
Andrew Herrington -
Anthony Hook -
Bobin Joseph -
Britton Anderson -
Bruce Orcutt -
Byron Ellis -
Carlos Alvarez -
Chapman, Brad (NBCUniversal) -
Charles Sprickman -
Chris Bromley -
Chris Cummings -
Chris Swingler -
Erik Lentz -
Geoffrey Mina -
George William Herbert -
Grant Ridder -
Jake Hayhurst -
Jay Farrell -
Keith I Myers -
Michael Acosta -
Michael Picher -
Mike -
Patrick W. Gilmore -
Peter Kristolaitis -
Phil Lavin -
Rich Davies -
Ryan Prihoda -
Sajal Kayan -
Samson Yeung -
Sneath, Dustin -
Steele, John -
Tony Gagliardi