Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



You’d be right to think that Tesla’s technology surely wouldn’t go wrong, especially with the huge amounts of media coverage it gets. But in 2021, Tesla suffered a few awkward technological faults.
You may have read that Tesla went offline which lead to customers around the world reporting issues around gaining access to their cars. It may sound comical seeing someone struggling to access their car but imagine the frustration; lateness to work, to appointments, to important life tasks. So is this something we should come to expect with many vehicles becoming keyless?
Manufacturers are becoming more and more technology-dependent with many vehicles now being managed through apps so there will be times when the technology will not work as well as we expect it to work, just like online websites, for example.
TESLA had recently launched a new update on their app which is used by most customers to access and manage their vehicle usage and needs. Through the app customers can use the phone as a key to unlock and lock the car, access service information and also buy and upgrade their packages. It was suspected that this update caused a domino-effect of issues, which were first reported in US and Canada but soon Europe and Asia started to report the same problem.
It was first reported in the US by Tesla customers after they attempted to get in the car but quite simply, found that they couldn’t. Once they managed to access their car, they found out that they couldn’t start it. The car was “offline” and not responding to any requests. Subsequently, the same issue was then reported across the world, with some very unhappy customers.
Across social media Tesla owners were flooding the pages with issues they were experiencing, and lucky for them it also meant that Tesla staff were also made aware of the issue. They soon posted an update to let all their customers know they were working on the issue and and trying to get a fix in place.
Many things can cause an outage, but when you have thousands of customers dependant on you to find a solution, you need to work quickly. Because Tesla had recently launched their app update to improve customer experience (the irony), it was suspected that this was the root cause for the outage. After an hour or so of investigation, Tesla found that it was the upgrade that had caused this huge technical fault and you know it’s serious when Elon Musk himself takes to Twitter to give an update:
“Should be coming back online now. Looks like we may have accidentally increased verbosity of network traffic”
True to his word. the network was back online soon after but this now begs the question – should Tesla risk doing this sort of upgrade globally without checking if their network can actually handle the changes and the pressure that their servers wil be experiencing. Elon also stated that “we will take measure to ensure this doesn’t happen again” but how true this is is yet to be determined!
What we can learn from this story is that no company is “too big” to have technical issues such as network outages or app upgrades that prove detrimental. I guess we should all start with the basics on this one and make sure that we monitor our network to avoid any prolong outages. In this instant, Tesla managed the situation well and got a fix live quickly but not every company has that capacity. It might we worth them launching any updates in a smaller number to help identify any potential issues before doing a global update.
Share this
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
Find out everything you need to know in our new uptime monitoring whitepaper 2021