Part 2/15:
According to detailed reports, the outage was first identified around 10:14 a.m. Eastern Standard Time, with significant API errors originating from AWS's US East 1 region. The impact was immediately felt across various services, many of which displayed degraded performance. AWS initially attributed the initial outage to a DNS issue, which they claimed was fully mitigated by early morning, though some errors persisted as the day progressed. By 11:43 a.m., they announced they had narrowed down the cause and were actively working on mitigation efforts. The online outage tracker DownDetector registered over 8,200 outage reports by midday, illustrating the extensive reach of the problem.