My tracerts are fine however most of our users are having problems.

My tracert

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

1 15 ms 16 ms 15 ms 172.31.30.26
2 15 ms 16 ms 16 ms 172.31.25.154
3 47 ms 47 ms 31 ms core1-0-0-62.Perth.netspace.net.au [203.17.99.50
]
4 32 ms 31 ms 31 ms FastEthernet2-0-10.cor2.per.connect.com.au [210.
9.196.130]
5 31 ms 31 ms 31 ms fastethernet6-0-0.bdr1.per.connect.com.au [203.6
3.113.94]
6 94 ms 94 ms 93 ms atm9-1-0-4.bdr2.syd.connect.com.au [203.63.112.6
5]
7 78 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 266 ms 250 ms g0-0-0-0.pabr3.global-gateway.net.nz [202.50.245
.24]
10 250 ms 250 ms 297 ms sl-st20-pa-6-3.sprintlink.net [144.223.243.17]
11 250 ms 282 ms 265 ms sl-bb20-sj-8-3.sprintlink.net [144.232.20.43]
12 250 ms 250 ms 250 ms sl-gw8-sj-9-0.sprintlink.net [144.232.3.110]
13 250 ms 265 ms 250 ms sl-cogentcomm-7-0.sprintlink.net [144.228.110.12
2]
14 250 ms 250 ms 250 ms p6-0.core01.sfo01.atlas.cogentco.com [66.28.4.14
5]
15 250 ms 250 ms 250 ms p4-0.core01.sjc01.atlas.cogentco.com [66.28.4.94
]
16 265 ms 266 ms 266 ms p13-0.core01.lax01.atlas.cogentco.com [66.28.4.7
3]
17 266 ms 265 ms 266 ms p5-0.core01.san01.atlas.cogentco.com [66.28.4.78
]
18 313 ms 312 ms 297 ms p6-0.core01.iah01.atlas.cogentco.com [66.28.4.5]

19 312 ms 313 ms 328 ms p15-0.core01.tpa01.atlas.cogentco.com [66.28.4.4
6]
20 329 ms 312 ms 328 ms p14-0.core01.jax01.atlas.cogentco.com [66.28.4.1
42]
21 406 ms 453 ms 531 ms p5-0.core01.atl01.atlas.cogentco.com [66.28.4.13
8]
22 328 ms 328 ms 328 ms g50.ba01.b000173-0.atl01.atlas.cogentco.com [66.
28.5.246]
23 328 ms 328 ms 328 ms dv2.demarc.cogentco.com [66.28.28.254]
24 313 ms 343 ms 329 ms dv2-atl-core-core-a.dv2.net [209.51.131.1]
25 328 ms 329 ms 328 ms 209.51.142.186

Trace complete.


Users tracert

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

1 8 ms 10 ms 8 ms 10.28.0.1
2 13 ms 8 ms 8 ms bla4-pos6-1.gw.optusnet.com.au [198.142.192.101]

3 9 ms 9 ms 8 ms ndmc1-pos3-4.gw.optusnet.com.au [198.142.192.89]

4 10 ms 10 ms 9 ms ndmc2-ge1-2.gw.optusnet.com.au [211.28.96.34]
5 9 ms 11 ms 11 ms pos2-3.ig5.optus.net.au [202.139.0.13]
6 168 ms 160 ms 159 ms 203.202.143.210
7 160 ms 159 ms 160 ms iar4-so-2-3-0-0.SanFrancisco.cw.net [208.173.173
.217]
8 161 ms 161 ms 160 ms acr2-loopback.SanFrancisco.cw.net [206.24.210.62
]
9 161 ms 162 ms 162 ms agr3-loopback.SantaClara.cw.net [208.172.146.103
]
10 161 ms 162 ms 191 ms dcr2-so-1-2-0.SantaClara.cw.net [208.172.156.153
]
11 161 ms 162 ms 171 ms agr1-so-6-0-0.SantaClara.cw.net [208.172.156.166
]
12 162 ms 165 ms 164 ms bpr2-loopback.PaloAltoPaix.cw.net [208.172.146.1
9]
13 165 ms 166 ms 165 ms 205.215.2.85
14 163 ms 175 ms 165 ms 205.215.12.1
15 242 ms 248 ms 240 ms g3-0.pr1.atl01.netrail.net [66.28.28.202]
16 1043 ms 1061 ms 1059 ms 205.215.2.6
17 1115 ms 1106 ms 1087 ms 209.51.142.186

Trace complete.


Another users tracert

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

