I was having some major problems with a server that would flip out under heavy load. Turns out it was the specific kernel I was using. Linode support was quite helpful once I actually contacted them about it.
(FYI, I'm asking purely out of curiosity)
The only real solution to this is BGP routing which is complicated to setup and VERY expensive (only big guys do it). Here's some excellent answers on SO: http://serverfault.com/questions/153576/global-high-availabi...
All resolvers cache records for the TTL (or SOA minimum for negative lookups) specified by your authoritative servers.
A solution to this would be to have a round robin DNS to different data centers but that is still plagued if one data center develops a network issue.
If the clients are web browsers they will try the alternative addresses in a record set if the one they pick doesn't respond.
Maybe it's something on your particular rack or node? Have you tried setting up new Linodes in Newark and migrating to those?
I personally haven't had issues with the network in the Dallas DC.
Math FTW!
This is not to say that internal network issues won't happen at any provider on occasion as well, because they certainly will. No network is perfect, least of all the massive system of interconnected networks known as the Internet, and you need to accept and plan for this. To believe or expect otherwise is simply unrealistic.
Just two days back they confirmed one internal outage. See this screenshot: http://imgur.com/jYzuD
Almost every time we contact them about an outage, we get this drup response: "Apologize for inconvenience" which is okay, but they should at least upgrade their infra or take steps to avoid it.
Maybe your acquaintance is not monitoring the deployment with higher frequency. We monitor our stack multiple times every minute.
Why do I have to contact them to be told they are having an issue? Why can't they let me know asap so I can mitigate any problems they are having.
The last issue we had was their backup system was failing and by the time we discovered it, it had been broken for days.
Maybe it is to do with their increased customer base, but earlier these outages were much less frequent and we enjoyed the service.
We own 25+ servers with them and have lately given thought of moving to some other provider. It's their responsive customer service and the pain of migrating everything that has kept us sticking to Linode.