![]() |
Reading area
Me and 2 buddies are having some issues in the reading area...
Pinging bbc.co.uk [212.58.228.154] with 32 bytes of data: Reply from 212.58.228.154: bytes=32 time=13ms TTL=245 Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Request timed out. Request timed out. Request timed out. Reply from 212.58.228.154: bytes=32 time=13ms TTL=245 Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Reply from 212.58.228.154: bytes=32 time=13ms TTL=245 Request timed out. Reply from 212.58.228.154: bytes=32 time=14ms TTL=245 Reply from 212.58.228.154: bytes=32 time=14ms TTL=245 Request timed out. Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Reply from 212.58.228.154: bytes=32 time=13ms TTL=245 Request timed out. Reply from 212.58.228.154: bytes=32 time=13ms TTL=245 Request timed out. Request timed out. Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Reply from 212.58.228.154: bytes=32 time=13ms TTL=245 Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Request timed out. Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Request timed out. Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Reply from 212.58.228.154: bytes=32 time=15ms TTL=245 Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Request timed out. Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Reply from 212.58.228.154: bytes=32 time=14ms TTL=245 Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Request timed out. Request timed out. Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Reply from 212.58.228.154: bytes=32 time=13ms TTL=245 Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 Reply from 212.58.228.154: bytes=32 time=12ms TTL=245 is a typical ping .. tracert: Tracing route to bbc.co.uk [212.58.228.154] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.123.254 2 9 ms 9 ms 7 ms 10.152.103.254 3 10 ms 9 ms 10 ms rdng-t2cam1-a-ge95.inet.ntl.com [62.253.122.17] 4 9 ms * 11 ms winn-t2core-a-ge-wan61.inet.ntl.com [62.253.121. 1] 5 9 ms 9 ms 9 ms win-bb-a-so-200-0.inet.ntl.com [62.253.184.113] 6 * * * Request timed out. 7 * * 10 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130] 8 16 ms 21 ms 11 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74] 9 12 ms 12 ms 11 ms 212.58.239.217 10 14 ms 12 ms 12 ms pos6-0.rt1.mh.bbc.co.uk [212.58.239.231] 11 15 ms 13 ms 12 ms bogons.mh.bbc.co.uk [212.58.228.154] Trace complete. just wondering if anyone knows about it or if some kind ntl chap will see it and plug the cable back in ;) Thanks. |
Re: Reading area
It's ok from Nottingham but I take a totally different route.
From that trace it looks a little suspect on the NTL backbone, after hop 5. Perhaps JANoob could have a look for you - if he's around atm. :) |
Re: Reading area
having some problems here 2 im near reading think im on the same ubr
msn keeps dropping and some sites are really slow couldnt get nthellworld at all earlier also coundnt get net first thing this morning. |
Re: Reading area
Quote:
Tracing route to bbc.co.uk [212.58.228.154] over a maximum of 30 hops: 1 13 ms 18 ms 13 ms 10.152.103.254 2 15 ms 40 ms 34 ms rdng-t2cam1-b-ge95.inet.ntl.com [62.253.122.145] 3 10 ms 10 ms 15 ms winn-t2core-b-ge-wan61.inet.ntl.com [62.253.121.129] 4 10 ms 13 ms 13 ms winn-t2core-a-v99.inet.ntl.com [62.253.121.13] 5 10 ms 11 ms 15 ms win-bb-a-so-200-0.inet.ntl.com [62.253.184.113] 6 13 ms 11 ms 35 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130] 7 12 ms 15 ms 29 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74] 8 12 ms 15 ms 14 ms 212.58.239.217 9 23 ms 20 ms 13 ms pos6-0.rt1.mh.bbc.co.uk [212.58.239.231] 10 13 ms 17 ms 38 ms bogons.mh.bbc.co.uk [212.58.228.154] Trace complete. using same route it would appear - maybe they fixed it .... |
Re: Reading area
Reading/RG area problems already being discussed here: http://www.cableforum.co.uk/board/showthread.php?t=9755
|
| All times are GMT. The time now is 11:53. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum