dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
574

Spare
join:2004-04-14
min2p6

Spare

Member

Pings gone south in the core hours

Been so long since I had an issue with Start (doubt this is there issue) forgot where the new topic button was

Any way here's a trace route don't think you could do any thing with it as its not your route. You can see where things go 'arry evening in the core hours 200ms is low 400ms the norm but manages to right itself at about 12:30am to about 75ms

1
daeron
join:2012-05-11
Ottawa

daeron

Member

I don't see a trace route here, just a 1 with a tongue out :P

rocca
Start.ca
Premium Member
join:2008-11-16
London, ON

rocca to Spare

Premium Member

to Spare
said by Spare:

here's a trace route don't think you could do any thing with it

:)
mikee
join:2012-12-21
Gloucester, ON

mikee to Spare

Member

to Spare
in ottawa - it was my first night on start 25/10 vdsl, and I had rockin pings to chicago that i've never played with before... 21 ping to chicago is dreamy for me living in ottawa.

if you post an ip i'll give you my trace route for a reference to compare.

Spare
join:2004-04-14
min2p6

Spare

Member

Doh!

1 1 ms 1 ms 1 ms
2 8 ms 8 ms 9 ms
3 35 ms 26 ms 26 ms 64.140.112.118
4 24 ms 25 ms 29 ms 64.140.112.117
5 31 ms 37 ms 35 ms core1-london1-ge1-1801.net.start.ca [64.140.112.
85]
6 34 ms 36 ms 35 ms 204.101.4.193
7 39 ms 38 ms 39 ms tcore4-london14_tengige10-0-1.net.bell.ca [64.23
0.112.52]
8 48 ms 46 ms 43 ms tcore4-london14_pos0-15-0-0.net.bell.ca [64.230.
49.70]
9 38 ms 38 ms 37 ms newcore2-chicago23_so2-0-0.net.bell.ca [64.230.1
47.174]
10 41 ms 92 ms 74 ms bx5-chicagodt_xe6-0-0.net.bell.ca [64.230.186.86
]
11 169 ms 174 ms 161 ms Verio-Peering.net.bell.ca [64.230.186.218]
12 85 ms 81 ms 77 ms ae-7.r20.chcgil09.us.bb.gin.ntt.net [129.250.4.1
45]
13 191 ms * 186 ms ae-4.r23.nycmny01.us.bb.gin.ntt.net [129.250.2.4
1]
14 177 ms * 195 ms ae-9.r20.asbnva02.us.bb.gin.ntt.net [129.250.2.1
49]
15 181 ms 183 ms 197 ms ae-1.r06.asbnva02.us.bb.gin.ntt.net [129.250.7.2
5]
16 1269 ms 1253 ms 1162 ms xe-0-0-0-20.r06.asbnva02.us.ce.gin.ntt.net [129.
250.206.138]
17 71 ms 60 ms 70 ms as36352.ge-1-1-5.cr2.iad1.us.scnet.net [75.102.4
3.122]
18 1171 ms 1162 ms 1161 ms ash.xfactorservers.com [75.102.41.52]

rocca
Start.ca
Premium Member
join:2008-11-16
London, ON

rocca

Premium Member

I'm going to guess they are getting DDoS'd (or are heavily under provisioned).

traceroute to ash.xfactorservers.com (205.234.159.130), 30 hops max, 60 byte packets
1 core1-london1-ge1-120.net.start.ca (64.140.120.1) 0.386 ms 0.487 ms 0.585 ms
2 204.101.4.185 (204.101.4.185) 0.307 ms 0.314 ms 0.314 ms
3 tcore3-london14_tengige4-0-1.net.bell.ca (64.230.112.46) 16.971 ms 16.716 ms 19.012 ms
4 tcore3-toronto12_pos0-15-0-0.net.bell.ca (64.230.73.224) 16.274 ms 16.319 ms 16.343 ms
5 newcore1-chicago23_so2-0-0.net.bell.ca (64.230.147.166) 15.590 ms 13.291 ms 13.382 ms
6 bx5-chicagodt_xe6-1-2_0 (64.230.186.253) 13.542 ms bx5-chicagodt_xe5-0-2.net.bell.ca (64.230.186.78) 23.293 ms 23.291 ms
7 Verio-Peering.net.bell.ca (64.230.186.218) 129.328 ms 130.812 ms 130.996 ms
8 ae-0.gtt-offnet.chcgil09.us.bb.gin.ntt.net (129.250.193.2) 13.793 ms 14.627 ms 14.580 ms
9 ae4.cr1.ord6.us.scnet.net (204.93.204.85) 14.320 ms 14.278 ms 14.176 ms
10 71.ae1.ar1.ord6.us.scnet.net (204.93.204.153) 91.488 ms 91.456 ms 91.573 ms
11 as36352.xe-2-1-3.ar1.ord6.us.scnet.net (50.31.151.170) 91.908 ms 91.280 ms 91.268 ms
12 10ge-2.fw146.chi1.colocrossing.com (75.102.10.254) 4935.163 ms !H 4935.284 ms !H *
rocca

rocca

Premium Member

Another path is just as bad at the same far end destination:

traceroute to ash.xfactorservers.com (205.234.159.130), 30 hops max, 60 byte packets
1 core1-toronto1.net.start.ca (64.140.114.1) 0.431 ms 0.510 ms 0.574 ms
2 xe-0-0-3.cr1.tor2.ca.nlayer.net (69.31.143.129) 0.241 ms 0.246 ms 0.290 ms
3 ae0-30g.cr1.tor1.ca.nlayer.net (69.31.143.24) 3.749 ms 3.754 ms 3.755 ms
4 ae2-50.tor10.ip4.gtt.net (199.229.230.89) 0.274 ms 0.280 ms 0.280 ms
5 xe-10-3-0.chi12.ip4.gtt.net (141.136.106.13) 9.840 ms 9.876 ms 9.877 ms
6 as23353.chi12.ip4.gtt.net (199.229.229.214) 12.673 ms 12.672 ms 12.666 ms
7 ae11.cr1.ord6.us.scnet.net (204.93.204.73) 13.486 ms 13.512 ms 13.539 ms
8 71.ae1.ar2.ord6.us.scnet.net (204.93.204.157) 10.978 ms 10.929 ms 10.941 ms
9 as36352.xe-2-1-3.ar2.ord6.us.scnet.net (50.31.154.182) 88.442 ms 88.859 ms 88.877 ms
10 10ge-1.fw146.chi1.colocrossing.com (205.234.152.254) 4233.430 ms !H * *
rocca

rocca

Premium Member

Fine until it gets to colocrossing.com, toast after that.

damir
join:2013-12-12
CANADA

damir

Member

Thats how colocrossing is.

I used to have servers with them, and they had tons of network issues, that is why i left.

Good luck OP.

Spare
join:2004-04-14
min2p6

Spare

Member

Well ain't that a soab. Since you cant fix it ill have to go to another isp

Ah but seriously thanks for taking a look