Tracerts to BurstNET Network

[Troy [ASAPweb]]

Thought I'd start this - I'm seeing some really bad traffic flows here (not saying it's BurstNET's fault here)
Can some people post some from their area and do some comparing of the networks to our servers?

This is run from Kingston Ontario Canada:
C:\>tracert asapwebhosting.com

Tracing route to asapwebhosting.com [64.191.80.213]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 25 ms 11 ms 10.70.96.1
3 8 ms 14 ms 29 ms d226-12-1.home.cgocable.net [24.226.12.1]
4 9 ms 10 ms 9 ms cgowave-0-109.cgocable.net [24.226.0.109]
5 9 ms 10 ms 11 ms ra1sh-pos8-3.mt.bigpipeinc.com [66.244.223.185]
6 10 ms 9 ms 10 ms rc1sh-ge9-0.mt.shawcable.net [66.163.66.9]
7 20 ms 21 ms 21 ms rc1hu-pos6-0.ny.shawcable.net [66.163.76.90]
8 105 ms 104 ms 103 ms core01.ams03.atlas.cogentco.com [195.69.144.124]
9 107 ms 109 ms 110 ms p5-0.core01.lon01.atlas.cogentco.com [130.117.1.58]
10 108 ms 110 ms 107 ms p6-0.core01.jfk01.atlas.cogentco.com [154.54.1.57]
11 107 ms * 107 ms p15-0.core02.jfk01.atlas.cogentco.com [66.28.4.166]
12 108 ms 111 ms 110 ms p12-0.core02.jfk02.atlas.cogentco.com [66.28.4.169]
13 108 ms 107 ms 107 ms p14-0.core01.phl01.atlas.cogentco.com [66.28.4.2]
14 113 ms * 109 ms g7.ba21.b003003-1.phl01.atlas.cogentco.com [38.112.34.138]
15 * 108 ms 111 ms BurstNet.demarc.cogentco.com [38.112.11.122]
16 116 ms 117 ms 115 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.45]
17 115 ms 115 ms 117 ms 66.197.191.82
18 116 ms 116 ms 115 ms ns1.asapwebhosting.com [64.191.80.213]

Trace complete.
Hop 8 is nasty
Not sure if that's why but I've noticed a definate decrease in load times on my server - people are starting to complain lol
Can't say I really blame them

[Stemel UK]

Run from Blueyonder in UK

Tracing route to stemel.com [66.197.144.101]
over a maximum of 30 hops:

1 28 ms 7 ms 11 ms 10.33.64.1
2 10 ms 31 ms 8 ms gsr01-du.blueyonder.co.uk [62.31.176.129]
3 19 ms 29 ms 15 ms 172.18.4.37
4 15 ms 18 ms 13 ms 194.117.136.134
5 17 ms 16 ms 14 ms 194.117.136.174
6 13 ms 16 ms 13 ms 195.66.224.185
7 107 ms 105 ms 120 ms p6
0.core02.jfk01.atlas.cogentco.com [154.54.1.5]
8 104 ms 102 ms 103 ms p12-0.core02.jfk02.atlas.cogentco.com [66.28.4.169]
9 101 ms 101 ms 100 ms p14-0.core01.phl01.atlas.cogentco.com [66.28.4.2]
10 108 ms 103 ms 100 ms g8.ba21.b003003-1.phl01.atlas.cogentco.com [38.112.34.142]
11 160 ms 158 ms 146 ms BurstNet.demarc.cogentco.com [38.112.11.122]
12 240 ms 254 ms 242 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.45]
13 248 ms 249 ms 250 ms server.rhdns.com [66.197.144.101]

Trace complete.

[unix1]

1-6 <1 <1 <1 local

7 25 ms 25 ms 56 ms war-b1-pos14-0.telia.net [213.248.76.117]

8 42 ms 64 ms 42 ms hbg-bb1-pos1-2-0.telia.net [213.248.64.201]

9 50 ms 48 ms 47 ms adm-bb1-pos7-0-0.telia.net [213.248.65.153]

10 55 ms 56 ms 56 ms ldn-bb1-pos7-0-0.telia.net [213.248.65.149]

11 54 ms 56 ms 54 ms ldn-b1-pos3-0.telia.net [213.248.74.6]

12 54 ms 55 ms 54 ms btn-pccw.c.telia.net [213.248.74.46]

13 130 ms 130 ms 128 ms pos2-0.cr01.phl02.pccwbtn.net [63.218.30.33]

14 222 ms 222 ms 226 ms hostnoc.ge3-0.2.cr01.phl02.pccwbtn.net [63.218.31.6]

15 285 ms 280 ms 267 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.45]

16 269 ms 270 ms 274 ms 66.197.191.82

17 320 ms 302 ms 294 ms my.server.com

Any Fire???? :mad:

[Matt [MainArea]]

Originally posted by osfdeath
Thought I'd start this - I'm seeing some really bad traffic flows here (not saying it's BurstNET's fault here)
Can some people post some from their area and do some comparing of the networks to our servers?

This is run from Kingston Ontario Canada:

Hop 8 is nasty
Not sure if that's why but I've noticed a definate decrease in load times on my server - people are starting to complain lol
Can't say I really blame them
I have no clue what's wrong... you're going from Canada, to Amsterdam, to London, to NY, then to Burst.

The other traces that some people posted do look odd, not sure why it's happening.

- Matt

[Troy [ASAPweb]]

::shrug::

I've had alot of complaints about the connection to burstnet's network. Here's one from central PA (one of my customers)

Tracing route to osfhome.com [64.191.80.217]
over a maximum of 30 hops:

1 16 ms <10 ms 15 ms 10.229.146.1
2 16 ms <10 ms 15 ms gateway-g5-0-0-ephblocal1.eph.ptd.net [216.144.187.222]
3 16 ms 16 ms 15 ms gateway2-atm4-0-0-305-sm22eph.sm.ptd.net [207.44.124.197]
4 31 ms 16 ms 16 ms POS1-3.GW8.PHL1.ALTER.NET [157.130.58.133]
5 15 ms 32 ms 15 ms 552.at-4-0-0.CL2.PHL1.ALTER.NET [152.63.39.206]
6 16 ms 31 ms 16 ms 0.so-5-0-0.XL2.DCA6.ALTER.NET [152.63.41.142]
7 15 ms 32 ms 15 ms POS7-0.BR4.DCA6.ALTER.NET [152.63.41.233]
8 16 ms 31 ms 16 ms 204.255.173.10
9 16 ms 15 ms 31 ms p1-2.core01.dca01.atlas.cogentco.com [154.54.2.249]
10 31 ms 62 ms 32 ms p4-0.core01.phl01.atlas.cogentco.com [66.28.4.18]
11 31 ms 31 ms 16 ms g8.ba21.b003003-1.phl01.atlas.cogentco.com [38.112.34.142]
12 141 ms 109 ms 125 ms BurstNet.demarc.cogentco.com [38.112.11.122]
13 188 ms 219 ms 218 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.45]
14 203 ms 203 ms 204 ms 66.197.191.82
15 219 ms 234 ms 219 ms 64.191.80.217

Trace complete.

[XILO-Matt]

Nothing odd here... very good actually..

From RedBus;

[root@pingu root]# traceroute gonzo.xilo.net
traceroute to gonzo.xilo.net (66.197.206.101), 30 hops max, 38 byte packets
1 core-gw.london.tsn.uk.com (80.253.115.254) 0.350 ms 0.304 ms 0.272 ms
2 ldn-s2-rou-1001.UK.eurorings.net (134.222.109.181) 19.029 ms 8.550 ms 9.895 ms
3 cr02.ldn01.pccwbtn.net (195.66.224.167) 0.978 ms 0.935 ms 0.778 ms
4 pos2-0.cr01.phl02.pccwbtn.net (63.218.30.33) 80.048 ms 99.213 ms 74.212 ms
5 hostnoc.ge3-0.2.cr01.phl02.pccwbtn.net (63.218.31.6) 78.691 ms 77.376 ms 77.852 ms
6 ge-7-0-ctsi.rtr0.scra1.hostnoc.net (66.197.191.45) 84.245 ms 83.764 ms 84.006 ms
7 gonzo (66.197.206.101) 85.990 ms 84.949 ms 84.248 ms

From home ADSL;

C:\Documents and Settings\Matt>tracert gonzo.xilo.net

Tracing route to gonzo.xilo.net [66.197.206.101]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms x.x.x.x [62.69.x.x]
2 3 ms 2 ms 2 ms x.x.x.x [62.69.x.x]
3 * * * Request timed out.
4 24 ms 23 ms 22 ms no-reverse.bsve.net [213.253.141.2]
5 23 ms 22 ms 23 ms no-reverse.bsve.net [213.253.141.1]
6 24 ms 23 ms 22 ms cr02.ldn01.pccwbtn.net [195.66.224.167]
7 98 ms 98 ms 96 ms pos2-0.cr01.phl02.pccwbtn.net [63.218.30.33]
8 103 ms 104 ms 103 ms hostnoc.ge3-0.2.cr01.phl02.pccwbtn.net [63.218.3
1.6]
9 112 ms 111 ms 110 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.4
5]
10 111 ms 110 ms 112 ms gonzo.xnoc.net [66.197.206.101]

