cancel
Showing results for 
Search instead for 
Did you mean: 

AS6453.net peering sucks

deathtrap
Grafter
Posts: 1,064
Thanks: 4
Registered: ‎23-04-2013

AS6453.net peering sucks

As the traffic is routed over AS6453.net links from the uk to ubisoft.com  the game uses IP 216.98.48.56 to connect  on port 3074
Since joining plusnet  latency to this host has increased  from 89ms to 125-140ms (spiking every few seconds) As for some reason AS6453.net  are now  routing to montreal via Chicago adding latency to the rtt, Therefore i would like to ask plusnet , if it would be possible for them to peer with a different carrier instead of AS6435.net for traffic to ubisoft's  server farms in Canada
The ping time i see currently is the highest iv'e seen it, I'm not blaming plusnet ,but i think that they should review their peering agreements  or have a word with level3 as they carry the traffic to AS46453.net and some other overseas destinations  from plusnet's core network, It would be nice if they found a better carrier with lower latency , So could my suggestion be passed on to the person or persons responsible for peering /routing ? thank's

202 REPLIES 202
Mattz0r
Rising Star
Posts: 620
Fixes: 1
Registered: ‎21-07-2010

Re: AS6453.net peering sucks

Hey There,
I think the as6453.net stuff is later on in the chain than directly with Plusnet.
If you look at the traceroute, does as6453.net come directly after plus.net hops?
I'm not on Plusnet myself, but a traceroute to that, goes via cogent first, then as6453.net
Regards,
Matt
Gus
Aspiring Pro
Posts: 3,236
Thanks: 26
Fixes: 3
Registered: ‎31-07-2007

Re: AS6453.net peering sucks

AS6453.net are beyond level3 so outwith PN's control, your only hope is the bring it to light of the game devs who will have a say
FTTP 500 regrade from Tues 28th November
deathtrap
Grafter
Posts: 1,064
Thanks: 4
Registered: ‎23-04-2013

Re: AS6453.net peering sucks

Unfortunately this is ubisoft,& they don't care about customers they don't even support some of their games , What about plusnet approaching level3 ,? There are other peering carriers why do most isp's have to use this unreliable company
Mattz0r
Rising Star
Posts: 620
Fixes: 1
Registered: ‎21-07-2010

Re: AS6453.net peering sucks

As mentioned before, AS6453.net isn't directly connected to Plusnet - Level(3) is one of the most popular and decent global carriers. Usually the fastest path is chosen.
If there aren't any direct links to Canada, then going via America is the only option.
It's nothing to do with Plusnet at all.
- But it's also to do with what providers the end point uses for connectivity. They might not have a choice at all.
Cheers,
Matt
Kelly
Hero
Posts: 5,497
Thanks: 380
Fixes: 9
Registered: ‎04-04-2007

Re: AS6453.net peering sucks

Get some traceroutes showing the path with the problems and we'll take a look at who we need to yell at.
Kelly Dorset
Ex-Broadband Service Manager
Blim
Grafter
Posts: 462
Registered: ‎06-03-2012

Re: AS6453.net peering sucks

I'm not being funny but I just want ot play games. This seems a never ending story. This isn't a gaming service!
Gus
Aspiring Pro
Posts: 3,236
Thanks: 26
Fixes: 3
Registered: ‎31-07-2007

Re: AS6453.net peering sucks

Target Name: lb-lsg-prod.ubisoft.com
        IP: 216.98.48.56
  Date/Time: 13/11/2013 6:39:25 PM
1  27 ms  32 ms  [192.168.1.254]
2  44 ms  44 ms  lo0-central10.pcl-ag08.plus.net [195.166.128.189]
3  44 ms  44 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.188]
4  47 ms  43 ms  xe-9-1-0.pcl-cr01.plus.net [212.159.0.220]
5  44 ms  44 ms  xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
6  52 ms  51 ms  ae-3-3.ebr1.Paris1.Level3.net [4.69.141.86]
7  50 ms  53 ms  ae-61-61.csw1.Paris1.Level3.net [4.69.161.78]
8  50 ms  50 ms  [4.69.168.8]
9  51 ms  51 ms  ix-20-0.tcore1.PVU-Paris.as6453.net [80.231.153.65]
10  144 ms  143 ms  if-12-2.tcore1.PYE-Paris.as6453.net [80.231.154.69]
11  151 ms  144 ms  if-5-2.tcore1.L78-London.as6453.net [80.231.130.1]
12  150 ms  145 ms  if-1-2.tcore2.L78-London.as6453.net [80.231.130.122]
13  145 ms  145 ms  if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
14  150 ms  154 ms  if-12-6.tcore1.CT8-Chicago.as6453.net [216.6.99.46]
15  146 ms  145 ms  if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
16  145 ms  147 ms  if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
17  *      *      [-]
18  *      *      [-]
19  *      *      [-]
20  N/A      *      [66.198.96.18]
21  *      *      [-]
22  *      *      [-]
23  *      *      [-]
24  *      *      [-]
25  *      *      [-]
26  *      *      [-]
27  *      *      [-]
28  *      *      [-]
29  *      *      [-]
30  *      *      [-]
31  *      *      [-]
32  *      *      [-]
33  *      *      [-]
34  *      *      [-]
35  *      *      [-]
Destination not reached in 35 hops

