cancel
Showing results for 
Search instead for 
Did you mean: 
DaveNI1979
Expert
1,363 Views
Message 651 of 660

Re: BT Infinity and Fifa routing issues continued....

easo tracert.jpg

 

Anyone elses connection to easo got up the left even more than usual tonight? 230ms ping for me. woeful. 

0 Ratings
Seamie
Contributor
1,325 Views
Message 652 of 660

Re: BT Infinity and Fifa routing issues continued....

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=2 ttl=109 time=212.170 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 1 packets received, 80% packet loss
round-trip min/avg/max = 212.170/212.170/212.170 ms

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=1 ttl=109 time=211.874 ms
64 bytes from 159.153.234.54: seq=2 ttl=109 time=211.593 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 2 packets received, 60% packet loss
round-trip min/avg/max = 211.593/211.733/211.874 ms

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

 

traceroute to 159.153.234.54 (159.153.234.54), 30 hops max, 38 byte packets
1 172.16.18.3 (172.16.18.3) 9.194 ms 8.352 ms 7.438 ms
2 * * *
3 217.41.216.109 (217.41.216.109) 13.470 ms 12.387 ms 12.511 ms
4 213.120.158.234 (213.120.158.234) 15.382 ms 15.402 ms 15.446 ms
5 31.55.165.219 (31.55.165.219) 15.432 ms 15.396 ms 15.456 ms
6 31.55.165.109 (31.55.165.109) 16.145 ms 15.614 ms 15.479 ms
7 acc2-10GigE-10-2-0.mr.21cn-ipp.bt.net (109.159.250.202) 14.915 ms acc2-10GigE-1-2-0.mr.21cn-ipp.bt.net (109.159.250.198) 14.925 ms acc2-10GigE-10-2-0.mr.21cn-ipp.bt.net (109.159.250.202) 15.138 ms
8 core2-te0-13-0-17.ealing.ukcore.bt.net (109.159.250.170) 24.441 ms core2-te0-0-0-17.ealing.ukcore.bt.net (109.159.250.158) 24.400 ms 22.691 ms
9 transit2-xe9-0-0.ealing.ukcore.bt.net (62.6.200.185) 21.687 ms 21.584 ms 22.219 ms
10 t2c4-xe-9-3-0-0.uk-eal.eu.bt.net (166.49.168.61) 21.460 ms 24.150 ms 21.480 ms
11 xe-4-1-0.edge4.London2.Level3.net (212.187.201.153) 55.648 ms 21.902 ms 22.955 ms
12 ae-0-11.edge3.London2.Level3.net (4.69.200.125) 26.714 ms 26.333 ms 26.439 ms
13 ae-3-3.ebr1.Paris1.Level3.net (4.69.141.86) 257.259 ms * 273.157 ms
14 ae-71-71.csw2.Paris1.Level3.net (4.69.161.82) 327.703 ms 252.671 ms ae-91-91.csw4.Paris1.Level3.net (4.69.161.90) 248.706 ms
15 ae-62-62.ebr2.Paris1.Level3.net (4.69.161.93) 105.470 ms 243.137 ms ae-92-92.ebr2.Paris1.Level3.net (4.69.161.105) 246.934 ms
16 ae-44-44.ebr2.Washington1.Level3.net (4.69.137.62) 102.692 ms 320.645 ms ae-42-42.ebr2.Washington1.Level3.net (4.69.137.54) 324.734 ms
17 ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 270.896 ms ae-92-92.csw4.Washington1.Level3.net (4.69.134.158) 308.442 ms ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 235.673 ms
18 ae-4-90.edge3.Washington1.Level3.net (4.69.149.209) 316.648 ms ae-2-70.edge3.Washington1.Level3.net (4.69.149.81) 217.660 ms ae-4-90.edge3.Washington1.Level3.net (4.69.149.209) 322.600 ms
19 EA-INC.edge3.Washington1.Level3.net (4.59.144.74) 158.917 ms 296.361 ms 319.195 ms
20 * 159.153.93.2 (159.153.93.2) 323.335 ms 289.646 ms
21 159.153.225.30 (159.153.225.30) 216.724 ms 145.160 ms 140.445 ms
22 meav5-pub.pt.iad.ea.com (159.153.226.105) 357.433 ms 314.032 ms 140.901 ms
23 * meav5-pub.pt.iad.ea.com (159.153.226.105) 347.939 ms !A *
24 meav5-pub.pt.iad.ea.com (159.153.226.105) 308.333 ms !A * *
25 meav5-pub.pt.iad.ea.com (159.153.226.105) 347.619 ms !A * *
26 meav5-pub.pt.iad.ea.com (159.153.226.105) 328.927 ms !A * 358.203 ms !A

 

Sort it out BT!

0 Ratings
DaveNI1979
Expert
1,319 Views
Message 653 of 660

Re: BT Infinity and Fifa routing issues continued....

Im getting 380ms ping to easo.ea.com now. This one could be ea's fault. Rest my pings to other sites is ok, bbc, apple etc.
0 Ratings
Seamie
Contributor
1,318 Views
Message 654 of 660

Re: BT Infinity and Fifa routing issues continued....

Another one of EA's servers, this time it doesn't go through Paris

 

traceroute to 159.153.68.152 (159.153.68.152), 30 hops max, 38 byte packets
1 172.16.18.3 (172.16.18.3) 7.768 ms 7.389 ms 7.436 ms
2 * * *
3 217.41.216.109 (217.41.216.109) 13.665 ms 12.635 ms 12.466 ms
4 213.120.158.242 (213.120.158.242) 15.480 ms 15.145 ms 15.427 ms
5 31.55.165.219 (31.55.165.219) 15.469 ms 15.390 ms 15.556 ms
6 31.55.165.109 (31.55.165.109) 15.870 ms 16.159 ms 16.163 ms
7 acc2-xe-4-2-3.mr.21cn-ipp.bt.net (109.159.250.246) 16.707 ms acc2-10GigE-0-3-0.mr.21cn-ipp.bt.net (109.159.250.210) 15.406 ms acc1-10GigE-1-3-0.mr.21cn-ipp.bt.net (109.159.250.214) 15.154 ms
8 core2-te0-3-0-5.ealing.ukcore.bt.net (109.159.250.143) 28.142 ms 28.394 ms 27.950 ms
9 transit2-xe1-1-0.ealing.ukcore.bt.net (62.6.200.142) 24.189 ms 22.612 ms 22.990 ms
10 t2c4-xe-9-1-0-0.uk-eal.eu.bt.net (166.49.168.53) 23.204 ms 22.126 ms 22.708 ms
11 xe-4-1-0.edge4.London2.Level3.net (212.187.201.153) 30.429 ms 22.422 ms 24.213 ms
12 ae-3-3.ebr1.London15.Level3.net (4.69.141.189) 162.708 ms 163.432 ms 162.943 ms
13 ae-41-41.ebr1.London1.Level3.net (4.69.167.18) 163.414 ms ae-43-43.ebr1.London1.Level3.net (4.69.167.26) 159.841 ms ae-42-42.ebr1.London1.Level3.net (4.69.167.22) 162.965 ms
14 vlan104.ebr2.London1.Level3.net (4.69.143.98) 163.142 ms vlan102.ebr2.London1.Level3.net (4.69.143.90) 159.723 ms 159.476 ms
15 ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70) 160.453 ms ae-44-44.ebr1.NewYork1.Level3.net (4.69.137.78) 161.835 ms 163.395 ms
16 ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) 160.228 ms ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) 163.444 ms ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70) 160.434 ms
17 ae-82-82.ebr2.NewYork1.Level3.net (4.69.148.41) 159.427 ms ae-92-92.ebr2.NewYork1.Level3.net (4.69.148.45) 160.673 ms 159.946 ms
18 ae-2-2.ebr1.SanJose1.Level3.net (4.69.135.185) 159.950 ms 160.416 ms 161.933 ms
19 ae-81-81.csw3.SanJose1.Level3.net (4.69.153.10) 164.955 ms 161.930 ms ae-71-71.csw2.SanJose1.Level3.net (4.69.153.6) 162.172 ms
20 ae-12-70.car2.SanJose2.Level3.net (4.69.152.76) 162.681 ms ae-22-60.car2.SanJose2.Level3.net (4.69.152.12) 176.404 ms ae-12-70.car2.SanJose2.Level3.net (4.69.152.76) 165.916 ms
21 EA-INC.car2.SanJose2.Level3.net (4.59.4.6) 161.636 ms 160.616 ms 162.211 ms
22 * * *
23 * * *
24 *

 

 