[Troy [ASAPweb]]

6 24 ms 23 ms 22 ms cr02.ldn01.pccwbtn.net [195.66.224.167]
7 98 ms 98 ms 96 ms pos2-0.cr01.phl02.pccwbtn.net [63.218.30.33]
That's not all that great IMO

[BurstCEO]

He's coming in from London, so that is not too bad of a trace (74ms hop)...

SMA
PRES/CEO
BURSTNET

[Troy [ASAPweb]]

True but that hop is in US (pccwbtn.net which is ns-corp.cais.net in VA)
It's what all of us are seeing - a larger hop just before getting to the BurstNET network.

[BurstCEO]

6 24 ms 23 ms 22 ms cr02.ldn01.pccwbtn.net [195.66.224.167]
7 98 ms 98 ms 96 ms pos2-0.cr01.phl02.pccwbtn.net [63.218.30.33]


Incorrect...hop 6 to hop 7 goes from London (ldn01) to Philadelphia (phl02)


As far as Cogent trace you posted, that had to have been during the issues on their nework, as it is smooth as can be now to Prolog/PennTeleData (ptd.net)

root@inter [/backup/cpbackup/daily]# traceroute 216.144.187.222
traceroute to 216.144.187.222 (216.144.187.222), 30 hops max, 38 byte packets
1 ge-6-0-core.scr1.hostnoc.net (66.96.192.1) 0.220 ms 1.868 ms 0.303 ms
2 66.197.191.46 (66.197.191.46) 6.973 ms 7.300 ms 6.851 ms
3 g5.ba21.b003003-1.phl01.atlas.cogentco.com (38.112.11.121) 7.454 ms 7.515 ms 7.522 ms
4 g9-0.core01.phl01.atlas.cogentco.com (38.112.34.141) 7.358 ms 7.495 ms 7.458 ms
5 p5-0.core02.jfk02.atlas.cogentco.com (66.28.4.1) 9.970 ms 9.830 ms 20.231 ms
6 p6-0.core01.jfk05.atlas.cogentco.com (154.54.1.166) 9.833 ms 9.728 ms 16.172 ms
7 so-0-2-2.BR1.NYC4.ALTER.NET (204.255.169.33) 9.699 ms 9.939 ms 10.003 ms
8 0.so-6-0-0.XL2.NYC4.ALTER.NET (152.63.21.82) 10.009 ms 9.979 ms 10.080 ms
9 0.so-3-1-0.XL2.NYC9.ALTER.NET (152.63.21.14) 10.266 ms 21.896 ms 10.205 ms
10 0.so-0-0-0.XR2.NYC9.ALTER.NET (152.63.9.89) 10.358 ms 10.352 ms 10.235 ms
11 180.ATM7-0.GW8.NYC9.ALTER.NET (152.63.24.153) 9.955 ms 9.921 ms 10.303 ms
12 Pentele-gw.customer.alter.net (65.206.120.230) 14.564 ms 14.052 ms 14.763 ms
13 gateway-atm1-0-0-315-eph2pal.eph.ptd.net (207.44.121.186) 20.692 ms


SMA
PRES/CEO
BURSTNET

[Troy [ASAPweb]]

My bad - didn't look up both IPs :)

Date is on my trace - here's another one:
Tracing route to asapwebhosting.com [64.191.80.213]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 6 ms 6 ms 10.70.96.1
3 16 ms 9 ms 8 ms d226-12-1.home.cgocable.net [24.226.12.1]
4 11 ms 10 ms 21 ms cgowave-0-109.cgocable.net [24.226.0.109]
5 11 ms 11 ms 11 ms ra1sh-pos8-3.mt.bigpipeinc.com [66.244.223.185]
6 10 ms 9 ms 10 ms rc1sh-ge9-0.mt.shawcable.net [66.163.66.9]
7 31 ms 22 ms 21 ms rc1hu-pos6-0.ny.shawcable.net [66.163.76.90]
8 103 ms 102 ms 103 ms core01.ams03.atlas.cogentco.com [195.69.144.124]
9 109 ms 107 ms 108 ms p5-0.core01.lon01.atlas.cogentco.com [130.117.1.58]
10 107 ms 108 ms 128 ms p6-0.core01.jfk01.atlas.cogentco.com [154.54.1.57]
11 107 ms 107 ms 107 ms p12-0.core01.jfk02.atlas.cogentco.com [66.28.4.10]
12 111 ms 107 ms 108 ms p15-0.core02.jfk02.atlas.cogentco.com [66.28.4.14]
13 113 ms 107 ms 108 ms p14-0.core01.phl01.atlas.cogentco.com [66.28.4.2]
14 108 ms 107 ms 109 ms g7.ba21.b003003-1.phl01.atlas.cogentco.com [38.112.34.138]
15 110 ms 108 ms 107 ms BurstNet.demarc.cogentco.com [38.112.11.122]
16 113 ms 128 ms 116 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.45]
17 114 ms 115 ms 113 ms 66.197.191.82
18 116 ms 124 ms 115 ms ns1.asapwebhosting.com [64.191.80.213]

