Cannot Access Certain Websites

[BenT91]

Too long in my opinion will be claiming for this as had a day without internet access near enough 70% of websites wont load!!

[michael48]

---

pippincp wrote:

---

michael48 wrote:
8am monday?! That's not good enough. We had Virgin ADSL before and in the 5 years we had it, we never once had an outtage for any longer than a couple of hours.

---

That could be because VM ADSL uses BT's network.

---

They may well be getting a phone call soon at this rate then!

[apcyberax]

if you have no access at all then that isn;t whats effecting you. this fault is routiong for some sites

[Kouneloz]

It looks like the fault has been resolved for the time being though it could be due to the off-peak period so other will need to confirm tomorrow

I'm now able to access websites which were unreachable before such as:

www.neowin.net

www.apple.com/uk/store

this forum of course and a few more

[nickh]

I see VM have closed the fault, however, it's still not working for me here in St Albans. For example, community.virginmedia.com just times out.  Traceroute as follows:

traceroute to virgin.lithium.com (46.19.168.46), 64 hops max, 52 byte packets
 1  10.0.1.1 (10.0.1.1)  1.914 ms  1.062 ms  1.806 ms
 2 
 3 
 4  nrth-bb-1b-as5-0.network.virginmedia.net (213.105.175.153)  8.833 ms  8.511 ms  21.219 ms
 5  nrth-tmr-2-ae6-0.network.virginmedia.net (213.105.159.34)  6.791 ms  11.578 ms  13.123 ms
 6  tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2)  10.905 ms  13.408 ms  11.786 ms
 7  te3-3.mpd01.lon02.atlas.cogentco.com (130.117.14.141)  12.648 ms  14.480 ms  9.094 ms
 8  te4-7.ccr01.lon02.atlas.cogentco.com (130.117.50.117)  16.845 ms
    te7-2.ccr01.lon02.atlas.cogentco.com (130.117.50.138)  12.456 ms
    te4-7.ccr01.lon02.atlas.cogentco.com (130.117.50.117)  12.607 ms
 9  te9-2.mpd02.lon01.atlas.cogentco.com (130.117.48.153)  11.009 ms  11.425 ms  13.202 ms
10  * te0-3-0-0.mpd22.ams03.atlas.cogentco.com (130.117.1.205)  21.724 ms *
11  * * *
12  te2-1.ccr01.ams07.atlas.cogentco.com (154.54.57.194)  21.588 ms
    te1-1.ccr01.ams07.atlas.cogentco.com (154.54.57.230)  18.812 ms
    te2-1.ccr01.ams07.atlas.cogentco.com (154.54.57.194)  23.528 ms
13  149.6.60.2 (149.6.60.2)  22.418 ms  21.492 ms  21.634 ms
14  95.172.79.1 (95.172.79.1)  23.891 ms  19.223 ms
    95.172.79.33 (95.172.79.33)  20.193 ms
15  lithiumtechinc-1.mpr1.ams004.pnap.net (95.172.78.146)  22.062 ms  26.331 ms  23.017 ms
16  * * *
17  * * *
18  * * *
19  * * *

And cableforum.co.uk does the same:

traceroute to cableforum.co.uk (87.106.245.143), 64 hops max, 52 byte packets
 1  10.0.1.1 (10.0.1.1)  1.361 ms  1.239 ms  0.813 ms
 2 
 3 
 4  popl-bb-1a-as5-0.network.virginmedia.net (213.105.175.149)  10.435 ms  12.752 ms  9.055 ms
 5  * * *
 6  amst-ic-1-as0-0.network.virginmedia.net (213.105.175.6)  18.712 ms  18.231 ms  15.921 ms
 7  amsix.bb-c.nkf.ams.nl.oneandone.net (195.69.144.220)  25.959 ms  23.679 ms  26.958 ms
 8  te-4-1.bb-c.act.fra.de.oneandone.net (212.227.120.130)  25.256 ms  24.300 ms  23.823 ms
 9  te-3-3.bb-c.tp.kae.de.oneandone.net (212.227.120.53)  28.275 ms
    te-1-3.bb-c.tp.kae.de.oneandone.net (212.227.120.17)  28.352 ms  27.703 ms
10  ae-2.gw-distp-a.bs.ka.oneandone.net (212.227.121.210)  28.467 ms  28.992 ms  28.273 ms
11  ae-1.gw-prtr-r1-1a.fs.kae.de.oneandone.net (195.20.247.137)  29.745 ms  28.052 ms  27.088 ms
12  * * *
13  * * *
14  * * *
15  * * *

So how do we get the fault re-opened?


[nickh]

I see that there's a new fault reference show on the service status page:

Service Disruption

intermittent connection issues on your broadband internet service

Reported on: Sun 16 Oct 2011, 09:20 PM
Estimated fix time: Mon 17 Oct 2011, 08:19 AM
Fault reference: F001770093

Question is why did they close the original one when the problem was not resolved.

[tb99]

I'm also still getting this and they have the new fault down as active in my area. Getting really sick of this.

[Bill-C]

Comes to something when i have to use a vpn to be able to surf to certain sites

[tb99]

It would be nice to know what they've screwed up... I guess from the routing problems they had a hardware failure, so you swap in a replacement and thrown on the backed up config, why the hell is it still down then??

Did anyone see what the resolution for the original fault was?

[disruptive]

A brief look with httping and Wireshark suggests that the initial TCP handshake and page request are fine, then the response is fragmented/delayed/dropped.

So I wouldn't call this a routing problem so much as a 'messing with http traffic gone wrong' one.