Looks like a routing issue to Ubisoft.com today
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: Looks like a routing issue to Ubisoft.com toda...
Looks like a routing issue to Ubisoft.com today
10-09-2013 1:29 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote Target Name: lb-lsg-prod.ubisoft.com
IP: 216.98.48.56
Date/Time: 10/09/2013 12:41:15 to 10/09/2013 13:17:10
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 1007 878 87.2 0 0 0 home.gateway.home.gateway [192.168.1.254]
2 1007 0 0.0 12 698 20 lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 1007 0 0.0 12 97 12 link-b-central10.ptw-gw02.plus.net [212.159.2.150]
4 1007 0 0.0 12 87 14 250.core.access.plus.net [212.159.0.250]
5 1007 0 0.0 12 100 17 ae1.pcl-cr02.plus.net [195.166.129.3]
6 1007 0 0.0 12 109 16 ae2.pcl-cr01.plus.net [195.166.129.6]
7 1007 0 0.0 12 86 15 xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
8 1007 3 0.3 19 38 19 ae-3-3.ebr1.Paris1.Level3.net [4.69.141.86]
9 1007 3 0.3 19 32 19 ae-61-61.csw1.Paris1.Level3.net [4.69.161.78]
10 1007 3 0.3 19 86 20 [4.69.168.8]
11 1007 0 0.0 19 79 21 ix-20-0.tcore1.PVU-Paris.as6453.net [80.231.153.65]
12 1007 0 0.0 99 177 101 if-2-2.tcore1.PYE-Paris.as6453.net [80.231.154.18]
13 1007 1 0.1 98 173 101 if-3-6.tcore1.L78-London.as6453.net [80.231.130.85]
14 1007 3 0.3 99 202 102 if-1-2.tcore2.L78-London.as6453.net [80.231.130.122]
15 1007 0 0.0 99 150 101 if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
16 1006 3 0.3 99 153 102 if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.30]
17 1006 0 0.0 99 153 101 if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
18 1006 3 0.3 99 162 101 if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6]
19 1006 1006 100.0 0 0 0 [-]
Destination not reached in 35 hops
The offending borked routing is highlighted London>>>>>Paris Back to London before being routed incorrectly via Paris again
Normal routing is London level 3 onto AS6453.net London >>New York>>> Montreal in around 90ms currently 99ms with 20ms spikes
It has done this before, But i do know that it doesn't affect all ISP's , Not good if you have a ubisoft game that is reliant on the Ubi server in Canada for authentication, and online play
This got changed at 6am today, at the same time there was what appears to be other routing/peering changes going on across the plusnet network Which is visible on almost every ping monitor , so not unique to me
Re: Looks like a routing issue to Ubisoft.com today
10-09-2013 3:33 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I've just tried a few traces to the same domain and don't see the same issue so I think it's safe to assume that was some kind of temporary blip. Do keep an eye out for any other issues with that though.
Re: Looks like a routing issue to Ubisoft.com today
10-09-2013 4:11 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
A tracert for me to that IP 216.98.48.56 & host name lb-lsg-prod.ubisoft.com Is still getting routed london paris london , when it should not be , other ubisoft.com IP's may take a different route, but the ubisoft game i have uses that IP ending with 56 so will make online play more problematic
Quote Target Name: lb-lsg-prod.ubisoft.com
IP: 216.98.48.56
Date/Time: 10/09/2013 16:04:43
1 0 ms * 0 ms N/A home.gateway.home.gateway [192.168.1.254]
2 13 ms 13 ms 13 ms 13 ms lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 13 ms 13 ms 13 ms 13 ms link-b-central10.ptw-gw02.plus.net [212.159.2.150]
4 13 ms 12 ms 13 ms 13 ms 250.core.access.plus.net [212.159.0.250]
5 20 ms 29 ms 13 ms 13 ms ae1.pcl-cr02.plus.net [195.166.129.3]
6 24 ms 41 ms 13 ms 13 ms ae2.pcl-cr01.plus.net [195.166.129.6]
7 13 ms 13 ms 13 ms 13 ms xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
8 20 ms 20 ms 20 ms 19 ms ae-3-3.ebr1.Paris1.Level3.net [4.69.141.86]
9 20 ms 19 ms 20 ms 20 ms ae-61-61.csw1.Paris1.Level3.net [4.69.161.78]
10 20 ms 19 ms 20 ms 33 ms [4.69.168.8]
11 20 ms 23 ms 20 ms 20 ms ix-20-0.tcore1.PVU-Paris.as6453.net [80.231.153.65]
12 101 ms 100 ms 123 ms 100 ms if-2-2.tcore1.PYE-Paris.as6453.net [80.231.154.18]
13 97 ms 123 ms 98 ms 98 ms if-3-6.tcore1.L78-London.as6453.net [80.231.130.85]
14 99 ms 99 ms 99 ms 99 ms if-2-2.tcore2.L78-London.as6453.net [80.231.131.1]
15 97 ms 100 ms 97 ms 103 ms if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
16 98 ms 98 ms 116 ms 98 ms if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.30]
17 97 ms 103 ms 97 ms 98 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
18 98 ms 97 ms 97 ms 97 ms if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6]
19 * * * * [-]
Destination not reached in 35 hops
Is routed correctly no Paris hops
Quote Target Name: lb-onl-vh-wspub01.ubisoft.com
IP: 216.98.48.133
Date/Time: 10/09/2013 16:09:50 to 10/09/2013 16:10:30
1 0 ms * 0 ms 0 ms 0 ms 0 ms N/A home.gateway.home.gateway [192.168.1.254]
2 15 ms 13 ms 13 ms 13 ms 35 ms 13 ms N/A lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 13 ms 13 ms 13 ms 13 ms 13 ms 13 ms N/A link-a-central10.ptw-gw01.plus.net [212.159.2.148]
4 13 ms 13 ms 13 ms 13 ms 13 ms 12 ms N/A 248.core.access.plus.net [212.159.0.248]
5 17 ms 12 ms 163 ms 13 ms 13 ms 13 ms N/A te-4-2.car5.London1.Level3.net [217.163.45.249]
6 13 ms 13 ms 13 ms 15 ms 12 ms 14 ms N/A ae-52-52.csw2.London1.Level3.net [4.69.139.120]
7 13 ms 13 ms 12 ms 13 ms 47 ms 13 ms N/A ae-225-3601.edge3.London1.Level3.net [4.69.166.146]
8 13 ms 13 ms 13 ms 13 ms 13 ms 13 ms N/A Vlan533.icore1.LDN-London.as6453.net [195.219.83.101]
9 93 ms 92 ms 93 ms 93 ms 93 ms 93 ms N/A if-17-2.tcore1.L78-London.as6453.net [80.231.130.129]
10 100 ms 124 ms 91 ms 91 ms 91 ms 97 ms N/A if-2-2.tcore2.L78-London.as6453.net [80.231.131.1]
11 91 ms 93 ms 92 ms 91 ms 91 ms 91 ms N/A if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
12 91 ms 91 ms 92 ms 109 ms 91 ms 92 ms N/A if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.30]
13 91 ms 91 ms 99 ms 91 ms 91 ms 91 ms N/A if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
14 91 ms 91 ms 92 ms 91 ms 91 ms 91 ms N/A if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6]
Destination not reached in 35 hops
Even Tracert's to ubisoft.com 216.98.48.40 Go via Paris for me as said there was some network wide routing/peering changes made at around 6am which resulted in this ,
Quote Target Name: ubisoft.com
IP: 216.98.48.40
Date/Time: 10/09/2013 16:13:05
1 0 ms 0 ms home.gateway.home.gateway [192.168.1.254]
2 15 ms 13 ms lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 13 ms 13 ms link-b-central10.ptw-gw02.plus.net [212.159.2.150]
4 13 ms 13 ms 250.core.access.plus.net [212.159.0.250]
5 44 ms 42 ms ae1.pcl-cr02.plus.net [195.166.129.3]
6 13 ms 13 ms ae2.pcl-cr01.plus.net [195.166.129.6]
7 13 ms 13 ms xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
8 20 ms 19 ms ae-3-3.ebr1.Paris1.Level3.net [4.69.141.86]
9 20 ms 19 ms ae-71-71.csw2.Paris1.Level3.net [4.69.161.82]
10 20 ms 20 ms [4.69.168.72]
11 20 ms 20 ms ix-20-0.tcore1.PVU-Paris.as6453.net [80.231.153.65]
12 99 ms 99 ms if-12-2.tcore1.PYE-Paris.as6453.net [80.231.154.69]
13 109 ms 98 ms if-5-2.tcore1.L78-London.as6453.net [80.231.130.1]
14 99 ms 99 ms if-2-2.tcore2.L78-London.as6453.net [80.231.131.1]
15 97 ms 97 ms if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
16 100 ms 122 ms if-2-2.tcore2.MTT-Montreal.as6453.net [64.86.226.13]
17 98 ms 98 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
18 124 ms 100 ms if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6]
Destination not reached in 35 hops
Re: Looks like a routing issue to Ubisoft.com today
10-09-2013 9:08 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote tracert lb-lsg-prod.ubisoft.com
Tracing route to lb-lsg-prod.ubisoft.com [216.98.48.56]
over a maximum of 30 hops:
1 59 ms 99 ms 99 ms 192.168.1.254
2 23 ms 16 ms 22 ms lo0-central10.pcl-ag07.plus.net [195.166.xx.xx]
3 24 ms 15 ms 16 ms link-a-central10.pcl-gw01.plus.net [212.159.2.184]
4 16 ms 16 ms 19 ms 216.core.access.plus.net [212.159.0.216]
5 16 ms 15 ms 15 ms xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
6 26 ms 24 ms 23 ms ae-3-3.ebr1.Paris1.Level3.net [4.69.141.86]
7 23 ms 23 ms 22 ms ae-61-61.csw1.Paris1.Level3.net [4.69.161.78]
8 22 ms 22 ms 21 ms 4.69.168.8
9 105 ms 22 ms 23 ms ix-20-0.tcore1.PVU-Paris.as6453.net [80.231.153.65]
10 156 ms 104 ms 108 ms if-12-2.tcore1.PYE-Paris.as6453.net [80.231.154.69]
11 169 ms 103 ms 101 ms if-5-2.tcore1.L78-London.as6453.net [80.231.130.1]
12 317 ms 103 ms 127 ms if-2-2.tcore2.L78-London.as6453.net [80.231.131.1]
13 104 ms 104 ms 103 ms if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
14 317 ms 101 ms 100 ms if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.30]
15 153 ms 101 ms 102 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
16 141 ms 101 ms 110 ms if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6]
17 * * 66.198.96.18 reports: Destination net unreachable.
Checking with http://www.downforeveryoneorjustme.com the destination is down from there too.
Re: Looks like a routing issue to Ubisoft.com today
10-09-2013 9:16 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
jim:quote
Re: Looks like a routing issue to Ubisoft.com today
11-09-2013 12:02 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
We receive routes from upstream providers, how they route traffic in their network isn't anything we can easily change. With this you can see we pass it off to Level3, its after that you are seeing issues. The route for this prefix has been in our table for over 5 days:
216.98.48.0/20 *[BGP/170] 5d 17:22:31, MED 0, localpref 40, from 4.68.2.7
The only work done this morning that I know of was a software upgrade on a router that we don't receive routes for this prefix on (or at least not prefered routes).
Re: Looks like a routing issue to Ubisoft.com today
11-09-2013 2:19 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
But in any case ,they must have some contract with Plusnet ? As an ISP you surely can complain about the bad links , they are assigning ? for the last week or so AS6453.net links have been displaying the all too familiar congestion hump between 1am -3am
Re: Looks like a routing issue to Ubisoft.com today
11-09-2013 7:50 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
216.98.48.0/20 is a range of 4096 addresses up to 216.98.63.255. Looking at your original traceroute and the Level3 looking glass service it seems as though they have two peering points with AS6453. One routes via Paris the other doesn't which seems to be where your right and wrong are coming from. The problem here may not even be with Level3 if they are just receiving upstream prefixes from AS6453.
Re: Looks like a routing issue to Ubisoft.com today
11-09-2013 1:56 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
To me plusnet routing or something else within plusnets control was changed at 6am as a result of what ever was done to the core router at that time, as said other isp's that peer with level3 aren't seeing this Paris and back routing and if 216.98.48.133 can be routed correctly then so can 216.98.48.56
As the 3 Tracert's using level3's looking glass web site shows 2 routed correctly http://lookingglass.level3.net/traceroute/lg_tr_output.php So it must be that the endpoint plusnet use got changed
I can't stress enough the maintenance performed has caused this , probably it was a side effect, but never the less i feel it's within plusnets control , not level 3 or any other 3rd party
Also my tracert to 216.98.48.133 leaves plusnet via 248.core.access.plus.net where as 216.98.48.56 leaves plusnet only after transiting ae1.pcl-cr02.plus.net and ae2.pcl-cr01.plus.net which then finds this longer route via level 3 , so please change this to the same route as 216.98.48.133 takes . back how it was
Another observation several tracert's pass through ae2.ptw-cr01.plus.net to get to outside destinations would seem to be the correct way to route my traffic as im on ptw ag02 gateway, the problematic IP is being routed to PLC core routers adding 2 internal hops and IMO could be the reason for this
And if you can't or won't change internal routing, then you should perhaps give level3 a call and make them aware of the London paris london fault
Re: Looks like a routing issue to Ubisoft.com today
12-09-2013 6:47 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
and see if all gateways routed traffic to the ubisoft.com IP the same , which they don't
Target Name: lb-lsg-prod.ubisoft.comNo London >>>Paris<<<London>>>>NewYork But routing to
IP: 216.98.48.56
Date/Time: 12/09/2013 17:45:26 to 12/09/2013 18:37:49
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 1007 580 57.6 0 1 0 home.gateway.home.gateway [192.168.1.254]
2 1007 0 0.0 12 671 20 [195.166.128.184]
3 1007 0 0.0 12 127 12 link-b-central10.pcl-gw02.plus.net [212.159.2.170]
4 1007 0 0.0 12 132 13 202.core.access.plus.net [212.159.0.202]
5 1007 0 0.0 12 77 15 ae2.pcl-cr01.plus.net [195.166.129.6]
6 1007 0 0.0 12 141 14 ae1.ptw-cr01.plus.net [195.166.129.0]
7 1007 16 1.6 12 228 37 [217.163.45.181]
8 1007 0 0.0 12 32 13 ae-52-52.csw2.London1.Level3.net [4.69.139.120]
9 983 0 0.0 12 78 14 ae-226-3602.edge3.London1.Level3.net [4.69.166.150]
10 1006 0 0.0 12 62 13 Vlan533.icore1.LDN-London.as6453.net [195.219.83.101]
11 1006 54 5.4 92 149 95 if-17-2.tcore1.L78-London.as6453.net [80.231.130.129]
12 1006 1 0.1 91 153 93 if-2-2.tcore2.L78-London.as6453.net [80.231.131.1]
13 1006 1 0.1 89 159 93 if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
14 1006 0 0.0 90 162 92 if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.30]
15 1006 0 0.0 89 169 92 if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
16 1006 0 0.0 89 181 92 if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6]
17 1006 1006 100.0 0 0 0 [-]
Destination not reached in 35 hops
Target Name: steampowered.com
IP: 208.64.202.68
Date/Time: 12/09/2013 17:27:54 to 12/09/2013 18:40:52
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 1007 487 48.4 0 1 0 home.gateway.home.gateway [192.168.1.254]
2 1007 0 0.0 12 377 21 lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 1007 0 0.0 12 44 12 link-b-central10.pcl-gw02.plus.net [212.159.2.170]
4 1007 0 0.0 12 101 13 202.core.access.plus.net [212.159.0.202]
5 1007 0 0.0 12 113 15 ae2.pcl-cr01.plus.net [195.166.129.6]
6 1007 0 0.0 12 69 14 xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
7 1007 2 0.2 157 178 158 ae-3-3.ebr1.Paris1.Level3.net [4.69.141.86]
8 1007 0 0.0 157 227 157 ae-71-71.csw2.Paris1.Level3.net [4.69.161.82]
9 1007 0 0.0 156 176 156 ae-72-72.ebr2.Paris1.Level3.net [4.69.161.97]
10 1007 2 0.2 157 190 157 ae-44-44.ebr2.Washington1.Level3.net [4.69.137.62]
11 1007 1 0.1 157 194 158 [4.69.202.62]
12 1007 0 0.0 157 240 157 ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
13 1007 0 0.0 156 177 157 ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
14 1007 0 0.0 155 213 156 ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
15 1007 0 0.0 157 175 158 ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
16 1007 3 0.3 158 225 161 ae-2-52.edge1.Seattle3.Level3.net [4.69.147.170]
17 1007 4 0.4 157 203 158 CENTURYTEL.edge1.Seattle3.Level3.net [4.59.232.74]
18 1007 2 0.2 157 266 159 [205.196.6.33]
19 1007 3 0.3 158 178 158 fw01-core.tuk.valve.net [208.64.202.21]
20 1007 1 0.1 158 181 158 208-64-202-68.valve.net [208.64.202.68]
Is As is the other ubisoft.com IP i made reference to, this is from PCL-ag03
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: Looks like a routing issue to Ubisoft.com toda...