on 03-11-2010 21:29
Upstream Frequency 45800000 Hz Upstream Power 49.7 dBmV
It may be that the modem only displays to 1 decimal point, but the upstream power increments in 0.25 dBmv steps.
If 49.70 dBmv is the actual upstream power, then the modem is prolly faulty. Tech support can look at this. I did note that you said upstream speed was OK - but it'll be the errors at the other end that matter.
Other than that, the stats are OK. The tracert should be allowed to display the hop names otherwise we have to do a DNS lookup to see what corresponds with the IP address.
on 03-11-2010 22:57
Regarding this 49.70 thing I mentioned, looking at other threads, it seems that this modem displays to 1 decimal point. So I think you can forget that theory!.
Is your upstream power stable? (Refresh the page a few times). Does it rise above 55 dBmv (in which case there is an ustream problem). Tech support can check whether or not there is noise on the upstream or errored packets.
03-11-2010 23:04 - edited 03-11-2010 23:06
Thanks for the ideas. I refreshed the connection page a few times and there was no change in the upstream power.
Tracert with hostnames:
Tracing route to newswww.bbc.net.uk [220.127.116.11]
over a maximum of 30 hops:
1 15 ms 17 ms 1223 ms 10.27.140.1
2 47 ms 20 ms 36 ms cmbg-core-1a-ge-210-2569.network.virginmedia.net
3 69 ms 35 ms 193 ms popl-bb-1a-ae2-0.network.virginmedia.net [212.43
4 800 ms 234 ms 20 ms nrth-bb-1b-as3-0.network.virginmedia.net [213.10
5 335 ms 67 ms 46 ms nrth-tmr-2-ae6-0.network.virginmedia.net [213.10
6 41 ms 175 ms 64 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
7 937 ms 36 ms 269 ms pos6-1.rt0.thdo.bbc.co.uk [18.104.22.168]
8 33 ms 20 ms 37 ms 22.214.171.124
9 297 ms 1005 ms 63 ms te12-1.hsw0.cwwtf.bbc.co.uk [126.96.36.199]
10 40 ms 71 ms 813 ms 188.8.131.52
11 48 ms 54 ms 24 ms bbc-vip002.cwwtf.bbc.co.uk [184.108.40.206]
on 04-11-2010 07:15
In that case one deduces from the tracert that there is congestion en route to or at your CMTS.
Tech support can eventually confirm.
04-11-2010 11:35 - edited 04-11-2010 11:52
For what it's worth, I did another tracert straight afterwards and the 1220ms hop was reduced to a normal 50-100ms.
on 04-11-2010 12:48
Thanks for the PM, I have checked your connection and local network and am unable to find an issue. Looking at the data provided here and on your other thread we're going to need to arrange for an engineer to call out to investigate the latency seen on the 1st hop of your traces. Can you let me know when in the next 7 days you will be available? Our timeslots Monday to Fridays are 8am-12noon, 12noon-4pm and 4pm-7pm. Saturdays 8am-12noon and 12noon-4pm.
04-11-2010 21:05 - edited 04-11-2010 21:06
I have arranged for an engineer to call on Saturday 13th November between 8am and 12noon for you. Any problems please let me know.
on 10-11-2010 23:31
As per your request, I have cancelled the technician visit for you. Any further issues with your service, please do let us know.