Quote:
|
Originally Posted by mmm
I agree the core network looks in good shape, extract from a traceroute back to my home PC ubr from the office:---
Code:
7 <10 ms <10 ms <10 ms tele-ic-1-ge-300-207.inet.ntl.com [212.250.14.33]
8 <10 ms <10 ms 10 ms gfd-bb-a-so-320-0.inet.ntl.com [62.253.185.77]
9 <10 ms <10 ms 10 ms gfd-bb-b-ae0-0.inet.ntl.com [213.105.172.6]
10 <10 ms 10 ms 10 ms nth-bb-a-so-000-0.inet.ntl.com [62.253.185.97]
11 <10 ms 10 ms <10 ms nth-bb-b-ae0-0.inet.ntl.com [62.253.185.118]
12 <10 ms 10 ms 10 ms bir-bb-a-so-100-0.inet.ntl.com [62.253.185.106]
13 10 ms 10 ms 10 ms oxfd-t2core-a-pos31.inet.ntl.com [62.253.187.10]
14 10 ms 10 ms 10 ms oxfd-t2cam1-a-ge-wan31.inet.ntl.com [213.106.245.38]
15 10 ms 10 ms 10 ms oxfd-oxfd-ubr-4-ge10.inet.ntl.com [213.106.246.14]
So go-on ntl switch it on now! |
The core network was always underloaded - traces from external sources confirmed this. Just local HFC area's (to you - cabling in your area) were getting congestion hence why latency wasnt as good as it is now. NTL have just resegmented yours and many others areas.