And another from EA 

 

traceroute to 159.153.80.56 (159.153.80.56), 30 hops max, 38 byte packets
1 172.16.18.3 (172.16.18.3) 7.688 ms 8.577 ms 6.977 ms
2 * * *
3 217.41.216.109 (217.41.216.109) 12.580 ms 12.422 ms 12.156 ms
4 213.120.158.234 (213.120.158.234) 15.470 ms 15.499 ms 16.092 ms
5 31.55.165.219 (31.55.165.219) 16.391 ms 15.376 ms 15.442 ms
6 31.55.165.109 (31.55.165.109) 15.673 ms 15.774 ms 15.202 ms
7 acc2-xe-7-3-0.mr.21cn-ipp.bt.net (109.159.250.226) 28.065 ms 15.174 ms acc2-10GigE-10-2-0.mr.21cn-ipp.bt.net (109.159.250.202) 14.942 ms
8 core1-te0-13-0-0.ilford.ukcore.bt.net (109.159.250.137) 24.844 ms 26.367 ms core2-te0-4-0-0.ealing.ukcore.bt.net (109.159.250.131) 26.229 ms
9 peer2-xe11-0-0.telehouse.ukcore.bt.net (109.159.254.130) 25.382 ms 25.124 ms 25.714 ms
10 t2c3-xe-1-1-2-0.uk-lon1.eu.bt.net (166.49.211.180) 22.461 ms 22.390 ms 22.455 ms
11 166-49-211-254.eu.bt.net (166.49.211.254) 22.202 ms 22.648 ms 21.728 ms
12 ae5-xcr1.lsw.cw.net (195.2.28.25) 22.427 ms 46.183 ms 22.637 ms
13 xe-11-0-0-xcr1.duc.cw.net (195.2.21.246) 33.499 ms 33.637 ms 35.937 ms
14 * * *
15 *

 

 

Can anyone get someone on another isp to do a tracecert and post the results.

0 Ratings
Seamie
Contributor
1,307 Views
Message 655 of 660

Re: BT Infinity and Fifa routing issues continued....

Serious packet loss from the fifa servers tonight!

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=1 ttl=109 time=133.623 ms
64 bytes from 159.153.234.54: seq=2 ttl=109 time=135.885 ms
64 bytes from 159.153.234.54: seq=3 ttl=109 time=139.805 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 3 packets received, 40% packet loss
round-trip min/avg/max = 133.623/136.437/139.805 ms

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=1 ttl=109 time=143.123 ms
64 bytes from 159.153.234.54: seq=2 ttl=109 time=141.092 ms
64 bytes from 159.153.234.54: seq=3 ttl=109 time=136.589 ms
64 bytes from 159.153.234.54: seq=4 ttl=109 time=140.673 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 136.589/140.369/143.123 ms

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=2 ttl=109 time=213.857 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 1 packets received, 80% packet loss
round-trip min/avg/max = 213.857/213.857/213.857 ms

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=0 ttl=109 time=140.772 ms
64 bytes from 159.153.234.54: seq=2 ttl=109 time=136.295 ms
64 bytes from 159.153.234.54: seq=3 ttl=109 time=187.274 ms
64 bytes from 159.153.234.54: seq=4 ttl=109 time=133.492 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 133.492/149.458/187.274 ms

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=0 ttl=109 time=170.751 ms
64 bytes from 159.153.234.54: seq=4 ttl=109 time=213.525 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 2 packets received, 60% packet loss
round-trip min/avg/max = 170.751/192.138/213.525 ms

0 Ratings
Seamie
Contributor
1,299 Views
Message 656 of 660

Re: BT Infinity and Fifa routing issues continued....

