Seems issues with them again :(, when are we getting multihomed again :(



Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>tracert perth.myacen.com

Tracing route to perth.myacen.com [209.51.142.186]
over a maximum of 30 hops:

1 32 ms 15 ms 16 ms 172.31.30.26
2 31 ms 16 ms 16 ms 172.31.25.154
3 31 ms 47 ms 31 ms core1-0-0-62.Perth.netspace.net.au [203.17.99.50
]
4 31 ms 47 ms 31 ms FastEthernet2-0-10.cor2.per.connect.com.au [210.
9.196.130]
5 31 ms 31 ms 47 ms fastethernet6-0-0.bdr1.per.connect.com.au [203.6
3.113.94]
6 94 ms 94 ms 109 ms atm9-1-0-4.bdr2.syd.connect.com.au [203.63.112.6
5]
7 94 ms 94 ms 94 ms g2-0-2.sybr3.global-gateway.net.nz [202.50.119.9
7]
8 250 ms 266 ms 250 ms p4-4.pabr2.global-gateway.net.nz [202.50.116.194
]
9 250 ms 250 ms 265 ms g0-0-0-0.pabr3.global-gateway.net.nz [202.50.245
.24]
10 266 ms 266 ms 265 ms sl-st20-pa-6-3.sprintlink.net [144.223.243.17]
11 250 ms 265 ms 250 ms sl-bb20-sj-8-3.sprintlink.net [144.232.20.43]
12 266 ms 265 ms 282 ms sl-gw8-sj-9-0.sprintlink.net [144.232.3.110]
13 532 ms 531 ms 531 ms sl-cogentcomm-7-0.sprintlink.net [144.228.110.12
2]
14 531 ms 516 ms 516 ms p6-0.core01.sfo01.atlas.cogentco.com [66.28.4.14
5]
15 578 ms 562 ms 578 ms p14-0.core01.ord01.atlas.cogentco.com [66.28.4.4
1]
16 594 ms 578 ms 563 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.6
2]
17 610 ms 609 ms 609 ms p6-0.core02.jfk02.atlas.cogentco.com [66.28.4.85
]
18 625 ms 594 ms 609 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.1
3]
19 594 ms 609 ms 625 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81
]
20 641 ms 625 ms 609 ms p14-0.core01.atl01.atlas.cogentco.com [66.28.4.1
25]
21 625 ms 609 ms 625 ms g50.ba01.b000173-0.atl01.atlas.cogentco.com [66.
28.5.246]
22 672 ms 656 ms 672 ms dv2.demarc.cogentco.com [66.28.28.254]
23 * * 703 ms dv2-atl-core-core-a.dv2.net [209.51.131.1]
24 656 ms 672 ms * perth.myacen.com [209.51.142.186]
25 719 ms * 734 ms perth.myacen.com [209.51.142.186]

Trace complete.

C:\>


