![]() ![]() While we don’t discount the reports of those experiencing problems with their AWS-hosted services yesterday, we saw no evidence to justify a widespread AWS-related outage notice for this event.This tutorial will show you how to post messages to Slack apps using their Incoming Webhook API and the AWS Lambda Function URL.Ī function URL is a dedicated HTTP(S) endpoint for your Lambda function. "Downdector independently verified service issues at AWS during the December event and published a 'widespread outage' alert. To put it in context, Downdetector received about 8,000 total user reports of problems at AWS yesterday, whereas we received over 400,000 user reports during the most recent significant AWS outage on December 16." However, we do not believe there was a widespread service issue on AWS’s platform. "We see a small number of credible reports that some AWS users had issues with their platform yesterday. We often find that minor problems impacting a small group of users will go unnoticed on internal monitoring systems, and Downdetector can help point the way to the source of the problem." "Downdetector provides a view of service availability from the perspective of the users of that platform, using data reported by users themselves. Here's what Luke Deryckx, Ookla CTO, had to say: However, the firm also noted that the nature of the platform means Downdetector is often better at noticing small-scale problems that affect only a small pool of users, which may otherwise be missed by internal monitoring. Ookla, the company that owns Downdetector, told us that the widespread outage at Slack (a known AWS customer) may have been misdiagnosed by some users as a problem on the end of the cloud provider. We've been doing some digging around what may have caused the discrepancy between the reporting on Downdetector and the official word coming out of AWS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |