|
|
|
|
|
by griffordson
2607 days ago
|
|
Yes, it is throwing 503s and we're also getting general network failures in other calls to the SQS APIs. As is typical, not a peep from AWS or any indication of what is going on. [Edit 1] And we're seeing the issue in us-east-1 too FYI [Edit 2] They are now reporting the issue in us-east-2 with SQS and Lambda [Edit 3] After looking harder it appears I was wrong about us-east-1. I thought we were seeing failures there but it does seem to be confined to us-east-2 only. [Edit 4] AWS is reporting it is back up and it appears the errors stopped for us at around 1:10pm Central |
|