Trace complete.

Still a jump @ cogentco.com - never used to do that ;)

[Troy [ASAPweb]]

Wow are these guys ever gonna get this resolved?
Like a freaking ping pong ball over here :(

Tracing route to asapwebhosting.com [64.191.80.213]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 73 ms 8 ms 9 ms 10.70.96.1
3 28 ms 20 ms 8 ms d226-12-1.home.cgocable.net [24.226.12.1]
4 62 ms 242 ms 10 ms cgowave-0-109.cgocable.net [24.226.0.109]
5 81 ms 210 ms 16 ms ra1sh-pos8-3.mt.bigpipeinc.com [66.244.223.185]
6 11 ms 13 ms 60 ms rc1sh-ge9-0.mt.shawcable.net [66.163.66.9]
7 29 ms 108 ms 68 ms rc1hu-pos6-0.ny.shawcable.net [66.163.76.90]
8 166 ms 184 ms 198 ms core01.ams03.atlas.cogentco.com [195.69.144.124]
9 137 ms 363 ms 379 ms p5-0.core01.lon01.atlas.cogentco.com [130.117.1.58]
10 187 ms 389 ms 358 ms p6-0.core01.jfk01.atlas.cogentco.com [154.54.1.57]
11 119 ms 316 ms 337 ms p12-0.core01.jfk02.atlas.cogentco.com [66.28.4.10]
12 295 ms 181 ms 178 ms p15-0.core02.jfk02.atlas.cogentco.com [66.28.4.14]
13 229 ms * 106 ms p14-0.core01.phl01.atlas.cogentco.com [66.28.4.2]
14 399 ms 372 ms * g7.ba21.b003003-1.phl01.atlas.cogentco.com [38.112.34.138]
15 110 ms 325 ms 357 ms BurstNet.demarc.cogentco.com [38.112.11.122]
16 113 ms 394 ms 410 ms ge-7-0-ctsi.rtr0.scra1.hostnoc.net [66.197.191.45]
17 118 ms 294 ms 163 ms 66.197.191.82
18 152 ms 174 ms 140 ms ns1.asapwebhosting.com [64.191.80.213]

Trace complete.

[Matt [MainArea]]

Originally posted by osfdeath
Wow are these guys ever gonna get this resolved?
Like a freaking ping pong ball over here :(
That's a problem with your ISP's peering. You're getting routed through Amsterdam & London from Canada & back to PA, that's what's causing the majority of the issue.

- Matt

[Troy [ASAPweb]]

It's the jump from shawcable to cogentco.com that's the problem here - My isp is cogeco :)

You can see it at
7 29 ms 108 ms 68 ms rc1hu-pos6-0.ny.shawcable.net [66.163.76.90]
8 166 ms 184 ms 198 ms core01.ams03.atlas.cogentco.com [195.69.144.124]


From what I can see by tracing these is that I'm being routed east instead of south through Burlington Ontario (as I used to be)

[Matt [MainArea]]

Originally posted by osfdeath
It's the jump from shawcable to cogentco.com that's the problem here - My isp is cogeco :)

You can see it at
7 29 ms 108 ms 68 ms rc1hu-pos6-0.ny.shawcable.net [66.163.76.90]
8 166 ms 184 ms 198 ms core01.ams03.atlas.cogentco.com [195.69.144.124]


From what I can see by tracing these is that I'm being routed east instead of south through Burlington Ontario (as I used to be)
You're also being routed overseas. Chances are, if you contact Cogeco in Canada, they'll easily be able to fix the problem by switching priority routes or getting in contact with their providers about the problem.

- Matt

[Troy [ASAPweb]]

Thanks Matt - already did that
The local cable company ISP here are pretty much morons IMO
I left them for DSL some time ago then just switched back because they have a new 10mb/1mb line - worked great for about 25 seconds....why'd I switch again?

[princeshoko]

wow 10mb/1mb how much? And why only 25seconds LOL

Robert

[Troy [ASAPweb]]

About $80 Canadian/month
I was with them before and left because they have no clue as to how to run an ISP
I switched to DSL (3mb/768) and never once had any issues or problems in two years - should have stayed there lol
But of course I just had to have the HIGHER SPEEDS - and all the problems that've come with having this cable company as a provider...