:(, usually around 340ms.

No offence but complaining about your supplier like this doesn't inspire confidence in your prospective clientel from around these parts. :)

Hope is all works out.

We don't get many clients from Webhostingtalk. They all expect 50gb's bandwidth for $2/mth here.

seems alright from my end...

Well, it was getting better now it's back to slow/packetloss performance.

Yep, its VERY bad :(

Originally posted by hosticle
Yep, its VERY bad :(
All that cogent. :eek:

This is a very aussie thread, lets go pissup at the casino and let the yanks sort it out ;)

Originally posted by Aussie Bob

All that cogent. :eek:

Yes Jeff we are waiting for those new tier1 providers :rolleyes:

C:\>tracert perth.myacen.com

Tracing route to perth.myacen.com [209.51.142.186]
over a maximum of 30 hops:

1 22 ms 21 ms 23 ms 172.31.16.24
2 26 ms 26 ms 24 ms 172.31.56.24
3 24 ms 26 ms 25 ms qld5-atm.qld.bigpond.net.au [***.***.***.***]
4 24 ms 23 ms 26 ms 61.9.209.8
5 25 ms 26 ms 25 ms GigabitEthernet4-1.cha23.telstra.net [139.130.19
3.113]
6 26 ms 25 ms 26 ms GigabitEthernet4-0.woo-core1.Brisbane.telstra.ne
t [203.50.50.129]
7 36 ms 34 ms 36 ms Pos5-0.ken-core4.Sydney.telstra.net [203.50.6.22
1]
8 37 ms 35 ms 35 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22
]
9 36 ms 36 ms 35 ms GigabitEthernet0-0.syd-core01.Sydney.net.reach.c
om [203.50.13.242]
10 225 ms 224 ms 224 ms 202.84.143.41
11 207 ms 207 ms 207 ms i-13-0.paix-core01.PaloAlto.net.reach.com [202.8
4.251.49]
12 208 ms 207 ms 208 ms ge4-0.mpr2.pao1.us.mfnx.net [198.32.176.11]
13 230 ms 229 ms 232 ms 64.124.11.181.cogentco.com [64.124.11.181]
14 212 ms 214 ms 212 ms p6-0.core01.sfo01.atlas.cogentco.com [66.28.4.14
5]
15 261 ms 261 ms 273 ms p14-0.core01.ord01.atlas.cogentco.com [66.28.4.4
1]
16 276 ms 274 ms 274 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.6
2]
17 306 ms 300 ms 301 ms p6-0.core02.jfk02.atlas.cogentco.com [66.28.4.85
]
18 302 ms 300 ms 301 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.1
3]
19 314 ms 317 ms 314 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81
]
20 329 ms 330 ms 327 ms p14-0.core01.atl01.atlas.cogentco.com [66.28.4.1
25]
21 331 ms 329 ms 332 ms g50.ba01.b000173-0.atl01.atlas.cogentco.com [66.
28.5.246]
22 314 ms 316 ms 312 ms dv2.demarc.cogentco.com [66.28.28.254]
23 329 ms 330 ms 332 ms dv2-atl-core-core-a.dv2.net [209.51.131.1]
24 314 ms 315 ms 313 ms perth.myacen.com [209.51.142.186]

Man,

and i finally got plesk 5.0 - now I just sit here for 10 mins and watch it time out *CRIES*

On the other hand you can watch all the pretty lights here:

http://status.myacen.com/

:D

The ****ty thing is, we have nowhere to go!

