On October 20th, 2025, the world awoke offline. A DNS issue blocked the internet worldwide, blocking access to Amazon Web Services (AWS). Amazon defines DNS as “DNS, or the Domain Name System, translates human readable domain names (for example, http://www.amazon.com) to machine readable IP addresses (for example, 192.0.2.44),” (AWS, 2025). The DNS issue has now affected the majority of digital applications affiliated with AWS, including student, business, and entertainment services. The global outage reveals the ineffectiveness of centralizing of all web applications to integrate with Amazon Web Services. Additionally, it displays a need for alternative entities to create similar services to compete with the digital behemoth.
Canvas currently remains inaccessible, placing many students’ assignments in jeopardy. Specifically, Canvas’s Website reads “Canvas is experiencing issues due to an ongoing AWS incident. We are working on recovering as soon as possible. You can follow the status of the issue at https://health.aws.amazon.com/health/status,” (Canvas, 2025). Now, students must wait for the DNS outage to be corrected before courses and their assignments can be viewed. There is no estimated time of restoration.
Further outages include Blackboard, Canva, Hulu, Disney+, HBO, Venmo, Verizon, Snapchat, Amazon, Microsoft, Zoom, Tidal, Apple Music, Pintrest, Adobe Creative Cloud, Ring, Blink, Duolingo, Chime, Instacart, Robinhood, Webull, Vangaurd, Meetup, Uber and Lyft, (DownDetector, 2025). Amazon Web Service boasts a “scale and fail independently” feature that allows for the Decoupling [of] app with application integration services allow[ing] them to remain interoperable, but if one service has a failure or spike in workload, it won’t affect the rest of them,” (AWS). But it does not warn of the risks involving AWS DNS issues that may result in the total inoperability of the service. Thus, it provides further evidence that the centralization of applications to integrate with AWS is ineffectual and should be decentralized and unconsolidated.
Despite the mass outages across the internet, Scripture reminds us “[d]on’t worry about anything; instead, pray about everything. Tell God what you need, and thank him for all he has done,” (Philippians 4:6; NLT). Succumbing to the overwhelming concern of this global internet outage will only escalate individual stress, and will not expedite the resurgence of Amazon Web Services.
In sum, the world awaits a timely remedy; the longer this outage occurs the more detrimental its impact. Instances like this reveal the human reliance on technology, particularly access to the internet. Moreover, it reinforces the need for decentralized servers and a means of alternative access to essential applications. Additionally, it displays the hegemony Amazon possesses over all other web applications and online services.
References
AWS. (Accessed on October 20th, 2025). https://aws.amazon.com/route53/what-is-dns/
Canvas. (Accessed on October 20th, 2025). https://canvas.liberty.edu/
DownDetector. (Accessed on October 20th, 2025). https://downdetector.com/
Health.AWS. (Accessed on October 20th, 2025). https://health.aws.amazon.com/health/status
Status.Instructure (Accessed on October 20th, 2025). https://status.instructure.com/incidents/rvd23ht9ht9k
Jordan Muhsin 