@Blim thats why gaming is the litmus test of online, we see the effects first.
FTTP 500 regrade from Tues 28th November
deathtrap
Grafter
Posts: 1,064
Thanks: 4
Registered: ‎23-04-2013

Re: AS6453.net peering sucks

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|               home.gateway.home.gateway -    0 |  202 |  202 |    0 |    0 |    1 |    0 |
|         lo0-central10.pcl-ag07.plus.net -    0 |  201 |  201 |   13 |   18 |  257 |   13 |
|      link-b-central10.pcl-gw02.plus.net -    0 |  201 |  201 |   12 |   13 |   31 |   13 |
|              xe-9-0-0.pcl-cr02.plus.net -    0 |  202 |  202 |   12 |   15 |   73 |   13 |
|                   ae1.ptw-cr02.plus.net -    0 |  201 |  201 |   13 |   15 |   79 |   13 |
|                   ae2.ptw-cr01.plus.net -    0 |  202 |  202 |   12 |   14 |   51 |   13 |
|          te-3-4.car5.London1.Level3.net -   12 |  134 |  119 |   13 |   57 |  319 |   23 |
|        ae-52-52.csw2.London1.Level3.net -    0 |  201 |  201 |   13 |   13 |   22 |   13 |
|    ae-225-3601.edge3.London1.Level3.net -    0 |  201 |  201 |   13 |   13 |   31 |   13 |
|    ix-20-0.tcore1.LDN-London.as6453.net -    0 |  201 |  201 |   13 |   13 |   46 |   13 |
|    if-17-2.tcore1.L78-London.as6453.net -    1 |  197 |  196 |  111 |  112 |  135 |  112 |
|     if-2-2.tcore2.L78-London.as6453.net -    0 |  201 |  201 |  111 |  116 |  162 |  140 |
|   if-20-2.tcore2.NYY-NewYork.as6453.net -    0 |  201 |  201 |  109 |  111 |  152 |  110 |
|   if-12-6.tcore1.CT8-Chicago.as6453.net -    0 |  201 |  201 |  110 |  112 |  148 |  110 |
|   if-22-2.tcore2.CT8-Chicago.as6453.net -    0 |  201 |  201 |  110 |  116 |  149 |  128 |
|   if-3-2.tcore1.W6C-Montreal.as6453.net -    0 |  201 |  201 |  110 |  116 |  161 |  130 |
|        Destination network unreachable. -  100 |   43 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|        Destination network unreachable. -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|        Destination network unreachable. -  100 |   40 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
  WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 Mine for comparison  even though it doesn't  route london paris london, before routing on to new york the min latency is 110ms or higher, when normally it should be sub 100ms when on fast-path it used to be 89-90ms when i first signed up and was for several months  the route the AS links used to take where New York  >>> Montreal not  Chicago which is geographically in the opposite direction
It would seem that they AS6453.net have for some reason changed the normal routing to go via Chicago then Montreal here is a better tracert  from another ISP which shows a better result of 95ms
Just to add the routing which seems to be causing the increase in latency got changed early on the morning of the 5th November , It's probable it's congestion on AS6453.net side,or their direct link's to Montreal are down,  their looking glass doesn't provide any info on such issues
deathtrap
Grafter
Posts: 1,064
Thanks: 4
Registered: ‎23-04-2013

Re: AS6453.net peering sucks

Are there any updates on this issue,Kelly ?
orbrey
Plusnet Alumni (retired)
Plusnet Alumni (retired)
Posts: 10,540
Registered: ‎18-07-2007

Re: AS6453.net peering sucks

Don't suppose the changes this post refers to have made any difference did they?
deathtrap
Grafter
Posts: 1,064
Thanks: 4
Registered: ‎23-04-2013

Re: AS6453.net peering sucks

Not directly it doesn't But it does highlight a similar issue with the way  That the IP the game i play uses 216.98.48.56 is getting routed  indirectly  (London to Paris back to London again) before transiting to NewYork  that is for some reason apparent if connected to some of your Gateways, Fortunately not all of them,
Which if i currently wasn't using a gateway which routes  London  directly to NewYork ,Which is surely the correct way in which to route traffic? I would have that issue in the other post on top of this issue of AS6453.net  routing traffic from NewYork  to Chicago!!! Before routing to Montreal Are AS6453.net for real?
Hence my enquiry regarding the use of a different peering company, who preferably routes traffic directly
For other Tracert results it does seem that AS6453.net  have changed the routing path  from NewYork to Montreal for some reason, But other tracert results are giving a slightly better /lower ping Maybe level3 need a prodding re this
From Level 3 looking glass
Traceroute results from London, England (2)
to 216.98.48.56(lb-lsg-prod.ubisoft.com)
 1 ae-15-15.edge3.London2.Level3.net (4.69.200.85) 48 msec 0 msec 60 msec
 2 ae-3-3.ebr1.Paris1.Level3.net (4.69.141.86) 92 msec 28 msec 28 msec
 3 ae-71-71.csw2.Paris1.Level3.net (4.69.161.82) 16 msec
   ae-81-81.csw3.Paris1.Level3.net (4.69.161.86) 52 msec
   ae-91-91.csw4.Paris1.Level3.net (4.69.161.90) 108 msec
 4 4.69.168.8 112 msec
   4.69.168.136 44 msec
   4.69.168.200 52 msec
 5 ix-20-0.tcore1.PVU-Paris.as6453.net (80.231.153.65) [AS6453 {GLOBEINTERNET}] 204 msec 204 msec 204 msec
 6 if-2-2.tcore1.PYE-Paris.as6453.net (80.231.154.18) [AS6453 {GLOBEINTERNET}] 216 msec 200 msec
   if-12-2.tcore1.PYE-Paris.as6453.net (80.231.154.69) [AS6453 {GLOBEINTERNET}] 204 msec
 7 if-3-6.tcore1.L78-London.as6453.net (80.231.130.85) [AS6453 {GLOBEINTERNET}] 124 msec 212 msec
   if-5-2.tcore1.L78-London.as6453.net (80.231.130.1) [AS6453 {GLOBEINTERNET}] 76 msec
 8 if-1-2.tcore2.L78-London.as6453.net (80.231.130.122) [AS6453 {GLOBEINTERNET}] 204 msec
   if-2-2.tcore2.L78-London.as6453.net (80.231.131.1) [AS6453 {GLOBEINTERNET}] 216 msec 212 msec
 9 if-20-2.tcore2.NYY-NewYork.as6453.net (216.6.99.13) [AS6453 {GLOBEINTERNET}] 204 msec *  136 msec
10 if-12-6.tcore1.CT8-Chicago.as6453.net (216.6.99.46) [AS6453 {GLOBEINTERNET}] 220 msec *  108 msec
11 if-22-2.tcore2.CT8-Chicago.as6453.net (64.86.79.1) [AS6453 {GLOBEINTERNET}] 124 msec 112 msec *
12 if-3-2.tcore1.W6C-Montreal.as6453.net (66.198.96.45) [AS6453 {GLOBEINTERNET}] 132 msec 116 msec 120 msec
13  *  *
   66.198.96.18 [AS6453 {GLOBEINTERNET}] !filtered
  From AS6453.net looking glass
Router: gin-ldn-core4
Site: UK, London, LDN
Command: traceroute ip 216.98.48.56