Everyone is deh suk lately! :(

No packetloss now, just very high pings 500ms :eek:

We have been tracing from a couple of locations, and cant see a problem..

This is a ping & traceroute from the UK:

C:\>ping perth.myacen.com

Pinging perth.myacen.com [209.51.142.186] with 32 bytes of data:

Reply from 209.51.142.186: bytes=32 time=120ms TTL=233
Reply from 209.51.142.186: bytes=32 time=111ms TTL=233
Reply from 209.51.142.186: bytes=32 time=110ms TTL=233
Reply from 209.51.142.186: bytes=32 time=110ms TTL=233

C:\>tracert perth.myacen.com

Tracing route to perth.myacen.com [209.51.142.186]
over a maximum of 30 hops:

1 <10 ms <10 ms 10 ms prdg02-e2.mprn.bt.com [10.230.167.1]
2 10 ms <10 ms <10 ms gprtpr01-f4-0.mprn.bt.com [10.230.131.55]
3 10 ms <10 ms 10 ms gcvnls70-a6-0-22.mprn.bt.com [10.240.17.21]
4 10 ms 10 ms 10 ms 10.240.1.65
5 10 ms 10 ms 10 ms gcrgehhad01-vl70.mprn.bt.com [10.240.2.11]
6 10 ms * 10 ms internet-jd.nor.bt.com [193.113.139.170]
7 20 ms 10 ms 10 ms 193.113.57.17
8 10 ms 10 ms 20 ms highspeed1-Serial2-0-1.manchester.bt.net [212.140.207.141]
9 90 ms 20 ms 10 ms core2-gig10-1.manchester.ukcore.bt.net [194.72.5.11]
10 20 ms 20 ms 20 ms core2-pos13-1.bletchley.ukcore.bt.net [62.6.196.126]
11 20 ms 20 ms 20 ms core2-pos13-3.ilford.ukcore.bt.net [62.6.196.222]
12 20 ms 21 ms 20 ms core2-pos8-0.telehouse.ukcore.bt.net [194.74.65.125]
13 20 ms 20 ms 30 ms pos7-1.mpr2.lhr1.uk.mfnx.net [208.185.156.217]
14 20 ms 20 ms 20 ms pos0-0.mpr1.lhr1.uk.mfnx.net [208.185.156.13]
15 90 ms 80 ms 90 ms so-4-2-0.cr1.lga1.us.mfnx.net [208.184.231.21]
16 90 ms 90 ms 90 ms so-0-0-0.cr1.lga2.us.mfnx.net [208.185.0.246]
17 90 ms 90 ms 90 ms so-2-0-0.pr1.lga4.us.mfnx.net [64.124.232.6]
18 190 ms 181 ms 180 ms 64.124.51.186.cogentco.com [64.124.51.186]
19 181 ms 180 ms 170 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81]
20 200 ms 190 ms 201 ms p14-0.core01.atl01.atlas.cogentco.com [66.28.4.125]
21 190 ms 201 ms 190 ms g50.ba01.b000173-0.atl01.atlas.cogentco.com [66.28.5.246]
22 120 ms 141 ms 390 ms dv2.demarc.cogentco.com [66.28.28.254]
23 111 ms 110 ms 120 ms 209.51.131.1
24 121 ms 110 ms 120 ms perth.myacen.com [209.51.142.186]

Trace complete.

Looks like there a problem with router on hop 13 Myacerns post, we'll see what we can do, but that is a Sprint to Cogent router..

If anyone wants to submit there traces please send to trace@eservers.biz

Imran

Originally posted by hosticle
This is a very aussie thread, lets go pissup at the casino and let the yanks sort it out ;)
Your shout?? :beer:

Originally posted by Myacen
Yes Jeff we are waiting for those new tier1 providers :rolleyes:
Meanwhile over at NAC. *whistles* :D :stickout

Originally posted by Aussie Bob

Meanwhile over at NAC. *whistles* :D :stickout

Bob, check your PM in about 5

yeah why not!

Might as well throw my money down the toilet now before it gets lost when we find out dv2 is bankrupt, all our servers are lost, eservers bank stole their money and we aren't entitled to refunds :D

Alcohol a waste of money? No, it's the only thing that keeps us going over here :D ;)

The pub down the road is probably kept in business because of US :D

Originally posted by cabalstudios
C:\>ping perth.myacen.com

Pinging perth.myacen.com [209.51.142.186] with 32 bytes of data:

Reply from 209.51.142.186: bytes=32 time=120ms TTL=233
Reply from 209.51.142.186: bytes=32 time=111ms TTL=233
Reply from 209.51.142.186: bytes=32 time=110ms TTL=233
Reply from 209.51.142.186: bytes=32 time=110ms TTL=233
C:\>ping perth.myacen.com

Pinging perth.myacen.com [209.51.142.186] with 32 bytes of data:

Reply from 209.51.142.186: bytes=32 time=317ms TTL=230
Reply from 209.51.142.186: bytes=32 time=314ms TTL=230
Reply from 209.51.142.186: bytes=32 time=313ms TTL=230
Reply from 209.51.142.186: bytes=32 time=316ms TTL=230

Ping statistics for 209.51.142.186:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 313ms, Maximum = 317ms, Average = 315ms

Woah, its blistering fast now!

Maybe they switch on another feed? *smirk*

