Ask
Reply
Solution
06-02-2017 09:49 AM
I've been having broadband issue over the last few week, recently I'm lead to believe it's a routing issue, because no matter where I go my connection routers me to London, then New York (where it drops all the packets) then to Ireland, then to Leeds before going to the destination.
I was wondering if anyone else noticed anything similar?
Here are a few examples:
First is to BBC.co.uk
Tracing route to bbc.co.uk [212.58.244.22]
over a maximum of 30 hops:
0 PC-NAME [192.168.0.226]
1 vodafone.connect [192.168.0.1]
2 host-212-158-250-37.dslgb.com [212.158.250.37]
3 63.130.104.194
4 ae13-100-xcr1.ltw.cw.net [195.2.23.77]
5 ae8-xcr1.lnt.cw.net [195.2.24.130]
6 bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PC-NAME [192.168.0.226]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% vodafone.connect [192.168.0.1]
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% host-212-158-250-37.dslgb.com [212.158.250.37]
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 63.130.104.194
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% ae13-100-xcr1.ltw.cw.net [195.2.23.77]
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% ae8-xcr1.lnt.cw.net [195.2.24.130]
0/ 100 = 0% |
6 15ms 0/ 100 = 0% 0/ 100 = 0% bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
Next is Google.co.uk
Even with google the route goes to the US then Ireland and then back to the US again
Tracing route to google.co.uk [216.58.201.3]
over a maximum of 30 hops:
0 PC-NAME [192.168.0.226]
1 vodafone.connect [192.168.0.1]
2 host-212-158-250-37.dslgb.com [212.158.250.37]
3 63.130.104.194
4 ae13-100-xcr1.ltw.cw.net [195.2.23.77]
5 ae8-xcr1.lnt.cw.net [195.2.24.130]
6 google-gw.lnt.cw.net [195.89.96.234]
7 108.170.246.225
8 lhr35s03-in-f3.1e100.net [216.58.201.3]
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PC-NAME [192.168.0.226]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% vodafone.connect [192.168.0.1]
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% host-212-158-250-37.dslgb.com [212.158.250.37]
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 63.130.104.194
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% ae13-100-xcr1.ltw.cw.net [195.2.23.77]
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% ae8-xcr1.lnt.cw.net [195.2.24.130]
0/ 100 = 0% |
6 15ms 0/ 100 = 0% 0/ 100 = 0% google-gw.lnt.cw.net [195.89.96.234]
0/ 100 = 0% |
7 15ms 0/ 100 = 0% 0/ 100 = 0% 108.170.246.225
0/ 100 = 0% |
8 15ms 0/ 100 = 0% 0/ 100 = 0% lhr35s03-in-f3.1e100.net [216.58.201.3]
Trace complete.
Last trace is to Facebook.com
Tracing route to facebook.com [31.13.92.36]
over a maximum of 30 hops:
0 PC-NAME [192.168.0.226]
1 vodafone.broadband.connect [192.168.0.1]
2 host-212-158-250-37.dslgb.com [212.158.250.37]
3 63.130.104.194
4 ae13-600-xcr1.ltw.cw.net [195.2.23.77]
5 ae11-xcr2.amd.cw.net [195.2.24.122]
6 ae14-xcr1.fix.cw.net [195.2.28.186]
7 ae17.pr03.fra2.tfbnw.net [103.4.96.22]
8 173.252.67.73
9 edge-star-mini-shv-01-frt3.facebook.com [31.13.92.36]
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PC-NAME [192.168.0.226]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% vodafone.station.connect [192.168.0.1]
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% host-212-158-250-37.dslgb.com [212.158.250.37]
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 63.130.104.194
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% ae13-600-xcr1.ltw.cw.net [195.2.23.77]
0/ 100 = 0% |
5 21ms 0/ 100 = 0% 0/ 100 = 0% ae11-xcr2.amd.cw.net [195.2.24.122]
0/ 100 = 0% |
6 28ms 0/ 100 = 0% 0/ 100 = 0% ae14-xcr1.fix.cw.net [195.2.28.186]
0/ 100 = 0% |
7 28ms 0/ 100 = 0% 0/ 100 = 0% ae17.pr03.fra2.tfbnw.net [103.4.96.22]
0/ 100 = 0% |
8 14ms 0/ 100 = 0% 0/ 100 = 0% 173.252.67.73
0/ 100 = 0% |
9 27ms 0/ 100 = 0% 0/ 100 = 0% edge-star-mini-shv-01-frt3.facebook.com [31.13.92.36]
06-02-2017 10:12 AM
I think the packet loss is a red herring there, and it is just the router at that hop being configured to not reply to ping requests. The traffic continues past that point, so suggests things are ok.
If it is going to the USA and back, that would be very strange.
As VF now own C&W, they may just be re-using IP ranges and the records of where they are located have not caught up.
What are the wider issues that you are having? Hopefully another member of the community, or the Vodafone staff may be able to help, or if the routing is as you think, explain what is going on.
06-02-2017 10:19 AM
Hi Grolschuk,
The issue I'm having is latency when connecting to online sevices, it's been on and off for a few weeks now it mainly happens Friday/Saturday/Sunday.(it does happen within the week but not as much)
One moment it fine and then the next moment it's not.
06-02-2017 07:17 PM
@Anonymous I'm sorry to hear you've been experiencing issues.
Our Broadband Live Chat team will be happy to help. You can also call them on 08080 034 515 8am-11pm, seven days a week.
06-02-2017 07:27 PM
Hi Colleen,
I've called your tech support team but the first time they weren't very helpfully (I'm guessing it was because I called late at night). The second time they were, I was told that the case was being transferred and that I would receive a call back within 72hrs (I called on Sunday afternoon), I only posted here to see if anyone else was getting a similar issues, as it's not one I've seen before
06-02-2017 09:39 PM - edited 06-02-2017 10:09 PM
I am having exactly the same issue with my connection. I joined Vodafone back in October 2016. Up to approximately 3 weeks ago it was fine, however now i am experiencing similar problems reported by other users.
Basically the connection is fine for one moment and then all of a sudden there is a dramatic increase in packet loss and latency. Tracing a route to ANY remote host produces very high figures from the hop past my vodafone.connect router.
two traces below, figures in red outline the issue
Tracing route to www.google.co.uk [216.58.204.67]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms vodafone.connect [192.168.1.1]
2 894 ms 1561 ms 710 ms host-212-158-250-34.dslgb.com [212.158.250.34]
3 1189 ms 10 ms 8 ms 63.130.105.130
4 741 ms 1096 ms 8 ms ae11-100-xcr1.hex.cw.net [195.89.96.1]
5 54 ms 8 ms 958 ms ae9-xcr1.lnt.cw.net [195.2.24.161]
6 71 ms 1092 ms 1109 ms google-gw.lnt.cw.net [195.89.96.234]
7 504 ms 10 ms 7 ms 108.170.246.129
8 406 ms 1047 ms 174 ms 108.170.238.121
9 * 721 ms 8 ms lhr25s13-in-f67.1e100.net [216.58.204.67]
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms vodafone.connect [192.168.1.1]
2 1101 ms 1063 ms 56 ms host-212-158-250-34.dslgb.com [212.158.250.34]
3 1281 ms 775 ms 932 ms 63.130.105.130
4 11 ms 8 ms 8 ms ae11-100-xcr1.hex.cw.net [195.89.96.1]
5 1607 ms 1098 ms 9 ms ae9-xcr1.lnt.cw.net [195.2.24.161]
6 1339 ms 1523 ms 9 ms google-gw.lnt.cw.net [195.89.96.234]
7 2342 ms 1768 ms 8 ms 108.170.246.129
8 1537 ms 8 ms 11 ms 216.239.57.103
9 * 2807 ms 9 ms google-public-dns-a.google.com [8.8.8.8]
By either waiting a random amount of time or a quick reboot of the router will cure the problem temporarily but then the ugly problem arises again.
I have spoken to Vodafone support (online chat and telephone) various times. The latest (called them today) is that i / we have two faults raised on the network and that i will be contacted back within 24hours.
Bottom line is they need to fix this quickly because in its current state, the connection and essentially what i have been sold is simply 'not fit for purpose'. The last resort is me having to cancel contract and move on which i don't want to do.
Lets see what happens.
07-02-2017 09:54 AM
Thank you Mellodello,
I'm glad that I'm not the only one being routed to the US and back again.....
It's really annyoing when you call support and they have no idea what you are going on about
Out of inerest where are you based?, I'm down in hampshire but my first hope is Camden the same as yours, then to US and back again.
07-02-2017 11:55 AM
07-02-2017 12:13 PM
Ah so your first hop seems right.
That would make sense its been around 3/4 weeks for me.
I wonder with these "problems" would the cancel the leaving fee
07-02-2017 02:10 PM