Did you feel the earthquake yesterday? Here in Massachusetts, the uTest headquarters is still standing and everything remains in its place. However, the momentary rattle sure caused load problems across media websites and cellular connections.
Several people reported that Boston.com’s website was down during periods of time after the quake. In addition, Engadget reported cell phone and landline service crashes:
“Verizon Wireless has released the following statement on Twitter: ‘Seeing no reports of damage to our wireless network. There was some network congestion in the East after tremors. Continuing to monitor.’
T-Mobile was feeling left out and sent us an email: ‘T-Mobile’s network is experiencing higher call volumes in all areas and counties affected by the earthquake. If customers are experiencing temporary difficultly placing calls due to network congestion, we advise them to use SMS or E-Mail until call volumes return to normal.’”
All types of software and technology should be in-the-wild tested for load problems. While earthquakes may not happen often – there are countless different kinds of events that could take place and cause serious network and web congestion. By in-the-wild testing to make sure your app functions under peak loads, you can avoid discouraged customers when a real world event does occur.
Did you experience any post-quake issues? Let us know in the comments section.