Originally posted by hosticle
Woah, its blistering fast now!

Maybe they switch on another feed? *smirk*

Yes Im getting good speeds again

Originally posted by hosticle
yeah why not!

Might as well throw my money down the toilet now before it gets lost when we find out dv2 is bankrupt, all our servers are lost, eservers bank stole their money and we aren't entitled to refunds :D
We're a cheery chap today, aren't we?? ;) :D :beer:

I was so excited about gettings plesk 5.0 then I can't use it

Like a kid getting his toys taken from him :)

Traceroutes please...

1 kallisti.chaosrunner.org (199.34.34.17) 3 ms 2 ms 2 ms
2 206.205.235.49 (206.205.235.49) 4 ms 4 ms 3 ms
3 dca1-core13-pos4-2.atlas.algx.net (165.117.63.1) 4 ms 5 ms 3 ms
4 dca10-core1-so-7-2-0.atlas.algx.net (165.117.56.22) 4 ms 9 ms 4 ms
5 dca10-core2-so-0-1-0-0.atlas.algx.net (165.117.192.46) 4 ms 4 ms 4 ms
6 sfo10-core2-so-7-0-0-0.atlas.algx.net (165.117.200.78) 92 ms 92 ms 92 ms
7 sfo10-core1-so-0-1-0-0.atlas.algx.net (165.117.192.41) 99 ms 92 ms 92 ms
8 sfo9-core2-pos10-0.atlas.algx.net (165.117.69.98) 98 ms 99 ms 92 ms
9 sjc3-core4-pos2-0.atlas.algx.net (165.117.192.113) 94 ms 96 ms 94 ms
10 206.181.191.210 (206.181.191.210) 94 ms 96 ms 94 ms
11 205.215.12.1 (205.215.12.1) 94 ms 103 ms 94 ms
12 g3-0.pr1.atl01.netrail.net (66.28.28.202) 194 ms 194 ms 194 ms
13 205.215.2.6 (205.215.2.6) 129 ms 130 ms 129 ms
14 velocity.eservers.biz (209.51.159.226) 129 ms 132 ms 130 ms


Tracing route to velocity.eservers.biz [209.51.159.226]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms r.orl-lngwd1.datapacket.net [208.195.14.225]
2 20 ms 10 ms 30 ms loopback0.gw8.orl1.alter.net [137.39.8.117]
3 30 ms 10 ms 10 ms 165.at-1-0-0.cl2.orl1.alter.net [152.63.86.182]
4 10 ms 30 ms 30 ms 0.so-3-0-0.tl2.atl1.alter.net [152.63.101.53]
5 50 ms 30 ms 100 ms 0.so-5-3-0.tl2.chi2.alter.net [152.63.13.42]
6 90 ms 30 ms 60 ms 0.so-2-0-0.xl2.chi2.alter.net [152.63.67.110]
7 40 ms 30 ms 60 ms 0.so-7-1-0.br6.chi2.alter.net [152.63.71.98]
8 40 ms 50 ms 51 ms 204.255.174.158
9 70 ms 70 ms 70 ms g3-0.pr1.atl01.netrail.net [66.28.28.202]
10 80 ms 80 ms 80 ms 205.215.2.6
11 60 ms 60 ms 60 ms velocity.eservers.biz [209.51.159.226]

Trace complete.


anyone else?

and you voted no against WHT having an IRC network!

look at this thread for example - only seconds between posts...may as well be IRC ;)

Originally posted by Myacen


Yes Im getting good speeds again

Can you do me a traceroute please.. and post

Imran

cobal,

she's all good now!

This is the first time I've had a problem with them (dv2).

Quite a novelty really. :D

Yeah, they are normally very very good - just a bit of network lag when we should be in bed - no hard feelings really :)

Originally posted by cabalstudios
Traceroutes please...

