Christopher Bradbury discovered his firm's websites and client email accounts had vanished from the internet when AWS suspended his Route 53 account due to unpaid invoices stemming from an expired credit card. Critical payment reminders from AWS had been caught by spam filters and routed to a former employee, leaving him unaware of the imminent deadline. The outage exposed a cascade of preventable vulnerabilities in his account setup.

When Bradbury attempted to regain access and resolve the situation, he found himself trapped by interconnected failures: his two-factor authentication depended on an older laptop whose motherboard had failed, forcing him to rely on recovery emails sent to an address that lived on a suspended domain, creating an impossible verification loop. Although he contacted AWS support and even purchased business-tier assistance, support teams could not complete ownership verification or unlock the account. Days passed before he finally managed to pay the outstanding balance and restore service.