1 0 ms 0 ms 0 ms 10.21.1.1
2 0 ms 0 ms 1 ms F0-1-0.G-RTR1.PORT.verizon-gni.net [64.223.196.66]
3 2 ms 3 ms 2 ms s3-0-3.bstnma1-cr7.bbnplanet.net [4.24.92.9]
4 2 ms 2 ms 3 ms so-3-1-0.bstnma1-nbr1.bbnplanet.net [4.24.4.225]
5 10 ms 10 ms 10 ms so-0-0-0.chcgil2-br1.bbnplanet.net [4.24.9.53]
6 10 ms 15 ms 10 ms so-7-0-0.chcgil2-br2.bbnplanet.net [4.24.5.218]
7 10 ms 11 ms 10 ms p1-0.chcgil2-cr2.bbnplanet.net [4.24.9.34]
8 20 ms 20 ms 20 ms aads-atm-gtei.netrail.net [4.24.146.78]
9 20 ms 25 ms 20 ms g3-0.pr1.atl01.netrail.net [66.28.28.202]
10 2000 ms 2000 ms 2001 ms 205.215.2.6
11 2010 ms 2000 ms 2100 ms 209.51.142.186

Trace complete.

don't feel bad burst.net is up to there crappy ways too :bawling:

I wonder why they appear to be preferencing their traffic out their Netrail peering?

traceroute to www.dv2.com (209.51.157.228), 30 hops max, 38 byte packets
<snip>
6 gbr2-a90s10.attga.ip.att.net (12.123.20.134) 18.540 ms gbr1-a80s11.attga.ip .att.net (12.123.20.138) 15.539 ms gbr5-p52.attga.ip.att.net (12.123.20.154) 1 6.512 ms
7 12.122.12.33 (12.122.12.33) 25.566 ms 17.600 ms 17.602 ms
8 12.122.10.73 (12.122.10.73) 43.918 ms 31.675 ms 32.053 ms
9 12.122.10.93 (12.122.10.93) 60.531 ms 63.538 ms 60.970 ms
10 tbr2-cl3.sffca.ip.att.net (12.122.10.25) 67.037 ms 66.278 ms 76.096 ms
11 ggr1-p3100.sffca.ip.att.net (12.122.11.230) 63.973 ms 106.469 ms 64.140 m s
12 nr1-p350.paix.ip.att.net (12.123.221.2) 69.658 ms 74.826 ms 70.534 ms
13 205.215.1.169 (205.215.1.169) 71.874 ms 72.961 ms 70.470 ms
14 205.215.12.1 (205.215.12.1) 69.250 ms 73.479 ms 71.465 ms
15 g3-0.pr1.atl01.netrail.net (66.28.28.202) 149.090 ms 151.970 ms 149.278 m s
16 205.215.2.6 (205.215.2.6) 82.341 ms 84.893 ms 82.461 ms
17 209.51.157.228 (209.51.157.228) 83.846 ms 82.387 ms 82.564 ms

Originally posted by Webjunkie
I wonder why they appear to be preferencing their traffic out their Netrail peering?



Cogent owns netrail who has a pop near dv2 if im not mistaken.

Myacen, you're not alone. My server at DV2 is also slower than usual:

01:26:12 (634.62 KB/s) - `uumap.tar.Z' saved [8520221]

My connection was bad to my servers in DV2, i contacted support there and they were looking into it. They had an issue with national-net the other week.

I think after they took national-net off their bgp4 and readded it it cleared up.

take a look at this :P

13 285 ms 275 ms 285 ms ge9-0.mpr2.lhr1.uk.mfnx.net [195.66.226.76] <-- this is london
14 286 ms 301 ms 269 ms pos0-0.mpr1.lhr1.uk.mfnx.net [208.185.156.13]
15 300 ms 301 ms 302 ms so-7-0-0.cr1.dca2.us.mfnx.net [64.125.31.186]
16 279 ms 300 ms 275 ms so-7-0-0.cr1.dca2.us.mfnx.net [64.125.31.186]
17 321 ms 306 ms 296 ms so-4-1-0.cr2.atl2.us.mfnx.net [208.184.232.50]
18 314 ms 295 ms 290 ms pos1-0.per1.atl2.us.mfnx.net [208.185.0.226]
19 303 ms 292 ms 301 ms tr1.atl2-1-1.national-net.com [66.115.128.53] <-- San Jose (CA)
20 282 ms 286 ms 299 ms tr1.atl1-1-8.national-net.com [66.115.128.42]
21 278 ms 287 ms 301 ms 209.51.137.125
22 305 ms 309 ms 286 ms 209.51.142.186 <-- Finally Atlanta.
Althrough its not slow, they have a horrible peering.

I'm getting the same as you Jorge - It didn't use to be like this, but ever since I saw national-net in tracerts I've had a couple of problems, the last the other week when I posted.

mine does that off and on = but doesnt last too long

It seems to have happened both times between 5/6 to 9/10 UK time. It will be terrible for a time - 70% packet loss, then it will come back for some minutes then go again.

Im getting reports of 2500ms pings now, seems the lines are heavily oversold?

We, are aware of the issue.

Its a problem with Cogent, we have raised an issue with Cogent and they are investigating, they have dumped all the traffic onto PSI which is causing the problem.

Imran

the problems seems to be here

8 so-2-1-3.pr1.SanFrancisco1.CA.us.netrail.net (205.215.1.229) 592.350 ms 645.005 ms 629.990 ms
9 GigE2-1.tr1.SanFrancisco1.CA.us.netrail.net (205.215.12.1) 607.607 ms 615.814 ms 662.844 ms

Can everyone please send there traceroutes to noc@eservers.biz ...

The more we get the better, will help us rectify the issue a.s.a.p
Thanks for your support.

UPDATE : We have done major re-routing, this should make things better until issues from the other network are resolved.

Thanks for your continued support...

wow. atleast for me it's fantastic now....

3 NYC-gw14.USA.net.DTAG.DE (62.156.131.161) 116.650 ms 114.115 ms 115.695 ms
4 NYC-gw19.USA.net.DTAG.DE (62.156.131.134) 119.8 ms 125.32 ms 120.404 ms
5 p1-0.pr1.nyc4.netrail.net (205.215.1.9) 118.175 ms 117.219 ms 117.428 ms
6 g3-0.pr1.atl01.netrail.net (66.28.28.202) 136.338 ms 136.653 ms 138.72 ms
7 205.215.2.6 (205.215.2.6) 136.762 ms 136.845 ms 134.806 ms
8 velocity.eservers.biz (209.51.159.226) 137.233 ms 134.726 ms 134.782 ms

8 hops from Germany to the US, nice! :)
and ping times are very nice for my dsl connection too.

C:\WINDOWS>ping eservers.biz

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

Reply from 209.51.159.226: bytes=32 time=1043ms TTL=227
Reply from 209.51.159.226: bytes=32 time=1044ms TTL=227
Reply from 209.51.159.226: bytes=32 time=1016ms TTL=227
Reply from 209.51.159.226: bytes=32 time=1016ms TTL=227

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


Back to 'Normal' again... :bawling:

C:\WINDOWS>ping eservers.biz

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

Reply from 209.51.159.226: bytes=32 time=645ms TTL=230
Reply from 209.51.159.226: bytes=32 time=646ms TTL=230
Reply from 209.51.159.226: bytes=32 time=646ms TTL=230
Reply from 209.51.159.226: bytes=32 time=645ms 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 = 645ms, Maximum = 646ms, Average = 645ms

Yeah... Speed is back to Normal normal now..!!! :cool:

still fine for me.
maybe your going through some other route:confused:

Okay From Kanada



1 64.229.176.1 HSE-MTL-ppp66096.qc.sympatico.ca 667 1875 63 63
2 64.230.244.65 dis26-toronto63-Vlan100.in.bellnexxia.net 651 1828 62 62
3 206.108.107.169 core3-toronto63-Gigabite4-0.in.bellnexxia.net 635 1781 62 62
4 206.108.103.114 core2-chicago23-pos0-0.in.bellnexxia.net 635 1750 78 78
5 206.108.103.122 bx2-chicago23-pos10-0.in.bellnexxia.net 610 1703 63 63
6 208.184.233.185 pos6-0.pr1.ord2.us.mfnx.net 599 1657 78 63
7 208.185.0.189 so-2-2-0.cr1.ord2.us.mfnx.net 589 1610 78 78
8 64.125.31.45 so-6-0-0.cr1.dca2.us.mfnx.net 588 1594 78 93
9 208.184.232.50 so-4-1-0.cr2.atl2.us.mfnx.net 578 1547 93 93
10 208.185.0.226 pos1-0.per1.atl2.us.mfnx.net 573 1516 94 110
11 66.115.128.53 tr1.atl2-1-1.national-net.com 99 93 110 94
12 66.115.128.42 tr1.atl1-1-8.national-net.com 94 94 94 94
13 209.51.137.125 156 156 156 156
14 209.51.142.186 156 156 156 156

Connection is alot better for me now too. :wavey:

Originally posted by JWong
C:\WINDOWS>ping eservers.biz

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

Reply from 209.51.159.226: bytes=32 time=1043ms TTL=227
Reply from 209.51.159.226: bytes=32 time=1044ms TTL=227
Reply from 209.51.159.226: bytes=32 time=1016ms TTL=227
Reply from 209.51.159.226: bytes=32 time=1016ms TTL=227

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


Back to 'Normal' again... :bawling:

Some of our users are better some are not! We aren't paying for a slow network. Let's see how long this takes to resolve.

my site is really slow :(NeoTrace Trace Version 3.25 Results
Target: perth.myacen.com
Date: 20/07/2002 (Saturday), 7:25:56 PM
Nodes: 17


Node Data
Node Net Reg IP Address Location Node Name
1 - - 192.168.0.4 Melbourne zen
2 1 - 192.168.0.1 Unknown
3 - - 0.0.0.0 Unknown No Response
4 2 1 198.142.0.2 12.375S, 130.725E meb2-ge2.gw.optusnet.com.au
5 3 2 202.139.0.37 Unknown pos2-3.mg1.optus.net.au
6 4 - 203.202.143.210 Unknown
7 5 3 208.173.173.217 San Francisco iar4-so-2-3-0-0.sanfrancisco.cw.net
8 6 3 206.24.210.61 San Francisco acr1-loopback.sanfrancisco.cw.net
9 5 3 208.172.146.103 Unknown agr3-loopback.santaclara.cw.net
10 5 3 208.172.156.153 Unknown dcr2-so-1-2-0.santaclara.cw.net
11 5 3 208.172.156.166 Unknown agr1-so-6-0-0.santaclara.cw.net
12 5 3 208.172.146.19 Unknown bpr2-loopback.paloaltopaix.cw.net
13 7 - 205.215.2.85 Unknown
14 7 4 205.215.12.1 Unknown gige2-1.tr1.sanfrancisco1.ca.us.netrail.net
15 8 4 66.28.28.202 Atlanta g3-0.pr1.atl01.netrail.net
16 7 - 205.215.2.6 Unknown
17 9 5 209.51.142.186 Atlanta perth.myacen.com


Packet Data
Node High Low Avg Tot Lost
1 0 0 0 1 0
2 16 0 1 11 0
3 ---- ---- ---- 22 22
4 11 8 9 11 0
5 11 8 10 11 0
6 176 171 171 11 0
7 180 177 178 11 0
8 183 178 178 11 0
9 182 175 178 11 0
10 180 176 176 11 0
11 197 176 183 11 0
12 184 178 180 11 0
13 959 841 898 12 1
14 926 840 905 11 0
15 1000 868 928 11 0
16 952 800 947 11 0
17 972 876 948 11 0


_____
NeoTrace Copyright ©1997-2001 NeoWorx Inc950 pings :(

normaly 250 or so when all is OK :(

Heres mine. Speeds OK, but not great.


C:\Documents and Settings\Alex>tracert sydney.myacen.com

Tracing route to sydney.myacen.com [209.51.138.218]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 9 ms 10 ms 9 ms c-24-130-168-1.we.client2.attbi.com [24.130.168.1]
3 8 ms 11 ms 8 ms bar02-p0-3.lsanhe4.ca.attbb.net [24.130.2.97]
4 10 ms 9 ms 9 ms bic02-d4-0.lsanhe3.ca.attbb.net [24.130.2.242]
5 10 ms 9 ms 9 ms 12.125.98.13
6 9 ms 9 ms 9 ms gbr2-p100.la2ca.ip.att.net [12.123.28.94]
7 24 ms 22 ms 26 ms tbr1-p013501.la2ca.ip.att.net [12.122.11.137]
8 18 ms 18 ms 19 ms tbr2-p012301.sffca.ip.att.net [12.122.10.37]
9 20 ms 18 ms 18 ms ggr1-p3100.sffca.ip.att.net [12.122.11.230]
10 24 ms 23 ms 24 ms nr1-p350.paix.ip.att.net [12.123.221.2]
11 23 ms 21 ms 22 ms 205.215.1.169
12 23 ms 23 ms 24 ms 205.215.12.1
13 102 ms 102 ms 102 ms g3-0.pr1.atl01.netrail.net [66.28.28.202]
14 104 ms 104 ms 104 ms 205.215.2.6
15 355 ms 232 ms 246 ms dv2-atl-core-core-b.dv2.net [209.51.131.2]
16 104 ms 103 ms 103 ms 209.51.138.218

Trace complete.

M:\Documents and Settings\hub5>tracert eservers.biz

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

1 1 ms <1 ms <1 ms 194.168.4.1
2 90 ms 15 ms 19 ms CPE-*****-1.qld.bigpond.net.au [***.
1]
3 22 ms 8 ms 10 ms 61.9.209.7
4 23 ms 63 ms 12 ms GigabitEthernet4-2.cha23.telstra.net [139.130.19
3.117]
5 9 ms 12 ms 13 ms GigabitEthernet4-0.woo-core1.Brisbane.telstra.ne
t [203.50.50.129]
6 23 ms 20 ms 20 ms Pos5-0.ken-core4.Sydney.telstra.net [203.50.6.22
1]
7 24 ms 22 ms 26 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22
]
8 59 ms 20 ms 21 ms GigabitEthernet0-0.syd-core01.Sydney.net.reach.c
om [203.50.13.242]
9 219 ms 211 ms 226 ms 202.84.143.5
10 211 ms 220 ms 217 ms i-13-0.paix-core01.PaloAlto.net.reach.com [202.8
4.251.49]
11 241 ms 217 ms 325 ms ge4-0.mpr2.pao1.us.mfnx.net [198.32.176.11]
12 237 ms 212 ms 215 ms so-4-1-0.mpr4.sjc2.us.mfnx.net [208.185.175.161]

13 215 ms 222 ms 211 ms pos12-0.cr7.sjc2.us.mfnx.net [64.125.30.13]
14 252 ms 252 ms 274 ms pos2-0.mpr1.dfw2.us.mfnx.net [208.184.232.81]
15 257 ms 251 ms 257 ms so-3-0-0.cr1.dfw2.us.mfnx.net [216.200.127.213]

16 275 ms 266 ms 276 ms so-4-1-0.cr1.atl2.us.mfnx.net [208.185.0.249]
17 353 ms 272 ms 268 ms pos0-0.per1.atl2.us.mfnx.net [208.185.0.222]
18 275 ms 269 ms 270 ms tr1.atl2-1-1.national-net.com [66.115.128.53]
19 267 ms 267 ms 269 ms tr1.atl1-1-8.national-net.com [66.115.128.42]
20 289 ms 367 ms 287 ms 209.51.137.125
21 263 ms 267 ms 265 ms velocity.eservers.biz [209.51.159.226]

Trace complete.

M:\Documents and Settings\hub5>

And the saga continues 1000ms pings to 50% of our users.

please send us specific traces you are having problems with and we will remedy them

Check your PM then :)

1 207.102.1.139 159ms 138ms 148ms TTL: 0 (pm2.stardate.ca ok)
2 207.102.1.254 148ms 142ms 140ms TTL: 0 (No rDNS)
3 64.114.172.202 174ms 155ms 410ms TTL: 0 (No rDNS)
4 204.174.217.6 175ms 153ms 155ms TTL: 0 (vancbc01br01.bb.telus.com fraudulent rDNS)
5 154.11.10.22 171ms 172ms 169ms TTL: 0 (clgrab21br01.bb.telus.com fraudulent rDNS)
6 154.11.10.165 172ms 169ms 177ms TTL: 0 (clgrab31br01.bb.telus.com fraudulent rDNS)
7 205.233.111.194 212ms 203ms 205ms TTL: 0 (chcnil23br00.bb.telus.com fraudulent rDNS)
8 216.200.254.30 211ms 203ms 217ms TTL: 0 (so-3-1-0.cr1.ord2.us.mfnx.net ok)
9 64.125.31.45 230ms 229ms 239ms TTL: 0 (so-6-0-0.cr1.dca2.us.mfnx.net ok)
10 208.184.232.50 244ms 233ms 236ms TTL: 0 (so-4-1-0.cr2.atl2.us.mfnx.net ok)
11 208.185.0.226 254ms 236ms 243ms TTL: 0 (pos1-0.per1.atl2.us.mfnx.net ok)
12 66.115.128.53 248ms 237ms 239ms TTL: 0 (tr1.atl2-1-1.national-net.com bogus rDNS: host not found [authoritative])
13 66.115.128.42 253ms 239ms 248ms TTL: 0 (tr1.atl1-1-8.national-net.com bogus rDNS: host not found [authoritative])
14 209.51.137.125 297ms 293ms 299ms TTL: 0 (No rDNS)
15 209.51.131.2 294ms 291ms 286ms TTL: 0 (dv2-atl-core-core-b.dv2.net ok)
16 209.51.138.218 302ms 294ms 304ms TTL:235 (sydney.myacen.com ok)


Hopefully this slow network doesnt become the norm for myacen. You deserve better than that for the price.

Originally posted by WoodShedd


Hopefully this slow network doesnt become the norm for myacen. You deserve better than that for the price.

I dont see how that as slow ... maybe you ought to look at the first hop which is 159m/sec.

302ms - 159ms = 143m/sec and since you are coming from Canada and depending on what connection you are on that is not bad at all.

Clients going via our Abovenet/National-net link are not affected by this.

On the other hand, we are working along with the carriers to get this fixed, until then we are rerouting paths to improve customers service.
Thanks for the continued support.

I was referring to previous traceroutes made by other forum members.

Sorry for the confusion :)

Thats understandable :D

30k sec from uunet backbone it's flying!

Who else is having slow speeds or is it just our servers?

Using Net tools to my server in DV2TraceRoute to 209.51.136.34

Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 66.46.176.3 -
2 0 0 0 216.191.97.41 pos5-3.core1-mtl.bb.attcanada.ca
3 15 0 16 216.191.65.173 pos8-1.core2-tor.bb.attcanada.ca
4 46 32 15 216.191.65.70 pos5-0.gwy1-chi.bb.attcanada.ca
5 31 16 16 216.191.65.38 po-9-2.pr1.ord2.us.mfnx.net
6 16 15 31 208.185.0.189 so-2-2-0.cr1.ord2.us.mfnx.net
7 47 31 47 64.125.31.45 so-6-0-0.cr1.dca2.us.mfnx.net
8 47 62 47 208.184.232.50 so-4-1-0.cr2.atl2.us.mfnx.net
9 47 47 63 208.185.0.226 pos1-0.per1.atl2.us.mfnx.net
10 141 234 47 66.115.128.53 tr1.atl2-1-1.national-net.com
11 47 62 172 66.115.128.42 tr1.atl1-1-8.national-net.com
12 125 79 46 209.51.137.125 -
13 172 156 47 209.51.131.2 dv2-atl-core-core-b.dv2.net
14 78 62 47 209.51.136.34 -

Trace complete


Ping 209.51.136.34
Round trip time to 209.51.136.34: 172 ms
Round trip time to 209.51.136.34: 62 ms
Round trip time to 209.51.136.34: 47 ms
Round trip time to 209.51.136.34: 63 ms
Round trip time to 209.51.136.34: 46 ms
Round trip time to 209.51.136.34: 63 ms
Round trip time to 209.51.136.34: 47 ms
Round trip time to 209.51.136.34: 62 ms
Round trip time to 209.51.136.34: 47 ms
Round trip time to 209.51.136.34: 63 ms


Average time over 10 pings: 67.2 ms

I get good pings now however transfer speeds are very very slow

Mine are still good here. No problems personally and no customer complaints.

Could you have a bad network card?

Doubt it on 3 servers.

Can someone test this:

http://sydney.myacen.com/~tools/uumap.tar.Z

Sent you a PM with a download link to test my server download speed against your servers.

Using Telstra cable I am seeing about 19kb/Sec

Originally posted by Monte
Using Telstra cable I am seeing about 19kb/Sec

Exactly, users on telstra cable before where getting 150kb/sec (uncapped now its around 15-20k) optus cable people are having the same problem now me(Im on netspace) receiving a maximum of 15k.

25.43 KB/s from a box at VO

Originally posted by Jedito
25.43 KB/s from a box at VO

Thanks Jorge, so it's a problem as I figured.

Seems like :(

I got piks of 50 Kb/s but lows of 13 Kb/s

18 KB/sec

Hovering around 18k here Robert, on Netspace.

Cheers

Gary

Thanks guys, just to confirm:

New server dv2 still:

http://perth.myacen.com/~tools/uumap.tar.Z

That's better mate. Levelled out at 52.0 and stayed there.

Cheers

Gary

Much worse here on Tesltra cable. 7.8KB/Sec

Originally posted by Monte
Much worse here on Tesltra cable. 7.8KB/Sec

Their has to be a prolem with DV2 & Telstra

Originally posted by Editor
That's better mate. Levelled out at 52.0 and stayed there.

Cheers

Gary

Thanks Gary! Netspace is great :)

Wel I don't doubt the problem with Telstra. They suck!

Originally posted by Monte
Wel I don't doubt the problem with Telstra. They suck!

No doubt :D, well can you max out your connection to your servers?

I just tried the speed test on my DV2 server and it is running at 40kb/sec

First server: 892,632 63.82K/s ETA 01:56

Perth server: I gave up.
Connecting to perth.myacen.com[209.51.142.186]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8,520,221 [application/x-tar]

0% [ ] 25,647 257.82B/s ETA 9:09:08^

(yes, that's bytes, not kilo bytes)

It isn't Telstra, this is from NAC !!

Originally posted by Monte
I just tried the speed test on my DV2 server and it is running at 40kb/sec

Monte, do you have ICQ or MSN? Can you contact me:

All of a sudden things are much better for you myacen:
8,520,221 1.70M/s ETA 00:00

Here's the route:
traceroute to perth.myacen.com (209.51.142.186), 64 hops max, 40 byte packets
1 64-21-150-1.site5.com (64.21.150.1) 0.361 ms 0.287 ms 0.382 ms
2 a9-0-0-1118.msfc1.nyc.nac.net (209.123.11.9) 3.235 ms 2.283 ms 2.469 ms
3 fe4-1-0.per1.lga3.us.mfnx.net (216.200.254.26) 3.612 ms 3.461 ms 2.592 ms
4 so-3-0-1.cr1.lga3.us.mfnx.net (208.185.0.181) 2.949 ms 4.357 ms 2.818 ms
5 so-5-2-0.cr1.lga1.us.mfnx.net (64.125.30.17) 2.908 ms 3.599 ms 2.910 ms
6 so-0-0-0.cr1.lga2.us.mfnx.net (208.185.0.246) 3.279 ms 2.881 ms 3.665 ms
7 so-5-0-0.cr1.atl2.us.mfnx.net (208.184.232.165) 18.804 ms 17.779 ms 19.095 ms
8 pos0-0.per1.atl2.us.mfnx.net (208.185.0.222) 18.599 ms 18.697 ms 18.480 ms
9 tr1.atl2-1-1.national-net.com (66.115.128.53) 19.369 ms 18.330 ms 20.028 ms
10 tr1.atl1-1-8.national-net.com (66.115.128.42) 18.666 ms 18.853 ms 18.472 ms
11 209.51.137.125 (209.51.137.125) 21.155 ms 20.260 ms 22.328 ms
12 209.51.142.186 (209.51.142.186) 21.395 ms 22.063 ms 20.486 ms

The above was from a server at Site5/NAC. This is from a workstation / ADSL in western Canada:
2,391,697 156.98K/s ETA 00:38

Back in business you appear to be.

Originally posted by mwatkins
All of a sudden things are much better for you myacen:
8,520,221 1.70M/s ETA 00:00

Here's the route:
traceroute to perth.myacen.com (209.51.142.186), 64 hops max, 40 byte packets
1 64-21-150-1.site5.com (64.21.150.1) 0.361 ms 0.287 ms 0.382 ms
2 a9-0-0-1118.msfc1.nyc.nac.net (209.123.11.9) 3.235 ms 2.283 ms 2.469 ms
3 fe4-1-0.per1.lga3.us.mfnx.net (216.200.254.26) 3.612 ms 3.461 ms 2.592 ms
4 so-3-0-1.cr1.lga3.us.mfnx.net (208.185.0.181) 2.949 ms 4.357 ms 2.818 ms
5 so-5-2-0.cr1.lga1.us.mfnx.net (64.125.30.17) 2.908 ms 3.599 ms 2.910 ms
6 so-0-0-0.cr1.lga2.us.mfnx.net (208.185.0.246) 3.279 ms 2.881 ms 3.665 ms
7 so-5-0-0.cr1.atl2.us.mfnx.net (208.184.232.165) 18.804 ms 17.779 ms 19.095 ms
8 pos0-0.per1.atl2.us.mfnx.net (208.185.0.222) 18.599 ms 18.697 ms 18.480 ms
9 tr1.atl2-1-1.national-net.com (66.115.128.53) 19.369 ms 18.330 ms 20.028 ms
10 tr1.atl1-1-8.national-net.com (66.115.128.42) 18.666 ms 18.853 ms 18.472 ms
11 209.51.137.125 (209.51.137.125) 21.155 ms 20.260 ms 22.328 ms
12 209.51.142.186 (209.51.142.186) 21.395 ms 22.063 ms 20.486 ms

Thanks! still why is it slow one time and fast at another :(

Can't tell - would need to see the before and after picture from a bunch of routes. At least eservers / dv2 appear to be responsive.

From a server at NAC:
root@swordfish [/home]# wget http://perth.myacen.com/~tools/uumap.tar.Z
--13:25:39-- http://perth.myacen.com/%7Etools/uumap.tar.Z
=> `uumap.tar.Z'
Resolving perth.myacen.com... done.
Connecting to perth.myacen.com[209.51.142.186]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8,520,221 [application/x-tar]

100%[====================================>] 8,520,221 1.78M/s ETA 00:00

13:25:48 (1.78 MB/s) - `uumap.tar.Z' saved [8520221/8520221]

root@swordfish [/home]#


From a server at Colo4Dallas:

18:28:49 (590.40 KB/s) - `uumap.tar.Z' saved [8520221/8520221]

We, are looking into the issue...

Looks like National-Net *maybe* playing up... thats why things keep on going from good to bad.

If, anyone is stil having problems, please do a traceroute and send the mail to trace@eservers.biz it will help us isolate the routes that are causing the problem...

Imran

Here's my latest tracert from home:

8 214 ms 262 ms 215 ms pos1-0.per1.atl2.us.mfnx.net [208.185.0.226]
9 238 ms 215 ms 264 ms tr1.atl2-1-1.national-net.com [66.115.128.53]
10 215 ms 214 ms 219 ms tr1.atl1-1-8.national-net.com [66.115.128.42]
11 * * 462 ms 209.51.137.125
12 403 ms * * server.hostname
[1.2.3.4]
13 * 416 ms * server.hostname
[1.2.3.4]
14 * 507 ms * server.hostname
[1.2..3.4]
15 * 521 ms 499 ms server.hostname
[1.2.3.4]

Trace complete.

C:\WINDOWS>ping eservers.biz

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

Reply from 209.51.159.226: bytes=32 time=671ms TTL=233
Reply from 209.51.159.226: bytes=32 time=811ms TTL=233
Reply from 209.51.159.226: bytes=32 time=724ms TTL=233
Reply from 209.51.159.226: bytes=32 time=751ms TTL=233

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

Compare to... WHT

C:\WINDOWS>ping webhostingtalk.com

Pinging webhostingtalk.com [207.218.223.148] with 32 bytes of data:

Reply from 207.218.223.148: bytes=32 time=412ms TTL=240
Reply from 207.218.223.148: bytes=32 time=344ms TTL=240
Reply from 207.218.223.148: bytes=32 time=351ms TTL=240
Reply from 207.218.223.148: bytes=32 time=331ms TTL=240

Ping statistics for 207.218.223.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 331ms, Maximum = 412ms, Average = 359ms

Almost 100% Faster Please do something

Haven't try on 56K Modem (most users) yet
but suspect that will go over 1000 mark

2PM (GMT +6) Tuesday

Well this issue is still not solved. Seems as though DV2 are slipping. One of our servers still has slow speeds after eservers told us it was going to be looked into.

The issue has been resolved my end at the moment in that I am no longer being routed through national-net/mfnx but rather netrail instead and the pings are back to low 200's.

http://perth.myacen.com/~tools/uumap.tar.Z
max. 53kb/s from a 2mbit line in germany.
hm. not very good.

we have decided to bring in another connection in addition to what we already have. We are taking any input right now in the selection of that connection. We are exmaning : ATT, Genuity, C/W, Sprint and qwest . We will be making our decision by friday so now is the time to put your 2 cents in.

Qwest

ATT, Genuity or C&W from that list.

Just out of curiosity, what seems to be the problem? Do you think a new provider will help?

AT&T or Genuity

Mike,

There are no problems as such, Cogent has some peering issue's which now are fixed...

We are improving the network and connectivity and would like to know what our customers would like us to add...

Sorry, I thought DV2 had more bandwidth than Cogent.

Mike,

We do have more bandwidth than Cogent and you know that pretty well :eek: We utilise BGP4 hence the reason only some customer were affected.

Adding a new tier1 will make our network even better :D

So when you add another provider youll have 3 different providers?

ATT or Genuity :)

Oh yeah, I forgot who I was talking to. Sorry.

Adding a new tier1 will make our network even better
:D :D :D

Originally posted by universal2001
Adding a new tier1 will make our network even better
:D :D :D
And your point is?

Speaking from my experience with most of the circuits you are mentioning let me give you my review.

The AT&T Circuit is VERY FAST but their peering isn't that great, but is improving.