1 kallisti.chaosrunner.org (199.34.34.17) 3 ms 2 ms 2 ms
2 206.205.235.49 (206.205.235.49) 4 ms 4 ms 3 ms
3 dca1-core13-pos4-2.atlas.algx.net (165.117.63.1) 4 ms 5 ms 3 ms
4 dca10-core1-so-7-2-0.atlas.algx.net (165.117.56.22) 4 ms 9 ms 4 ms
5 dca10-core2-so-0-1-0-0.atlas.algx.net (165.117.192.46) 4 ms 4 ms 4 ms
6 sfo10-core2-so-7-0-0-0.atlas.algx.net (165.117.200.78) 92 ms 92 ms 92 ms
7 sfo10-core1-so-0-1-0-0.atlas.algx.net (165.117.192.41) 99 ms 92 ms 92 ms
8 sfo9-core2-pos10-0.atlas.algx.net (165.117.69.98) 98 ms 99 ms 92 ms
9 sjc3-core4-pos2-0.atlas.algx.net (165.117.192.113) 94 ms 96 ms 94 ms
10 206.181.191.210 (206.181.191.210) 94 ms 96 ms 94 ms
11 205.215.12.1 (205.215.12.1) 94 ms 103 ms 94 ms
12 g3-0.pr1.atl01.netrail.net (66.28.28.202) 194 ms 194 ms 194 ms
13 205.215.2.6 (205.215.2.6) 129 ms 130 ms 129 ms
14 velocity.eservers.biz (209.51.159.226) 129 ms 132 ms 130 ms


Tracing route to velocity.eservers.biz [209.51.159.226]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms r.orl-lngwd1.datapacket.net [208.195.14.225]
2 20 ms 10 ms 30 ms loopback0.gw8.orl1.alter.net [137.39.8.117]
3 30 ms 10 ms 10 ms 165.at-1-0-0.cl2.orl1.alter.net [152.63.86.182]
4 10 ms 30 ms 30 ms 0.so-3-0-0.tl2.atl1.alter.net [152.63.101.53]
5 50 ms 30 ms 100 ms 0.so-5-3-0.tl2.chi2.alter.net [152.63.13.42]
6 90 ms 30 ms 60 ms 0.so-2-0-0.xl2.chi2.alter.net [152.63.67.110]
7 40 ms 30 ms 60 ms 0.so-7-1-0.br6.chi2.alter.net [152.63.71.98]
8 40 ms 50 ms 51 ms 204.255.174.158
9 70 ms 70 ms 70 ms g3-0.pr1.atl01.netrail.net [66.28.28.202]
10 80 ms 80 ms 80 ms 205.215.2.6
11 60 ms 60 ms 60 ms velocity.eservers.biz [209.51.159.226]

Trace complete.


anyone else?
C:\>tracert velocity.eservers.biz

Tracing route to velocity.eservers.biz [209.51.159.226]
over a maximum of 30 hops:

1 23 ms 22 ms 26 ms 172.31.16.24
2 26 ms 25 ms 25 ms 172.31.56.24
3 25 ms 25 ms 26 ms qld5-atm.qld.bigpond.net.au [??]
4 22 ms 23 ms 26 ms 61.9.209.8
5 24 ms 25 ms 25 ms GigabitEthernet4-1.cha23.telstra.net [139.130.193.113]
6 25 ms 26 ms 24 ms GigabitEthernet4-0.woo-core1.Brisbane.telstra.net [203.50.50.129]
7 36 ms 36 ms 35 ms Pos5-0.ken-core4.Sydney.telstra.net [203.50.6.221]
8 35 ms 39 ms 34 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22]
9 37 ms 35 ms 35 ms GigabitEthernet0-0.syd-core01.Sydney.net.reach.com [203.50.13.242
10 224 ms 223 ms 225 ms 202.84.143.5
11 211 ms 208 ms 211 ms i-13-0.paix-core01.PaloAlto.net.reach.com [202.84.251.49]
12 208 ms 208 ms 209 ms ge4-0.mpr2.pao1.us.mfnx.net [198.32.176.11]
13 227 ms 232 ms 231 ms 64.124.11.181.cogentco.com [64.124.11.181]
14 213 ms 215 ms 212 ms p6-0.core01.sfo01.atlas.cogentco.com [66.28.4.145]
15 258 ms 260 ms 258 ms p14-0.core01.ord01.atlas.cogentco.com [66.28.4.41]
16 275 ms 274 ms 276 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62]
17 327 ms 321 ms 307 ms p6-0.core02.jfk02.atlas.cogentco.com [66.28.4.85]
18 301 ms 301 ms 299 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.13]
19 316 ms 317 ms 316 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81]
20 328 ms 328 ms * p14-0.core01.atl01.atlas.cogentco.com [66.28.4.125]
21 312 ms 313 ms 311 ms g49.ba01.b000173-0.atl01.atlas.cogentco.com [66.28.5.242]
22 313 ms 313 ms 315 ms dv2.demarc.cogentco.com [66.28.28.254]
23 331 ms 331 ms 329 ms dv2-atl-core-core-a.dv2.net [209.51.131.1]
24 312 ms 309 ms 311 ms velocity.eservers.biz [209.51.159.226]

Trace complete.

C:\>ping velocity.eservers.biz

Pinging velocity.eservers.biz [209.51.159.226] with 32 bytes of data:

Reply from 209.51.159.226: bytes=32 time=312ms TTL=230
Reply from 209.51.159.226: bytes=32 time=309ms TTL=230
Reply from 209.51.159.226: bytes=32 time=310ms TTL=230
Reply from 209.51.159.226: bytes=32 time=318ms TTL=230

Ping statistics for 209.51.159.226:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 309ms, Maximum = 318ms, Average = 312ms

:D

Originally posted by hosticle
cobal,

she's all good now!

hmm, can I ask why you call us cobal?
cabal would be nice, :stickout

do you have a liking for the programing language cobol, and get us mixed up or something, have a pint on me :beer:

*rubs his eyes* It's all the excitement of plesk 5.0 - im more worried about spontaniously wetting myself than changing vowels :P

I do call you cobol all the time dont i? :P

*tries typeing cabal* hmm, much easier to type. I think I might call you cabal for now on :)

However! cobal sounds better imo :D

Originally posted by hosticle
im more worried about spontaniously wetting myself....
That would be too much :beer: now, wouldn't it?? :D :stickout

jc@gw:~$ traceroute perth.myacen.com
traceroute to perth.myacen.com (209.51.142.186), 64 hops max, 40 byte packets
1 62.225.255.225 (62.225.255.225) 30.706 ms 29.201 ms 49.817 ms
2 62.225.255.226 (62.225.255.226) 33.566 ms 28.697 ms 50.368 ms
3 NYC-gw14.USA.net.DTAG.DE (62.156.131.161) 120.473 ms 115.760 ms 126.76 ms
4 NYC-gw19.USA.net.DTAG.DE (62.156.131.134) 160.882 ms 127.488 ms 128.276 ms
5 205.215.1.9 (205.215.1.9) 159.260 ms 121.837 ms 141.776 ms
6 g3-0.pr1.atl01.netrail.net (66.28.28.202) 156.547 ms 177.921 ms 175.843 ms
7 205.215.2.6 (205.215.2.6) 140.450 ms 151.747 ms 160.120 ms
8 perth.myacen.com (209.51.142.186) 158.675 ms 144.829 ms 161.241 ms

never saw any problem with the netrail route to dv2.

looks like dv2 still sucks! cogentco dns errors abound!

Originally posted by Myacen
We don't get many clients from Webhostingtalk. They all expect 50gb's bandwidth for $2/mth here.

How about $3?! :D

Tracing route to perth.myacen.com [209.51.142.186]
over a maximum of 30 hops:

1 140 ms 140 ms 151 ms 192.168.254.200
2 150 ms 160 ms 161 ms 192.168.254.200
3 150 ms 150 ms 151 ms 172.16.95.28
4 150 ms 150 ms 151 ms 172.16.95.33
5 150 ms 140 ms 141 ms 213.120.207.201
6 140 ms 150 ms 141 ms core2-pos12-1.ealing.ukcore.bt.net [194.72.9.201]
7 140 ms 151 ms 150 ms core2-pos7-0.telehouse.ukcore.bt.net [194.74.65.121]
8 151 ms 130 ms 140 ms pos7-1.mpr2.lhr1.uk.mfnx.net [208.185.156.217]
9 160 ms 140 ms 160 ms pos0-0.mpr1.lhr1.uk.mfnx.net [208.185.156.13]
10 230 ms 220 ms 201 ms so-4-2-0.cr1.lga1.us.mfnx.net [208.184.231.21]
11 211 ms 200 ms 210 ms so-0-0-0.cr1.lga2.us.mfnx.net [208.185.0.246]
12 270 ms 210 ms 231 ms core1-lga2-oc48.lga4.above.net [64.124.232.6]
13 300 ms 391 ms 391 ms 64.124.51.186.cogentco.com [64.124.51.186]
14 400 ms 381 ms 370 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81]
15 330 ms 291 ms 380 ms p14-0.core01.atl01.atlas.cogentco.com [66.28.4.125]
16 340 ms 301 ms 290 ms g49.ba01.b000173-0.atl01.atlas.cogentco.com [66.28.5.242]
17 310 ms 381 ms 240 ms dv2.demarc.cogentco.com [66.28.28.254]
18 240 ms 240 ms 241 ms dv2-atl-core-core-a.dv2.net [209.51.131.1]
19 261 ms 240 ms 230 ms perth.myacen.com [209.51.142.186]

Trace complete.


All from my shoddy 56K :(

James

James, that looks rather normal to me.. perhaps a little slow in the bt area, however its been so long since I used dial up, that could be normal.

LOL

If you want good trace's get a server in your own country,,,, :D

No worries then lol :D

Yes ... do one :D

Haze - it wasn't a problem - soz, should have stated that :D

It's fine for 56k from the UK.
ISDN from the UK is about 120ms - 150ms.

James

Originally posted by ben_h
looks like dv2 still sucks! cogentco dns errors abound! ben, do you have any documentation of the "dns errors"? not sure what you meant. sorry if i am being obtuse :)

looks like dv2 still sucks! cogentco dns errors abound!

Thank god....... you must be in a different DV2 to us :D we've had no such problems with our DV2......... :PD

NZ rocks :D

Originally posted by ben_h
looks like dv2 still sucks! cogentco dns errors abound!

ben, your redundant posting using this flawed information is getting old fast, i was wondering why and what's your point other than to try and bash other hosts??

using your initial "investigation" on the COGENT NEWS post as an example, you can see MANY other hosted sites / providers have the exact same DNS errors (and some others) that you pointed as being a cogent problem.

Originally posted by skylab


ben, your redundant posting using this flawed information is getting old fast, i was wondering why and what's your point other than to try and bash other hosts??

using your initial "investigation" on the COGENT NEWS post as an example, you can see MANY other hosted sites / providers have the exact same DNS errors (and some others) that you pointed as being a cogent problem.

Agree 100%! Stop bashing! If you don't like Cogent then choose one of the other 30+ providers available and stop whining like a little girl... jesus!

I remain behind the awful AOL Time Warner - Cogent peer. This situation has persisted for at least 3 weeks though the latency has lowered just recently from the 300's down to the 90's. Is DV2 still multihomed or is it Cogent only? I hope it's not the latter as I was under the impression that I was paying for multihoming.

What used to be a 20ms - 30ms ping is now lucky to get below 100ms.

