NTL's crazy routing...
so i've finally managed to get access to blogspot.com subdomains again (thanks to a ssh tunnel to a server on another network)!
what follows is speculation based on the various reports on the internet (boards.ie; blogger's help group)...
so it appears sometime in the past week (28feb / 01 mar), a change in NTL's routing policy has resulted in packets destined for blogspot IP space to be routed rather strangely (via various networks which are now owned by virgin)...
connections to ed-in-f191.google.com (aka *.blogspot.com) are killed instantly and no data is returned. to me this suggests that there could be something happening at the server end too.
from the various blog posts and forum postings no-one has convinced NTL to fix it yet so most folk are still without blogspot for the time-being. :(
I've done my bit by emailing the customer support folk in NTL. hopefully they'll read it before replying with "have you tried rebooting your PC". :P
I've also dropped the blogger support team an email to see if they've spotted anything odd their end (though there are a number of threads in the blogger help forum about the issue).
what follows is speculation based on the various reports on the internet (boards.ie; blogger's help group)...
so it appears sometime in the past week (28feb / 01 mar), a change in NTL's routing policy has resulted in packets destined for blogspot IP space to be routed rather strangely (via various networks which are now owned by virgin)...
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| [removed] - 0 | 57 | 57 | 0 | 29 | 110 | 10 |
| [removed].ntlworld.ie - 0 | 57 | 57 | 10 | 27 | 60 | 40 |
| 213.46.165.49 - 0 | 57 | 57 | 10 | 26 | 91 | 30 |
| dbln-bb-a-ae1-0.inet.ntl.com - 0 | 57 | 57 | 20 | 39 | 160 | 70 |
| ren-bb-b-so-100-0.inet.ntl.com - 0 | 57 | 57 | 20 | 41 | 120 | 50 |
| man-bb-a-so-010-0.inet.ntl.com - 0 | 57 | 57 | 20 | 46 | 90 | 81 |
| man-bb-b-ge-000-0.inet.ntl.com - 0 | 57 | 57 | 20 | 43 | 91 | 41 |
| bir-bb-a-so-000-0.inet.ntl.com - 0 | 57 | 57 | 20 | 42 | 120 | 30 |
| florence-pos20.inet.ntl.com - 0 | 57 | 57 | 20 | 38 | 90 | 80 |
| brad-wit-pos.telewest.net - 0 | 57 | 57 | 30 | 52 | 201 | 70 |
| 194.117.136.214 - 0 | 57 | 57 | 30 | 60 | 231 | 50 |
| 194.117.136.209 - 0 | 57 | 57 | 30 | 52 | 190 | 30 |
| kno-kno-cas-pos.telewest.net - 0 | 57 | 57 | 30 | 49 | 311 | 30 |
| pc-62-30-249-14-ha.blueyonder.co.uk - 0 | 57 | 57 | 30 | 56 | 220 | 30 |
| pc-62-31-0-204-nm.blueyonder.co.uk - 0 | 57 | 57 | 30 | 46 | 110 | 40 |
| pc-62-30-249-46-ha.blueyonder.co.uk - 0 | 57 | 57 | 30 | 54 | 251 | 40 |
| 194.117.136.162 - 0 | 57 | 57 | 30 | 52 | 150 | 30 |
| 194.117.148.251 - 0 | 57 | 57 | 30 | 49 | 120 | 40 |
| 72.14.238.255 - 0 | 57 | 57 | 30 | 45 | 120 | 30 |
| 72.14.236.216 - 2 | 57 | 56 | 100 | 121 | 160 | 110 |
| 66.249.94.235 - 0 | 56 | 56 | 120 | 138 | 190 | 140 |
| 72.14.238.138 - 0 | 56 | 56 | 130 | 156 | 220 | 160 |
| 72.14.239.23 - 0 | 56 | 56 | 130 | 156 | 231 | 180 |
| 216.239.43.186 - 0 | 56 | 56 | 140 | 159 | 210 | 160 |
| ed-in-f191.google.com - 0 | 56 | 56 | 130 | 156 | 230 | 160 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )
connections to ed-in-f191.google.com (aka *.blogspot.com) are killed instantly and no data is returned. to me this suggests that there could be something happening at the server end too.
from the various blog posts and forum postings no-one has convinced NTL to fix it yet so most folk are still without blogspot for the time-being. :(
I've done my bit by emailing the customer support folk in NTL. hopefully they'll read it before replying with "have you tried rebooting your PC". :P
I've also dropped the blogger support team an email to see if they've spotted anything odd their end (though there are a number of threads in the blogger help forum about the issue).
Comments