C&W is a great and very reliable circuit, but they have not been very flexible on pricing lately.

Qwest appears to be ok, we are not directly connected to them.

Genuity is a good and stable circuit, and most importantly if you are interested in a burstable OC3, they go down to a 20Mbit tier for a tad over 10k not including the loop.

Have you considered a circuit from Broadwing? They have very good peering arrangements and are eager to work with customers.

If you need traceroutes from any of these I will provide the ones that I have.

-Robert

I have a server at eServers.biz.
I also suffer from slow connection and sent them an email.
But they didn't give us any information about what's going on.
They didn't even admit there has been a problem:angry:

They are not what I expected.
I just wanted to know what's going on.
Of cource network issue is not always their fault.
Is this case,it may be Cogent's fault.

Is there anyone still having this problem?
Or this is only my problem :rolleyes:

ampan:

When a clients sends a email with a traceroute which is fine and says "I am having major packet loss", all one can do is reply like i did with "There is no packet loss shown in the trace route supplied, please supply more detail"

Hence from the traceroute you showed there were no problems, i have just tested your issue for the last 30 minutes and send a detailed report.

================================================
=== VisualRoute report on 24-Jul-02 21:49:13 ===
================================================

Report for server.dvd-critic.net [209.51.131.242]

Analysis: 'server.dvd-critic.net' was found in 14 hops (TTL=244).

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 212.126.138.32 | moose-shack | * | | | | Claranet NOC and Customer Network |
| 1 | | 195.8.83.38 | fab-rk-38.access.clara.net | ?London, UK | * | 46 | x | Claranet Modem Pool Allocation 2 |
| 2 | | 195.8.83.128 | access-fe-0-0-0-banner-starbuck.router.clara.net | ?London, UK | * | 47 | x-- | Claranet Modem Pool Allocation 2 |
| 3 | | 195.8.68.138 | atm-6-0-0-telee-tashtego.router.clara.net | ?London, UK | * | 46 | x | Claranet NOC and Customer Network |
| 4 | | 213.253.16.65 | ge-1-0-0-telee-peleg.router.clara.net | ?London, UK | * | 46 | x | Claranet NOC and Customer Network |
| 5 | | 195.66.224.76 | ge2-0.mpr1.lhr1.uk.mfnx.net | ?London, UK | * | 46 | x | London Internet exchange (LINX) |
| 6 | | 208.184.231.21 | so-4-2-0.cr1.lga1.us.mfnx.net | ?San Jose, CA 95113 | | 109 | x | Abovenet Communications, Inc. |
| 7 | | 208.185.0.246 | so-0-0-0.cr1.lga2.us.mfnx.net | ?San Jose, CA 95113 | | 115 | x | Abovenet Communications, Inc. |
| 8 | | 64.124.232.6 | core1-lga2-oc48.lga4.above.net | New York, NY, USA | -05:00 | 116 | x | Abovenet Communications, Inc. |
| 9 | | 64.124.51.186 | 64.124.51.186.cogentco.com | - | | 109 | x | Abovenet Communications, Inc. |
| 10 | | 66.28.4.81 | p4-0.core02.dca01.atlas.cogentco.com | Washington, DC, USA | -05:00 | 156 | -x----- | Cogent Communications |
| 11 | | 66.28.4.125 | p14-0.core01.atl01.atlas.cogentco.com | Atlanta, GA, USA | -05:00 | 125 | x- | Cogent Communications |
| 12 | | 66.28.5.242 | g49.ba01.b000173-0.atl01.atlas.cogentco.com | Atlanta, GA, USA | -05:00 | 131 | x- | Cogent Communications |
| 13 | | 66.28.28.254 | dv2.demarc.cogentco.com | - | | 134 | x- | Cogent Communications |
| 14 | | 209.51.131.242 | server.dvd-critic.net | ?Atlanta, GA 30303 | | 128 | x- | Net Depot, Inc. |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to server.dvd-critic.net, average = 128ms, min = 125ms, max = 141ms -- 24-Jul-02 21:49:13


Routing seems OK from the UK

James

Broadwing :eek: :smash:


Go with AT&T :)