Christian Horner's daughter gave him strength to cope with Red Bull axe: Ex-F1 boss reveals how 11-year-old's 'bravery' after her mother died helped him overcome 'brutal' sacking
Investigation launched after large fly-tip found blocking country road
Australian politician Helen Haines loses a leg after horrific attack - as new footage reveals moment LandCruiser reversed following alleged hit
Moment 'murderer' overtakes car 'before hitting headteacher and dragging him under car for 1.3miles' is shown to court
Russell Brand grinned 'like a clown' and told woman 'don't be a spoilsport' as he raped her in a toilet cubicle, court told
Extreme Left-wing activists threaten French-style mayhem on the streets of Britain next month
Japan Launches Historic MMX Sample-Return Mission to Mars' Moon Phobos
Read more of this story at Slashdot.
850 new homes could be built surrounding Wickford beauty spot park
A policeman lobbing a tear-gas grenade down the Metro. Shopkeepers weeping on the streets. And a student who tells me violence is 'legitimate': ROBERT HARDMAN in Paris
DAVID BARRETT: Labour's time bomb of up to 2.2million migrants set to win the right to remain here permanently
Mary Berry's daughter sells her hideaway Oxfordshire mansion for £3.95million
The Outage
At my employer, we use a service called Coveralls, which is a code coverage reporting tool that hooks into your CI pipeline. It takes your lcov reports and gives you some insights, and also makes it easy to cause the CI pipeline to fail if newly added code doesn't have reasonable coverage.
I have no strong feelings about the tool, but on February 24th, our CI jobs started failing, and our CI step that talked to Coveralls was the culprit. Coveralls had gone down. That happened to us, and a lot of other people. It was a widespread outage impacting anybody who used their service.
Coveralls actively published updates as the outage dragged on, and boy, did it drag on. Between them posting nearly identical updates minutes or even seconds apart and the general desperation that snuck into their outage notes after the first few days, I couldn't help but find their notes hilarious.
They've published their post-mortem, and the short version is that despite them paying their bills, Amazon decided they hadn't, and shut down their services. But it took them roughly 68 hours to figure that out.
If you scroll down past the post-mortem, you can see their outage notes. This is an unauthorized, dramatic reading of those notes. We've taken some liberties in interpreting it.
I hope this is taken in a good spirit, because they were just doing their best when this happened. I don't think most companies would be able to maintain operations when their cloud provider decides to lock their accounts. But I don't care who you are: begging your users to email you if they can help you migrate off AWS is funny.