It seems to have improved just after 10pm?  any autotimers set BT?

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=0 ttl=109 time=135.263 ms
64 bytes from 159.153.234.54: seq=1 ttl=109 time=143.730 ms
64 bytes from 159.153.234.54: seq=2 ttl=109 time=133.968 ms
64 bytes from 159.153.234.54: seq=3 ttl=109 time=142.176 ms
64 bytes from 159.153.234.54: seq=4 ttl=109 time=140.946 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 133.968/139.216/143.730 ms

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=0 ttl=109 time=149.205 ms
64 bytes from 159.153.234.54: seq=1 ttl=109 time=150.759 ms
64 bytes from 159.153.234.54: seq=2 ttl=109 time=134.618 ms
64 bytes from 159.153.234.54: seq=3 ttl=109 time=137.990 ms
64 bytes from 159.153.234.54: seq=4 ttl=109 time=136.439 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 134.618/141.802/150.759 ms

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=0 ttl=109 time=137.021 ms
64 bytes from 159.153.234.54: seq=1 ttl=109 time=142.250 ms
64 bytes from 159.153.234.54: seq=2 ttl=109 time=135.693 ms
64 bytes from 159.153.234.54: seq=3 ttl=109 time=136.486 ms
64 bytes from 159.153.234.54: seq=4 ttl=109 time=139.001 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 135.693/138.090/142.250 ms

 

PING 159.153.234.54 (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: seq=0 ttl=109 time=151.325 ms
64 bytes from 159.153.234.54: seq=1 ttl=109 time=171.866 ms
64 bytes from 159.153.234.54: seq=2 ttl=109 time=140.889 ms
64 bytes from 159.153.234.54: seq=3 ttl=109 time=139.082 ms
64 bytes from 159.153.234.54: seq=4 ttl=109 time=142.278 ms

--- 159.153.234.54 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 139.082/149.088/171.866 ms

 

 

0 Ratings
DaveNI1979
Expert
1,288 Views
Message 657 of 660

Re: BT Infinity and Fifa routing issues continued....

My pings to easo.ea.com have improved down to around 180ms still far too high and now i am getting packet loss as well to easo.ea.com.
0 Ratings
Seamie
Contributor
1,284 Views
Message 658 of 660

Re: BT Infinity and Fifa routing issues continued....

It seems like its just the Fifa servers I tried a few others and pings were decent and without packet loss. The pings could be 15ms but if there's packet loss you'll never get a lag free game.
0 Ratings
Manutdimy
Aspiring Expert
1,277 Views
Message 659 of 660

Re: BT Infinity and Fifa routing issues continued....

I only see contacting Watchdog as being the only solution because I am sick of this. I am NOT waiting until October when my contract is up. 

0 Ratings
Community Manager
Community Manager
1,216 Views
Message 660 of 660

Re: BT Infinity and Fifa routing issues continued....

Hi Guys,

 

As we have previously stated on the thread, after testing our network thoroughly we were unable to identify any issue on the BT network so we are unable to help with the problem that a few of you are reporting.

 

In relation the question about re-routing traffic, there were no steps taken to re-route traffic for this issue. In the interest of clarification the IPMC at BT only manage a router between AS2856 and AS5400, contrary to speculation a re-route of the traffic would affect more than just the gamers on this thread, the traffic to these servers also include all BT Vision and BT Sport traffic as well as various other businesses and Broadband users, so for this particular instance a re-route is not an option.

 

If there was an issue with the way traffic was being routed, the network teams would see multiple faults, the only potential problem could be with Amsterdam but as these are P2P connections it’s impossible to prove as the game will run on the worst connection out of the two.  BT can’t control other people’s connections or how bandwidth is being used by end users whilst playing FIFA. Amsterdam who look after our EU routers and would peer with other ISP’s have also reported that there is no evidence of a wider network issue.

 

We don’t disbelieve that some of you are having a poor gaming experience but as stated previously, this is not something related to a wider BT Network issue.  We have offered to look at each connection individually to see if there is an underlying problem for each customer concerned.

We will help each customer as much as we can, but as far as pushing that the fault is a problem with the network, there is no evidence to back this up and so the network teams are unable to proceed with their investigations.

 

I am afraid that we have taken the decision to lock this thread, the reason being that this is now becoming counterproductive.  There is little of no value to the community by leaving this thread to carry on. We are happy that the network teams have done all they can to help us with this one.

 

We fully appreciate that you are frustrated but there is nothing more can we do as an ISP if we cannot find the fault on our Network.

 

Cheers

 

Stephanie

Community ManagerStephanie
Did you get the help you needed?
Help others by clicking on ‘Mark as accepted solution’
Show your appreciation!
Click on the star next to a reply to say thanks
Help guide to using the community? Click below
Kudos”
Make sure you are logged into the forum otherwise you will not see our contact link when a moderator offers help. When sending us your details please don’t send a private message (PM), we can’t deal with account/service issues via PM so please use the contact link. Thanks
0 Ratings