Tesla is having some big network issues

[68Charger]

Exactly.

This Tesla cloud based system, one of if not THE first of it's kind, has been in place for half a dozen years now and this is the first hiccup it's experienced and we're all supposed to be scared back to driving stage coaches? I only wish my other cloud based accounts were anywhere near as reliable. It should be noted that your phone will still unlock and start the car since it communicates with trusted connections locally w/o the need to "phone home" to verify. The only issue is that you may not be able to remotely "start" your car (not even a thing w/Teslas really) to cool or heat the cabin to the temperature you set.

This is much ado about nothing & about as click baity as things get IMO.

The exact implementation of what they're doing (EV with those specific components), but they're not inventing the wheel... embedded code has been used on many systems, not just on automobiles.

So did it not inconvenience you in the slightest on daily use of your Tesla?

Running a single datacenter is just a ticking timebomb for full out failure- that's no DR plan whatsoever. All it would take is one significant local event (think like Hurricane Sandy), and it's all offline for DAYS to WEEKS.
Maybe they're working on a new datacenter, but IMHO it's good to have critical thinking that reveals the "man behind the curtain" rather than just blindly trusting and worshiping.... after all, he is just a man.

[O2HeN2]

Running a single datacenter is just a ticking timebomb for full out failure- that's no DR plan whatsoever.

About redundancy: I worked on a project whose DR datacenters were fairly close to, and on either side of the San Andreas fault in the bay area.

Back in my DEC (Digital Equipment Corporation) days we had a customer who ran DR datacenters in buildings 1 and 2 of the World Trade Center. In one day that company's personnel and data ceased to exist.

My last project had DR running between the bay area, Colorado Springs and Boise. In terms of disasters we talked earthquakes, nukes and volcanoes.

O2

[68Charger]

About redundancy: I worked on a project whose DR datacenters were fairly close to, and on either side of the San Andreas fault in the bay area.

Back in my DEC (Digital Equipment Corporation) days we had a customer who ran DR datacenters in buildings 1 and 2 of the World Trade Center. In one day that company's personnel and data ceased to exist.

My last project had DR running between the bay area, Colorado Springs and Boise. In terms of disasters we talked earthquakes, nukes and volcanoes.

O2

Prime examples of redundancy without diversity... I've also seen well done diverse backup systems where the backup was not monitored... had been down for months when the primary failed.

Mention of DEC takes me back, did a lot of work with them over the years... and a customer with Datacenters in the WTC could have very well been one of our customers, too. That impacted lots of our customers, we worked our asses off before market open after 9/11... our backbone stayed up, but the LEC lost a complete CO in one of the buildings... virtually every customer had another circuit with a CLEC for diversity., but we had many customers back on redundant circuits before that first market day after.

Beancounters are the bane of properly diverse networks... always trying to consolidate equipment, circuits and buildings to save $$$. We'd ask them what would the cost to the company be if we are on the front page of the WSJ because a lack of diversity in the network caused the market to close?

There's also a tradeoff between latency and diversity... "of course the backup path has a higher latency, it can't take the shortest path- that's where the primary is" "no sir, we can't put it on the shortest path too... then they'd both be down right now"