View Full Version : Cannot access non-UK sites
scrotnig
13-10-2007, 10:55
Once again I'm finding I cannot access non-UK based sites (including my own which is hosted in the US). Every now and then it works but then times out subsequently.
Tracert gets as far as London1.leve12.net and then stops.
Tried ringing technical support..it just rings out for two minutes then cuts off.
Anyone else finding this? It's similar to the problem a while ago when nobody could access that "World Of Warcraft" site. Though I cannot remember the URL for that so I can't see if that's affected also.
Service is ex-ntl Bromley SACM, Manchester 20mb.
yeah im same here in newcastle all usa web down for me too.
I'm in the same boat to, the only way I can connect to my site at the planet datacenter in texas is via a remote desktop direct to the server :(
Manchester 20meg
gkhewitt
13-10-2007, 11:24
Also having trouble here in Newcastle. Some stuff works, some doesn't. My VoIP line is causing trouble too, although not entirely sure if it's related..
The rest of the web uk included is down to a snails pace again for me now too at times.
scrotnig
13-10-2007, 11:35
I got through to tech support....a tracert has shown it stops at london1.level3.net. NTL are saying it's not their problem as they don't have any control over that.
From Leeds, 4Mb - just got into Washington Post, USA Today, PBS, and Aintitcool.com OK.
(and other US based SF book websites).
scrotnig
13-10-2007, 11:42
Tech support have now acknowledged that it's a routing issue and have said they will call back within 24 hours with an update.
Cobbydaler
13-10-2007, 11:44
From Leeds, 4Mb - just got into Washington Post, USA Today, PBS, and Aintitcool.com OK.
(and other US based SF book websites).
I can get into Washington Post here in the North West, but off & on...
scrotnig
13-10-2007, 12:02
Yes, it's intermittent.
I rank customer services afterwards to arrange the refund of the call charge but they said I must wait til the bill comes.
However, customer services seemed to be in India as well...either that or it's a terrible line. I didn't know customer services had been offshored as well, when did that happen?
Same here in Manchester. Can't access my own site, http://unspecific.net (Level3)
Xtrm2Matt
13-10-2007, 12:56
Same here. Can't access a number of my websites all hosted in a Texas datacenter on my dedicated servers.
Also can't access any online games, such as C&C3.
Tried rebooting my modem, router and all the obvious rubbish but no avail.
Same here. Can't access a number of my websites all hosted in a Texas datacenter on my dedicated servers.
Also can't access any online games, such as C&C3.
Tried rebooting my modem, router and all the obvious rubbish but no avail.
It's a routing issue. Rebooting modems won't work :D
VirginMedia :mad::mad::mad::mad::mad::td::td:
Same here in Manchester. Can't access my own site, http://unspecific.net (Level3)
I can get to that one OK from Lincoln. I don't use Virgin DNS servers, could that be a factor?
Xtrm2Matt
13-10-2007, 13:03
It's a routing issue. Rebooting modems won't work :D
VirginMedia :mad::mad::mad::mad::mad::td::td:
Yeah, but obviously I didn't know that at first :p:
I can get to that one OK from Lincoln. I don't use Virgin DNS servers, could that be a factor?
DNS plays no part in this. It's the routing in which VM uses - which is causing the problem.
You may be able to access it, but it's a 1:5 chance.
---------- Post added at 13:05 ---------- Previous post was at 13:04 ----------
Yeah, but obviously I didn't know that at first :p:
I tried rebooting it too :p:
scrotnig
13-10-2007, 13:08
It seems to be ok from some areas and not others...possibly dependent on Bromley/Langley/ex-Telewest and suchlike.
I have some Virgin Media users on my site able to access it ok, but I am not sure if they are ex-Telewest, ex-Cable & Wireless, ex-ntl etc.
It seems to be ok from some areas and not others...possibly dependent on Bromley/Langley/ex-Telewest and suchlike.
I have some Virgin Media users on my site able to access it ok, but I am not sure if they are ex-Telewest, ex-Cable & Wireless, ex-ntl etc.
Considering a majority of websites are now hosted on infrastructure located in the US! Why don't VM put this on the bloody service-status page! :rolleyes::rolleyes:
It's always the same. When you're not really bothered it's ok. When it's something you need to access you can't. :mad:
Just have to keep trying.
It's always the same. When you're not really bothered it's ok. When it's something you need to access you can't. :mad:
Just have to keep trying.
Keep trying Aimlessly
Cobbydaler
13-10-2007, 13:15
I can get to that one OK from Lincoln. I don't use Virgin DNS servers, could that be a factor?
I use openDNS & it's still been an on & off problem here for me.
It depends which way the connection's routed. Something must be down somewhere...
scrotnig
13-10-2007, 13:16
Considering a majority of websites are now hosted on infrastructure located in the US! Why don't VM put this on the bloody service-status page! :rolleyes::rolleyes:
They may well do so...to be fair, it's barely an hour since they admitted being aware of the problem when I phoned them.
This has happened before, and it's usually resolved the same day.
They may well do so...to be fair, it's barely an hour since they admitted being aware of the problem when I phoned them.
This has happened before, and it's usually resolved the same day.
it's been a problem for the last 2 and 1/2 hours.
it really kicked in at least 2 hours ago.
:)
Also happening in teesside seems to be on their London2 / London1 connection (level3 that is).
7 17 ms 17 ms 18 ms 212.187.136.125
8 37 ms 22 ms 31 ms ae-4-4.ebr1.London1.Level3.net [4.69.133.102]
9 * * * Request timed out.
7 16 ms 16 ms 16 ms 195.50.91.129
8 18 ms 18 ms 36 ms ae-32-54.ebr2.London2.Level3.net [4.68.117.126]
9 19 ms 39 ms 32 ms ae-2.ebr1.London1.Level3.net [4.69.132.146]
10 * * * Request timed out.
11 * * * Request timed out.
Going to http://www.level3.com/lookingglass also shows this when you try to traceroute from London2.
If NTL is not going to change their routing, then they need to get in touch with level3 to get them to fix their routing, probably be just a bad/corrupted routing table.
Also happening in teesside seems to be on their London2 / London1 connection (level3 that is).
7 17 ms 17 ms 18 ms 212.187.136.125
8 37 ms 22 ms 31 ms ae-4-4.ebr1.London1.Level3.net [4.69.133.102]
9 * * * Request timed out.
7 16 ms 16 ms 16 ms 195.50.91.129
8 18 ms 18 ms 36 ms ae-32-54.ebr2.London2.Level3.net [4.68.117.126]
9 19 ms 39 ms 32 ms ae-2.ebr1.London1.Level3.net [4.69.132.146]
10 * * * Request timed out.
11 * * * Request timed out.
Going to http://www.level3.com/lookingglass also shows this when you try to traceroute from London2.
If NTL is not going to change their routing, then they need to get in touch with level3 to get them to fix their routing, probably be just a bad/corrupted routing table.
are you with virginmedia?
which site were you trying to tracert?
Xtrm2Matt
13-10-2007, 13:22
Small update:
This isn't a VM issue.
My friend from Spain is also having problems accessing USA sites and my websites.
Seems this may be a transatlantic issue.
Small update:
This isn't a VM issue.
My friend from Spain is also having problems accessing USA sites and my websites.
Seems this may be a transatlantic issue.
If anybody cared to notice. It seems to be a Level3 related routing issue.
To answer the question yes, Im on virginmedia (ex ntl). Its not a VM issue, its a level3 routing issue, so any ISP that uses level3 london link we be effected, including VM.
Xtrm2Matt
13-10-2007, 13:33
Level3 does indeed seem to be the issue.
Glad I found this that will explain why I can't log on to my PS3 was spending ages trying to reconfigure it because my internet connection comes up as working. This level 3 issue expalins it cause its the ps3 network I can't get on to only.
What a joke! :mad:
1 48 ms 6 ms 42 ms 10.90.116.1
2 10 ms 9 ms 9 ms oldh-t2cam1-b-v124.inet.ntl.com [80.5.164.225]
3 12 ms 11 ms 39 ms 62.252.192.165
4 32 ms 44 ms 9 ms man-bb-b-so-020-0.inet.ntl.com [213.105.242.245]
5 28 ms 18 ms 11 ms man-bb-a-ge-000-0.inet.ntl.com [62.253.187.177]
6 10 ms 49 ms 14 ms 212.187.136.125
7 21 ms 22 ms 51 ms ae-4-4.ebr1.london1.level3.net [4.69.133.102]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
That's just another favourite site of mine.
Cobbydaler
13-10-2007, 13:59
3 oldh-t2cam1-b-v120.inet.ntl.com (80.5.164.209) 10.026 ms 30.515 ms 54.420 ms
4 62.252.192.173 (62.252.192.173) 56.078 ms 57.577 ms 53.354 ms
5 man-bb-b-so-020-0.inet.ntl.com (213.105.242.245) 50.903 ms 46.206 ms 43.139 ms
6 man-bb-a-ge-000-0.inet.ntl.com (62.253.187.177) 36.044 ms 32.965 ms 28.230 ms
7 212.187.136.125 (212.187.136.125) 22.820 ms 20.582 ms 16.640 ms
8 ae-4-4.ebr1.London1.Level3.net (4.69.133.102) 22.532 ms 36.338 ms 35.636 ms
9 * ae-1-100.ebr2.London1.Level3.net (4.69.132.118) 20.534 ms 20.844 ms
10 ae-4.ebr1.NewYork1.Level3.net (4.69.132.109) 100.080 ms 95.780 ms 107.954 ms
11 ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) 109.107 ms * *
12 ae-82-82.ebr2.NewYork1.Level3.net (4.69.134.89) 107.107 ms * ae-62-62.ebr2.NewYork1.Level3.net (4.69.134.81) 102.969 ms
13 * ae-2.ebr1.Chicago1.Level3.net (4.69.132.65) 109.645 ms *
14 ae-68.ebr3.Chicago1.Level3.net (4.69.134.58) 114.323 ms * *
15 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 142.906 ms * *
16 * * ge-9-2.hsa1.Denver1.Level3.net (4.68.107.163) 138.484 ms
17 * 4.68.94.1 (4.68.94.1) 132.583 ms 133.487 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
:shrug: :confused:
Seems fixed for me as of 2 minutes ago.
scrotnig
13-10-2007, 14:16
Yes it's getting through now.
yah. seems to be working now ...
nice to see people blaming VM again for something out of their control :rolleyes:
scrotnig
13-10-2007, 15:03
Perhaps if they didn't tell me it was my own PC/my own website that was the problem, before eventually falling back on "we don't guarantee access to non-Uk sites, please use UK based sites in future and you'll be fine" then people wouldn't jump to that conclusion.
A little more willingness to accept that it's not always the customer's fault wouldn't go amiss.
Besides, technically, if their routing provider goes down, it is quite reasonable to expect that there will be a backup provider in place, which obviously there wasn't.
All things considered, it's been sorted out quickly so I've no problem. But I *do* have a problem with being repeatedly told it's my own settings when it so blatantly obviously isn't, and then being charged a fiver in call charges for it.
Perhaps if they didn't tell me it was my own PC/my own website that was the problem, before eventually falling back on "we don't guarantee access to non-Uk sites, please use UK based sites in future and you'll be fine" then people wouldn't jump to that conclusion.
A little more willingness to accept that it's not always the customer's fault wouldn't go amiss.
Besides, technically, if their routing provider goes down, it is quite reasonable to expect that there will be a backup provider in place, which obviously there wasn't.
All things considered, it's been sorted out quickly so I've no problem. But I *do* have a problem with being repeatedly told it's my own settings when it so blatantly obviously isn't, and then being charged a fiver in call charges for it.
it depends what the support have to work with, they see your connection to VM being fine and no issues in your area, what are they meant to think?
also, seeing as the error was in the level 3 network, the problem lies with level 3 and they should be the ones to have a backup route.
a question to you though, if you did a tracert and saw it get to the level 3 network and then stop, why phone VM at all?
scrotnig
13-10-2007, 15:12
it depends what the support have to work with, they see your connection to VM being fine and no issues in your area, what are they meant to think?
also, seeing as the error was in the level 3 network, the problem lies with level 3 and they should be the ones to have a backup route.
a question to you though, if you did a tracert and saw it get to the level 3 network and then stop, why phone VM at all?
Because they need to be aware there is a problem.
If they are not made aware, then level 3 will not be made aware, and the problem will not get fixed.
I cannot make level 3 aware myself. If I could then I would.
Besides, I know how to do a tracert. I would say from experience that the greater majority of VM users will not know how to do one, and thus will simply call their ISP with "my connection isn't working". If VM are aware of the problem, then a good tech will be able to match the symptoms with the issue and advise accordingly.
Had VM simply said to me "sounds like a problem with Level 3, we can try and let them know but other than that it's out of our hands", it would have been much more honest than "it's your computer". When I worked for NTL, I came across customers that had actually gone out and bought new computers on the basis of this sort of advice, and that's appalling.
all I can say is thank goodness I ordered bt last night! Half the speed......triple the reliability!
scrotnig
13-10-2007, 15:14
BT are fortunate in this instance in that they don't appear to rely on Level 3...otherwise they'd have been for the chop as well!
None of what's happened today would make me go onto ADSL. My broadband connection, whilst far from perfect, is pretty reliable overall, even though it never gets even half the advertised 20mb.
If I was *forced* onto ADSL though, then yes I'd use BT. Best of a bad bunch.
I'm sorry to say I've been on NTL/VM for 15 months and have had nothing but problem after problem. I had maybe a 4 month period where it actually worked but apart from that its just been so frustrating. The speed is great but it just doesn't seem to work for me. I've had engineers out and they have aklnowledged I have a problem but don't know what it might be or can't suggest any way of fixing it.
aldiboronti
13-10-2007, 16:50
I don't know what's going on - US sites are up and down like a tart's knickers at the moment.
Axegrinder
13-10-2007, 17:07
Yeah, sites such as Bebo, Myspace and Youtube are constantly timing out, other UK sites are fine.
Flubflow
13-10-2007, 17:18
It started to go OK earlier this afternoon but has turned to crap again. Can't do anything with eBay.co.uk at this moment in time.
Considering the huge impact of this fault, it is quite surprising that there is absolutely jack all about it on Virgin Media's server status page.
I have had this problem and I'm in Cardiff. Another friend of mine on NTL/VirginMedia is having it also. I looked for the virginmedia phone number 09062121111 and it isn't working, so i looked for the old ntl number 0871 225 1111 and that tells you to phone the new one which isn't working or to check the service status. So you check service status, press 1 for broadband etc, and all it does it tell you to reboot your modem as it can solve most problems. There was no information about current service status.
freakgirl
13-10-2007, 17:26
Ebay has been playing up all day
slingading
13-10-2007, 17:38
Ebay isnt working for me at all, not very good considering I have auctions ending :td:
Ive done a tracert and this is the results:
Tracing route to hp-intl-uk.ebay.com [66.135.200.16]
over a maximum of 30 hops:
1 13 ms 10 ms 11 ms 10.108.192.1
2 10 ms 9 ms 11 ms 80.192.128.3
3 19 ms 11 ms 11 ms pres-t3core-1a-ge-010-0.inet.ntl.com [80.0.160.6
9]
4 11 ms 28 ms 28 ms lee-bb-a-ge-330-0.inet.ntl.com [213.105.175.173]
5 21 ms 19 ms 20 ms bre-bb-b-so-200-0.inet.ntl.com [213.105.175.26]
6 24 ms 31 ms 27 ms 195.50.91.129
7 39 ms 33 ms 24 ms ae-31-55.ebr1.London2.Level3.net [4.68.117.158]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Its been like this since I first went online about 9 oclock this morning.
Flubflow
13-10-2007, 17:55
Ebay has been playing up all day
For the likes of you and I, yes it has. For anyone else who is using an Internet Service Provider that does not rely on routing from the "Level3" company then ebay will be OK. Ebay itself is not currently experiencing any issues.
---------- Post added at 17:55 ---------- Previous post was at 17:54 ----------
Ebay isnt working for me at all, not very good considering I have auctions ending :td:
Ive done a tracert and this is the results:
Tracing route to hp-intl-uk.ebay.com [66.135.200.16]
over a maximum of 30 hops:
1 13 ms 10 ms 11 ms 10.108.192.1
2 10 ms 9 ms 11 ms 80.192.128.3
3 19 ms 11 ms 11 ms pres-t3core-1a-ge-010-0.inet.ntl.com [80.0.160.6
9]
4 11 ms 28 ms 28 ms lee-bb-a-ge-330-0.inet.ntl.com [213.105.175.173]
5 21 ms 19 ms 20 ms bre-bb-b-so-200-0.inet.ntl.com [213.105.175.26]
6 24 ms 31 ms 27 ms 195.50.91.129
7 39 ms 33 ms 24 ms ae-31-55.ebr1.London2.Level3.net [4.68.117.158]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Its been like this since I first went online about 9 oclock this morning.
Yup, as has been pointed out before, it all ends at Level3, London.
Mick Fisher
13-10-2007, 18:03
Level3 and Sprintlink have been pants for ages. VM is simply not providing enough capacity or if they are, then they are getting ripped off by the likes of said peering partners and it's about time they woke up and did something about it. :(
I have been having problems all day, I'm both a VM and a Telewest Business customer and its been up and down all day. Hope they fix this soon....
internetguy
13-10-2007, 18:28
My connection has been fine all of today :P Im in stevenage btw ;)
Maybe you weren't just affected, whereas most of us were.
homealone
13-10-2007, 21:19
it looks like they have tried re-routing
10/13/07 21:12:43 Fast traceroute 66.135.200.16
Trace 66.135.200.16 ...
1 192.168.1.1 0ms 0ms 0ms TTL: 0 (No rDNS)
2 10.249.136.1 57ms 7ms 8ms TTL: 0 (No rDNS)
3 82.13.48.65 10ms 12ms 15ms TTL: 0 (nott-t2cam2-a-v613.inet.ntl.com ok)
4 195.182.175.129 16ms 13ms 18ms TTL: 0 (nott-t3core-1a-ge-110-0.inet.ntl.com ok)
5 213.105.174.169 19ms 12ms 13ms TTL: 0 (lee-bb-a-so-020-0.inet.ntl.com ok)
6 213.105.175.26 19ms 49ms 21ms TTL: 0 (bre-bb-b-so-200-0.inet.ntl.com ok)
7 195.50.91.129 19ms 22ms 32ms TTL: 0 (No rDNS)
8 4.68.117.190 30ms 39ms 26ms TTL: 0 (ae-32-56.ebr2.London2.Level3.net ok)
9 4.69.132.121 20ms 40ms 37ms TTL: 0 (ae-1-100.ebr1.London2.Level3.net ok)
10 4.69.133.93 28ms 36ms 34ms TTL: 0 (ae-2.ebr1.Paris1.Level3.net ok)
11 4.69.133.82 36ms 33ms 33ms TTL: 0 (ae-1-100.ebr2.Paris1.Level3.net ok)
12 4.69.132.113 103ms 105ms 110ms TTL: 0 (ae-5.ebr2.Washington1.Level3.net ok)
13 4.69.134.158 108ms 112ms 107ms TTL: 0 (ae-92-92.csw4.Washington1.Level3.net ok)
14 4.69.134.189 115ms 125ms 99ms TTL: 0 (ae-94-94.ebr4.Washington1.Level3.net ok)
15 4.69.132.94 108ms 109ms 110ms TTL: 0 (ae-3.ebr4.NewYork1.Level3.net ok)
16 4.69.135.185 201ms 173ms 182ms TTL: 0 (ae-2.ebr4.SanJose1.Level3.net ok)
17 4.69.134.254 172ms 180ms 172ms TTL: 0 (ae-94-94.csw4.SanJose1.Level3.net ok)
18 4.68.18.196 171ms 169ms 175ms TTL: 0 (ae-42-99.car2.SanJose1.Level3.net ok)
19 No Response * * *
20 No Response * * *
21 No Response * * *
22 No Response * * *
23 No Response * * *
24 No Response * * *
25 No Response * * *
26 No Response * * *
27 No Response * * *
28 No Response * * *
29 No Response * * *
nothing after san jose could be just the target rejecting pings?
it looks like they have tried re-routing
nothing after san jose could be just the target rejecting pings?
that's correct, a tcp traceroute goes through fine, normal one stops there for me to (and via a non-VM connection)
Considering the huge impact of this fault, it is quite surprising that there is absolutely jack all about it on Virgin Media's server status page.
It's not a Virgin Media issue so why would it be on their status page.
It's crappy Level3 (again), this is about the forth time in the last 9 months that this same route has had issues - in each case it takes level3 a few hours to sort it out (and annoyingly for me, the affected route kills my connectivity to the Planet's data centre(s)).
If you want to moan at someone then moan at those who run Level3. It's got nothing to do with VM at all.
---------- Post added at 23:16 ---------- Previous post was at 23:13 ----------
For those interested, my logs show it was down between 9:15am and 1:55pm, and then again from 3:15pm until 6:15pm. It's been ok since then.
Flubflow
14-10-2007, 02:48
It's not a Virgin Media issue so why would it be on their status page.
It's crappy Level3 (again), this is about the forth time in the last 9 months that this same route has had issues - in each case it takes level3 a few hours to sort it out (and annoyingly for me, the affected route kills my connectivity to the Planet's data centre(s)).
If you want to moan at someone then moan at those who run Level3. It's got nothing to do with VM at all.
---------- Post added at 23:16 ---------- Previous post was at 23:13 ----------
For those interested, my logs show it was down between 9:15am and 1:55pm, and then again from 3:15pm until 6:15pm. It's been ok since then.
Virginmedia buys a service from Level3. So, if Level3 have a fault which affects aspects of Virginmedia's service then Virginmedia should acknowledge on their status page that there is (or was) a problem. It would also be for VM's own benefit since it would reduce the number of tech support calls from people thinking they have a local fault.
TraxData
14-10-2007, 08:47
i see its back to being crap again, half the US sites i visit aint working!
And nor is my DC/Server, which has put me out of work this morning -rolls eyes-
It's not a Virgin Media issue so why would it be on their status page.
It's crappy Level3 (again), this is about the forth time in the last 9 months that this same route has had issues - in each case it takes level3 a few hours to sort it out (and annoyingly for me, the affected route kills my connectivity to the Planet's data centre(s)).
If you want to moan at someone then moan at those who run Level3. It's got nothing to do with VM at all.
I'm sorry but you couldn't be further from the truth!
I pay Virgin to provide me with an internet service. If my internet service isn't working then virgin should tell me why it isn't working. It doesn't matter whether it is physically their problem or not. If they subcontract in effect part of my connection out then they are still responsible for managing that part of the service. If they sell me internet service routing up to level 3 and nothing else then fair enough but they don't they sell me a full service and they have to take on the responsibility for it.
internetguy
14-10-2007, 10:52
I dunno why so many isps use Level3, they are crap... surely there must be other options?
simon9975
14-10-2007, 11:06
My service was terrible yesterday,but all seems to be ok now?
Maybe been sorted out?
My service was terrible yesterday,but all seems to be ok now?
Maybe been sorted out?
Not for me. I can access this site and a few non-uk sites, but other than that the whole web appears to be down for me. I'm on ADSL24 btw.
papa smurf
14-10-2007, 11:57
i cant get out of uk
agent00x
14-10-2007, 15:16
I'm also having a problem with sprintlink, sometimes it works sometimes it doesn't, and this is often.
Mick Fisher
14-10-2007, 21:07
I dunno why so many isps use Level3, they are crap... surely there must be other options?
My guess is it's because they are cheap.
---------- Post added at 21:07 ---------- Previous post was at 21:05 ----------
I'm also having a problem with sprintlink, sometimes it works sometimes it doesn't, and this is often.
Too true, must be a rebadged Level3. :D
hmmm, I only started having problems Saturday night, but they still continue. That's 24 hours for me. Basically, I can connect to a select few sites, but 95% of the web is down for me. No Google, no BBC, no US sites. Most UK sites are down. My ISP's forum is unavailable. By some fluke I can connect to this site, thank god.
I can understand things going tits up occasionally (and I hate the moaning that invariably breaks out when there is a fault), but I have to say that over 24 hours to resolve a fault of this proportion is not acceptable.
Edit: Scratch that. A router reboot solved it :)
I vaguely recall reading somewhere that this is something to do with available bandwith on the transatlantic cable. Not sure of the exact details but basically too many VM customers are competing for the same bandwidth creating a bottleneck with the usual dropped connections and slow speeds.
I dunno why so many isps use Level3, they are crap... surely there must be other options?
Absolutely. Cogent, Telia, Tiscali (maybe they should get a quote! :P), etc...
Siegfried
15-10-2007, 09:16
I had problems with my connection since saturday, it looks VM DHCP wasn't working correctly. Now it's ok - LONDON N16
Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sun Oct 14 04:10:06 2007 Critical (3) REG RSP not received
Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Critical (3) DHCP FAILED - Request sent, No response
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
I had problems with my connection since saturday, it looks VM DHCP wasn't working correctly. Now it's ok - LONDON N16
Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sun Oct 14 04:10:06 2007 Critical (3) REG RSP not received
Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Critical (3) DHCP FAILED - Request sent, No response
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
That's a common issue. I wouldn't worry.
Absolutely. Cogent, Telia, Tiscali (maybe they should get a quote! :P), etc...
:shocked: someone actually recommending the usage of tiscali or cogent? :shocked:
cogent are one of the worst (and cheapest) and my servers connection has gone to pot since it started using tiscali
deerokus
16-10-2007, 23:57
I'm having some problems just now with certain sites - BBC News, wikipedia well basically anything foreign or with lots of traffic. Is that what's happening here?
tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.251.201]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 5 ms 5 ms 10.232.232.1
3 6 ms 8 ms 6 ms renf-t2cam1-b-v131.inet.ntl.com [80.4.65.229]
4 8 ms 6 ms 7 ms renf-t3core-1b-ge-012-0.inet.ntl.com [195.182.17
6.185]
5 22 ms 7 ms 6 ms ren-bb-b-so-600-0.inet.ntl.com [213.105.175.225]
6 13 ms 12 ms 13 ms man-bb-a-so-010-0.inet.ntl.com [62.253.185.170]
7 19 ms 18 ms 19 ms gfd-bb-b-so-200-0.inet.ntl.com [62.252.192.94]
8 24 ms 19 ms 23 ms redb-ic-1-as0-0.inet.ntl.com [62.253.185.78]
9 20 ms 21 ms 22 ms 212.58.238.189
10 26 ms 199 ms 203 ms 212.58.238.149
11 21 ms 20 ms 19 ms 212.58.239.62
12 21 ms 22 ms 20 ms www1.telhc.bbc.co.uk [212.58.251.201]
Trace complete.
that works fine, but nothing on the bbc site itself works. So I tried this:
tracert news.bbc.co.uk
Tracing route to newswww.bbc.net.uk [212.58.226.29]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 7 ms 7 ms 10.232.232.1
3 8 ms 8 ms 8 ms renf-t2cam1-a-v131.inet.ntl.com [80.4.65.201]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
tracert en.wikipedia.org
Tracing route to rr.knams.wikimedia.org [145.97.39.155]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.1.1
2 27 ms 7 ms 9 ms 10.232.232.1
3 7 ms 7 ms 7 ms renf-t2cam1-a-v131.inet.ntl.com [80.4.65.201]
4 * * * Request timed out.
5 * * * Request timed out.
6 * *
etc...
Or is this some other issue? I note that for the non-working sites it's not even getting as far as these Level 3 people.
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.