1 9 ms 9 ms 11 ms 10.47.128.1
2 10 ms 8 ms 9 ms pos0-2-nycmnys-rtr1.nyc.rr.com [24.29.100.45]
3 9 ms 10 ms 11 ms pos2-0-nycmnyr-rtr1.nyc.rr.com [24.29.100.90]
4 10 ms 10 ms 9 ms pos3-0-nycmnya-rtr1.nyc.rr.com [24.29.97.29]
5 14 ms 10 ms 12 ms pop1-nye-P0-2.atdn.net [66.185.137.193]
6 10 ms 11 ms 10 ms bb2-nye-P5-0.atdn.net [66.185.141.18]
7 15 ms 15 ms 13 ms bb2-vie-P8-0.atdn.net [66.185.153.118]
8 14 ms 15 ms 14 ms bb2-ash-P15-2.atdn.net [66.185.152.41]
9 13 ms 15 ms 15 ms pop2-ash-P1-0.atdn.net [66.185.139.214]
10 90 ms 92 ms 92 ms CogentTestPeering.atdn.net [66.185.141.242]
11 96 ms 101 ms 96 ms g3-0.pr1.atl01.netrail.net [66.28.28.202]
12 95 ms 96 ms 95 ms 205.215.2.6
13 96 ms 96 ms 96 ms velocity.eservers.biz [209.51.159.226]

Exactly, I think it's cogent/netrail only, but netrail is owned by cogent bit misleading :angry:

Originally posted by MrE

What used to be a 20ms - 30ms ping is now lucky to get below 100ms.

What exactly is wrong with having 100ms pings?
DV2 is very cheap i.e. not a 500$/month place so pings can't be 20-30ms cause if it was all 500$ places would be out of business.

I really cannot understand all this fuss. DV2 is multihomed but that means that if Cogent fails completely the backup kicks in. AFAIK the backup is 10times expensive then the main line so running on backup when pings go high would wreck the place financially.

At HE.NET I have 20ms pings and 20+carriers but hey!: 300$/mbit and not 35$ (Cogent) ;)

http://www.webhostingtalk.com/showthread.php?s=&threadid=69437

Originally posted by netdude
http://www.webhostingtalk.com/showthread.php?s=&threadid=69437

Yes we all know that your upcoming 1 Million Dollar business utilizing your "cogent-trashing" Exodus bandwith will revolutionize the internet and will put all of us out of business.

You have been busy enough promoting it all over WHT except the posts bashing competitors and Cogent related stuff.

I suggest you take it easy. Not very cool to get a stress-related seizure at age 15.

nocsol, attack me personally and i'll make it personal... that thread, was strictly about multihoming until a service provider decided to bring his company into it.

oh, and i ain't 15...

A thread called "DV2 Network Problems?" is surely not a thread about multihoming as DV2 IS a provider so cut the BS.

Don't worry about getting personal, I am sure by now quite a few people already hav epersonal feelings for you.

And as to you beeing 15 only referrs to your style and intelligence.

nocsol, the post preceeding yours was directly discussing whether or not dv2's network is multihomed (and he/she being a client of dv2, was concerned)... even you mentioned how he.net was multihomed and that someone can't expect that kind quality (multihoming) from an inexpensive provider.

as for my style, i keep things casual unless circumstances demand otherwise. if you want me to start posting threads where you've acted like a pure moron (in regards to irrelavent posts/etc), ask me to do so and i will.

Originally posted by netdude
nocsol, the post preceeding yours was directly discussing whether or not dv2's network is multihomed (and he/she being a client of dv2, was concerned)... even you mentioned how he.net was multihomed and that someone can't expect that kind quality (multihoming) from an inexpensive provider.

as for my style, i keep things casual unless circumstances demand otherwise. if you want me to start posting threads where you've acted like a pure moron (in regards to irrelavent posts/etc), ask me to do so and i will.

I don't take threats. My posts are no excuse for your wrongdoing so post whatever you want (net)dude