Tracing the route to lb-lsg-prod.ubisoft.com (216.98.48.56)
 1 if-4-3-2-0.tcore2.LDN-London.as6453.net (80.231.20.37) [MPLS: Label 302065 Exp 0] 96 msec
   if-0-1-3-0.tcore2.LDN-London.as6453.net (80.231.62.25) [MPLS: Label 302065 Exp 0] 96 msec
   if-3-1-2-12.tcore2.LDN-London.as6453.net (80.231.62.29) [MPLS: Label 302065 Exp 0] 100 msec
 2 if-15-2.tcore2.L78-London.as6453.net (80.231.131.117) [MPLS: Label 725890 Exp 0] 96 msec 96 msec 96 msec
 3 if-20-2.tcore2.NYY-NewYork.as6453.net (216.6.99.13) [MPLS: Label 349761 Exp 0] 96 msec 108 msec 96 msec
 4 if-12-6.tcore1.CT8-Chicago.as6453.net (216.6.99.46) [MPLS: Label 384049 Exp 0] 100 msec 100 msec 96 msec
 5 if-22-2.tcore2.CT8-Chicago.as6453.net (64.86.79.1) [MPLS: Label 391169 Exp 0] 100 msec 96 msec 96 msec
 6 if-3-2.tcore1.W6C-Montreal.as6453.net (66.198.96.45) 112 msec 96 msec 100 msec

And some direct routing from London to NewYork
Traceroute results from London, England
to 216.98.48.56(lb-lsg-prod.ubisoft.com)
1 ae-52-52.csw2.London1.Level3.net (4.69.139.120) 0 msec
   ae-51-51.csw1.London1.Level3.net (4.69.139.88) 0 msec
   ae-52-52.csw2.London1.Level3.net (4.69.139.120) 8 msec
 2 ae-115-3501.edge3.London1.Level3.net (4.69.166.130) 0 msec
   ae-225-3601.edge3.London1.Level3.net (4.69.166.146) 228 msec
   ae-116-3502.edge3.London1.Level3.net (4.69.166.134) 0 msec
 3 ix-20-0.tcore1.LDN-London.as6453.net (195.219.83.101) [AS6453 {GLOBEINTERNET}] 0 msec 0 msec 0 msec
 4  *
   if-17-2.tcore1.L78-London.as6453.net (80.231.130.129) [AS6453 {GLOBEINTERNET}] 408 msec 212 msec
 5 if-1-2.tcore2.L78-London.as6453.net (80.231.130.122) [AS6453 {GLOBEINTERNET}] 160 msec
   if-2-2.tcore2.L78-London.as6453.net (80.231.131.1) [AS6453 {GLOBEINTERNET}] 204 msec 228 msec
 6 if-20-2.tcore2.NYY-NewYork.as6453.net (216.6.99.13) [AS6453 {GLOBEINTERNET}] 204 msec *  *
 7 if-12-6.tcore1.CT8-Chicago.as6453.net (216.6.99.46) [AS6453 {GLOBEINTERNET}] 112 msec 92 msec 96 msec
 8 if-22-2.tcore2.CT8-Chicago.as6453.net (64.86.79.1) [AS6453 {GLOBEINTERNET}] 92 msec 96 msec 96 msec
 9 if-3-2.tcore1.W6C-Montreal.as6453.net (66.198.96.45) [AS6453 {GLOBEINTERNET}] 92 msec 132 msec 92 msec
10  *  *  *
11  *  *  *
12  *  *  *
13  *  *  *
14 66.198.96.18 [AS6453 {GLOBEINTERNET}] !filtered  *  *

http://lookingglass.level3.net/index.html  http://lg.as6453.net/lg/ Level3 aren't exactly brilliant on peering either certainly to montreal and other transatlantic routes, and all the rtt results are higher than they where just over a month ago , for instance Newyork was nearly always 80ms or less and my ping times with the different ISP's for years have never been over 100ms  the average for me was 95ms max 98ms  and as i said until they started routing via Chicago  on plusnet  it was 89-90ms more or less all the time, only times it increased  apart from the paris level3  routing  as per other post, was what appeared to be peak time congestion  effects  which could occur at different times of the day or night , So could be level3  or AS6453.net are/have been  running some links too hot at times
Blim
Grafter
Posts: 462
Registered: ‎06-03-2012

Re: AS6453.net peering sucks

back in the day we used have 75ms ping to US servers in ut2k4, witch is about right if you get the calculator out based on the speed of a electron or the speed of light. So mutch for fibre speeds.
deathtrap
Grafter
Posts: 1,064
Thanks: 4
Registered: ‎23-04-2013

Re: AS6453.net peering sucks

Well  still no news as to when or if this will be resolved ? I done a little digging and it would appear that at least some providers are  using different peering to Level 3 and AS6453.net  http://www.wipmania.com/en/trace/216.98.48.56/?s=&point=69
Gus
Aspiring Pro
Posts: 3,236
Thanks: 26
Fixes: 3
Registered: ‎31-07-2007

Re: AS6453.net peering sucks

a thousand words attached
FTTP 500 regrade from Tues 28th November