Zero day exploits are written about all of the time - there are 2.93 million hits on google for "zero day" and 314,000 for zero+day+exploit. Saturday of this weekend was the UK's first O day (and the ones exploited were early iPhone adopters):
- O2's servers fell over under the load of iPhone 3G activation. An eminently predictable event - one that should have seen months of planning - resulted in a Black Swan day for O2. The probability of high take up of the new iPhone was known, but the consequences were not well predicted. Nassim Nicholas Taleb can add this case study to his next book. O2 can perhaps be known just as "O" for the next few days.
- Oyster cards across London fell into disuse as the central unit that operates them fell over. I had no idea these were run by some central server - I always figured that the card only talked to the local reader during the transaction and that perhaps there was some kind of bulk upload of transactions periodically or even once a day. Every system has a bad day - and Oyster's seem few and far between - but for a multi-hour outage to occur? (Don't worry folks, David Frost would have been unaffected - Freedom passes are still paper-based)
Olympics organisers had better watch out. These are good examples of how not to demonstrate the capability of our infrastructure to respond to high load events.