Chewy102 Posted February 1, 2007 Report Share Posted February 1, 2007 Not been able to access Google for nearly 24 hours now. Is everyone else having the same problems? Link to comment Share on other sites More sharing options...
Mac219 Posted February 1, 2007 Report Share Posted February 1, 2007 WORKS FINE HERE Link to comment Share on other sites More sharing options...
Chewy102 Posted February 1, 2007 Author Report Share Posted February 1, 2007 WORKS FINE HERE Ok thanks. Google is the only website that's not working for me none of the Google sites, .co.uk .com or any of the other countries subsites and bizarrely Google Earth isn't working either. Every other site is loading perfectly normally Link to comment Share on other sites More sharing options...
Chewy102 Posted February 1, 2007 Author Report Share Posted February 1, 2007 Errm got an answer to the problem but not sure it makes anything clearer Google uses a self-healing network, consisting of layers of load balancing at both DNS and inner network level. One Google datacenter IP equals a load balancer with hundreds of thousands of grid servers behind it. When one of these grids gets put under strain or is taken out of the collective for maintenance, the DNS automatically starts pushing traffic to another grid. Not all ISPs will see this change in time and send traffic to a grid which has been taken out of action. This can be further complicated when the ISP's core routers peer directly with the Google network (saving bandwidth costs and TTL times) and have traffic paths/routes hardcoded into their router which may not catch up with changes at Google's end. Link to comment Share on other sites More sharing options...
theboss Posted February 5, 2007 Report Share Posted February 5, 2007 Errm got an answer to the problem but not sure it makes anything clearer Google uses a self-healing network, consisting of layers of load balancing at both DNS and inner network level. One Google datacenter IP equals a load balancer with hundreds of thousands of grid servers behind it. When one of these grids gets put under strain or is taken out of the collective for maintenance, the DNS automatically starts pushing traffic to another grid. Not all ISPs will see this change in time and send traffic to a grid which has been taken out of action. This can be further complicated when the ISP's core routers peer directly with the Google network (saving bandwidth costs and TTL times) and have traffic paths/routes hardcoded into their router which may not catch up with changes at Google's end. Makes complete sense Link to comment Share on other sites More sharing options...
Recommended Posts