G
А можно ссылку потом?
Size: a a a
2020 November 26
G
Конечно, утром запосчу и закину. Без ноута уже сижу.
👍
G
Когда на сердце тяжесть
И холодно в груди,
К провайдеру в контору
Ты в сумерках приди,
Где без питья и хлеба,
Забытые в веках,
Админы сервер держат
В слабеющих руках!
Админы сервер держат
В слабеющих руках.
И холодно в груди,
К провайдеру в контору
Ты в сумерках приди,
Где без питья и хлеба,
Забытые в веках,
Админы сервер держат
В слабеющих руках!
Админы сервер держат
В слабеющих руках.
Это тоже хорошее. Сразу гитарка, ночь, костер, плеск реки...
G
Это Боян:)
Я не встречал)
☁
Service: AWS IoT Core
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#awsiot-us-east-1_1606345901
We continue to experience increased latency and failure rates for Connect and Subscribe operations in the US-EAST-1 region. Messaging on existing connections and Shadow operations continue to operate normally. We have identified the root cause and continue to work towards resolution.
#awsiot #useast1
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#awsiot-us-east-1_1606345901
We continue to experience increased latency and failure rates for Connect and Subscribe operations in the US-EAST-1 region. Messaging on existing connections and Shadow operations continue to operate normally. We have identified the root cause and continue to work towards resolution.
#awsiot #useast1
☁
Service: Amazon EventBridge
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#events-us-east-1_1606346647
We have identified the root cause of elevated API errors and latencies in the US-EAST-1 Region and have begun implementing mitigations resulting in partial recovery. We continue to see elevated error rates and latency on API calls to PutEvents. Additionally, for Rules subscribing to Events from other AWS Services, latency is recovering but still elevated. We are continuing to work towards full resolution.
#events #useast1
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#events-us-east-1_1606346647
We have identified the root cause of elevated API errors and latencies in the US-EAST-1 Region and have begun implementing mitigations resulting in partial recovery. We continue to see elevated error rates and latency on API calls to PutEvents. Additionally, for Rules subscribing to Events from other AWS Services, latency is recovering but still elevated. We are continuing to work towards full resolution.
#events #useast1
☁
Service: AWS Batch
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#batch-us-east-1_1606346634
We are beginning to see recovery for the elevated job state transition times in the US-EAST-1 Region, and continue to work toward full resolution.
#batch #useast1
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#batch-us-east-1_1606346634
We are beginning to see recovery for the elevated job state transition times in the US-EAST-1 Region, and continue to work toward full resolution.
#batch #useast1
☁
Service: Amazon CloudWatch
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#cloudwatch-us-east-1_1606347729
We continue to experience increased error rates impacting the PutMetricData API error rates, and delayed Cloudwatch metrics. We expect to begin seeing recovery once the on-going Kinesis issue is fully resolved. Once we have observed recovery, metrics will backfill if they were queued during the impact
#cloudwatch #useast1
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#cloudwatch-us-east-1_1606347729
We continue to experience increased error rates impacting the PutMetricData API error rates, and delayed Cloudwatch metrics. We expect to begin seeing recovery once the on-going Kinesis issue is fully resolved. Once we have observed recovery, metrics will backfill if they were queued during the impact
#cloudwatch #useast1
АП
Во блин адище, сегодня же индюшкин дэй
Да для любого дня это ад. Репетиция большой пятницы так сказать.
АП
Вряд ли этого хватит чтобы уронить целый регион. Но кто знает, без пост мотртема мы не узнаем.
☁
Service: Amazon EventBridge
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#events-us-east-1_1606349049
We have identified the root cause of elevated API errors and latencies in the US-EAST-1 Region and have implemented mitigations resulting in significant improvement in error rates and latency on the PutEvents API. We continue to see delays in Rules subscribing to Events from other AWS Services and are working towards full resolution.
#events #useast1
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#events-us-east-1_1606349049
We have identified the root cause of elevated API errors and latencies in the US-EAST-1 Region and have implemented mitigations resulting in significant improvement in error rates and latency on the PutEvents API. We continue to see delays in Rules subscribing to Events from other AWS Services and are working towards full resolution.
#events #useast1
☁
Service: AWS Batch
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#batch-us-east-1_1606349483
We continue to see some recovery for the elevated job state transition times in the US-EAST-1 Region, and are working toward full resolution.
#batch #useast1
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#batch-us-east-1_1606349483
We continue to see some recovery for the elevated job state transition times in the US-EAST-1 Region, and are working toward full resolution.
#batch #useast1