AOL 1996 flat-rate pricing login congestion crisis
America Online's switch to unlimited, flat-rate internet access caused such a surge in simultaneous logins and prolonged sessions that millions of subscribers experienced constant busy signals and inability to connect for weeks; AOL later paid refunds under state attorney general settlements.
The damage was public. The root cause was preventable.
America Online's switch to unlimited, flat-rate internet access caused such a surge in simultaneous logins and prolonged sessions that millions of subscribers experienced constant busy signals and inability to connect for weeks; AOL later paid refunds under state attorney general settlements.
What the software actually got wrong
AOL's network and modem-pool capacity, along with the software managing user sessions, had not been provisioned for a world where customers stayed connected far longer once usage-based charges were removed, and the company had not modeled the true scale of the resulting demand.
AOL's network and modem-pool capacity, along with the software...
AOL's network and modem-pool capacity, along with the software managing user sessions, had not been provisioned for a world where customers stayed connected far longer once usage-based charges were removed
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
The company had not modeled the true scale of...
the company had not modeled the true scale of the resulting demand
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.