Anyone else having slow or intermittent access problems? Not sure if it's just me...

1 <1 ms <1 ms <1 ms NTT1G [192.168.0.10]
2 8 ms 9 ms 21 ms 10.126.128.1
3 9 ms 10 ms 11 ms gsr01-dn.blueyonder.co.uk [62.31.64.225]
4 20 ms 19 ms 21 ms gat-edi-pos.telewest.net [194.117.136.10]
5 25 ms 20 ms 21 ms tele2-gat-pos.telewest.net [194.117.136.6]
6 21 ms 21 ms 23 ms ge51-linx-gw1.cableinet.net [194.117.154.9]
7 92 ms 90 ms 94 ms lndnuk1icx1.wcg.net [195.66.224.105]
8 91 ms 94 ms 96 ms nycmny2wcx3-oc3.wcg.net [64.200.87.133]
9 108 ms 107 ms 106 ms nycmny2wcx2-oc48.wcg.net [64.200.87.77]
10 107 ms 115 ms 108 ms hrndva1wcx2-oc48.wcg.net [64.200.240.46]
11 111 ms 108 ms 111 ms hrndva1wcx3.oc48.wcg.net [64.200.95.78]
12 108 ms 108 ms 108 ms drvlga1wcx2-pos.wcg.net [64.200.210.57]
13 116 ms 108 ms 111 ms atlnga6lce1-pos5-0.wcg.net [64.200.127.62]
14 * * 119 ms atlnga6lce1-cuttingedge-atm.wcg.net [64.200.126.70]
15 * 121 ms * *
16 * * * *

Problems here. We're down for 20 mins now

Glad to know it's not just me

This is bad

Not again :rolleyes:

got all the symptoms...

this really sucks

guess it's just us then?

Nope same problem

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

1 <10 ms <10 ms <10 ms 192.168.0.1
2 16 ms 15 ms 16 ms wpp2.wa [172.31.22.154]
3 16 ms <10 ms 31 ms 172.31.25.154
4 15 ms 16 ms 15 ms core1-0-0-61.Perth.netspace.net.au [203.17.99.30
]
5 16 ms 16 ms 15 ms FastEthernet2-0-10.cor2.per.connect.com.au [210.
9.196.130]
6 62 ms 219 ms 94 ms fastethernet6-0-0.bdr1.per.connect.com.au [203.6
3.113.94]
7 78 ms 78 ms 94 ms atm9-1-0-4.bdr2.syd.connect.com.au [203.63.112.6
5]
8 78 ms 78 ms 94 ms g2-0-2.sybr3.global-gateway.net.nz [202.50.119.9
7]
9 250 ms 250 ms 250 ms p4-4.pabr2.global-gateway.net.nz [202.50.116.194
]
10 250 ms 250 ms 250 ms g0-0-0-0.pabr3.global-gateway.net.nz [202.50.245
.24]
11 * * * Request timed out.
12 266 ms 265 ms 250 ms sntcca2lce1-oc48.wcg.net [64.200.210.177]
13 313 ms 312 ms 313 ms snfcca1wcx2-oc48.wcg.net [64.200.199.77]
14 329 ms 312 ms 313 ms anhmca1wcx3-oc48.wcg.net [64.200.240.1]
15 312 ms 328 ms 313 ms anhmca1wcx2-oc48.wcg.net [64.200.143.73]
16 313 ms 328 ms 312 ms dllstx1wcx3-oc48.wcg.net [64.200.240.5]
17 312 ms 313 ms 312 ms drvlga1wcx1-oc48.wcg.net [64.200.240.22]
18 312 ms 313 ms 312 ms atlnga6lce1-pos2-0.wcg.net [64.200.127.82]
19 328 ms 328 ms 313 ms atlnga6lce1-cuttingedge-atm.wcg.net [64.200.126.
70]
20 * * * Request timed out.
21 * 328 ms 344 ms cet-dv2.transit.dv2.net [209.51.130.33]
22 328 ms * * myacen.com [216.180.224.69]

down as well for us.. just one of our servers that is

Guys sorry its the script kiddies, being DDOS'd - filtering the network as we speak..

All should be pretty stable as I type this message..

-Shazad

EDIT : I spoke a little to soon :(

back here :)

Noticed something interesting...cogent test peering has become cogent.atdn.net :D

Congratulations Cogent :beer:

<edit> spoke too soon...back down again...</edit>

Internal Network Trace
traceroute to myacen.com (216.180.224.69), 30 hops max, 38 byte packets
1 216.180.225.97 (216.180.225.97) 0.594 ms 0.465 ms 0.414 ms
2 209.51.130.241 (209.51.130.241) 0.467 ms 0.498 ms 0.393 ms
3 myacen.com (216.180.224.69) 0.397 ms 0.416 ms 0.305 ms

External Trace
1 <1 ms <1 ms <1 ms NTT1G [192.168.0.10]
2 9 ms 9 ms 9 ms 10.126.128.1
3 13 ms 9 ms 10 ms gsr01-dn.blueyonder.co.uk [62.31.64.225]
4 21 ms 22 ms 60 ms gat-edi-pos.telewest.net [194.117.136.10]
5 24 ms 19 ms 20 ms tele2-gat-pos.telewest.net [194.117.136.6]
6 20 ms 21 ms 37 ms ge51-linx-gw1.cableinet.net [194.117.154.9]
7 89 ms 94 ms 131 ms lndnuk1icx1.wcg.net [195.66.224.105]
8 91 ms 90 ms 92 ms nycmny2wcx3-oc3.wcg.net [64.200.87.133]
9 109 ms 108 ms 124 ms nycmny2wcx2-oc48.wcg.net [64.200.87.77]
10 110 ms 110 ms 108 ms hrndva1wcx2-oc48.wcg.net [64.200.240.46]
11 108 ms 108 ms 111 ms hrndva1wcx3.oc48.wcg.net [64.200.95.78]
12 108 ms 117 ms 108 ms drvlga1wcx2-pos.wcg.net [64.200.210.57]
13 111 ms 107 ms 113 ms atlnga6lce1-pos5-0.wcg.net [64.200.127.62]
14 * 120 ms 122 ms atlnga6lce1-cuttingedge-atm.wcg.net [64.200.126.70]
15 * * * Request timed out.

Update : The offending server has been blackholed and everything should be moving fine again...

Thank you for your support and have a great weekend.
-Shazad

thanks to my team for quickly handling this dos

sailor : congrats for the intelligent team.


cabalstudios : are you originally from pakistan? :) i also had a friend name Shehzad.

AmericaD:

No I am not, thought I know my name originates from their which is where my parents are from :)

Have a great weekend.

P.S. Could I be your long lost friend ... ;) hehe you wished *smerks*

Originally posted by cabalstudios
AmericaD:

No I am not, thought I know my name originates from their which is where my parents are from :)


Nice. So are my parents :) and i do visit Pakistan once in a while along with other countries i lived.


P.S. Could I be your long lost friend ... ;) hehe you wished *smerks*

sure, buddy :)

sailor - please check the pm and/or mail i've sent you!

8 68 ms 83 ms 137 ms dcr1-so-3-1-0.Chicago.cw.net [208.175.10.85]
9 83 ms 69 ms 137 ms agr4-so-0-0-0.Chicago.cw.net [208.175.10.30]
10 69 ms 69 ms 68 ms acr2-loopback.Chicago.cw.net [208.172.2.62]
11 96 ms 82 ms 83 ms williams-communications-inc.Chicago.cw.net [208.172.1.130]
12 69 ms 68 ms 69 ms chcgil1wcx2-oc48.wcg.net [64.200.103.73]
13 69 ms 69 ms 82 ms chcgil1wcx2-pos.wcg.net [64.200.240.73]
14 68 ms 69 ms 69 ms atlnga6lce1-pos5-0.wcg.net [64.200.127.62]
15 83 ms 83 ms 151 ms atlnga6lce1-cuttingedge-atm.wcg.net [64.200.126.70]
16 55 ms 55 ms 55 ms 10.30.30.2
17 2527 ms 2512 ms 2527 ms cet-dv2.transit.dv2.net [209.51.130.33]


:stickout:

C:\WINDOWS>tracert 208.175.10.85

Tracing route to dcr1-so-3-1-0.Chicago.cw.net [208.175.10.85]
over a maximum of 30 hops:

1 19 ms 17 ms 17 ms x.dv2.net [209.51.x.x]
2 17 ms 18 ms 18 ms atl-core-router-b.dv2.net [209.51.137.77]
3 24 ms 18 ms 18 ms dv2-cet.transit.dv2.net [209.51.130.34]
4 17 ms 18 ms 19 ms 10.30.30.1
5 18 ms 17 ms 18 ms atlnga6lce1-atm.wcg.net [64.200.126.69]
6 18 ms 17 ms 17 ms drvlga1wcx1-pos4-0.wcg.net [64.200.127.81]
7 37 ms 36 ms 36 ms dllstx1wcx3-oc48.wcg.net [64.200.240.21]
8 36 ms 37 ms 36 ms acr2-so-6-0-0.Dallas.cw.net [208.172.129.225]
9 85 ms 38 ms 37 ms agr3-loopback.Dallas.cw.net [208.172.130.103]
10 37 ms 37 ms 39 ms dcr1-so-0-2-0.Dallas.cw.net [208.172.139.9]
11 49 ms 49 ms 51 ms dcr1-so-3-1-0.Chicago.cw.net [208.175.10.85]

Trace complete.

I'm getting something similar but it looks to be a BBN issue again - but isn't there a way the d/c can route around it e.g. not send out on cogent:

In to DC:

1 143 ms 138 ms 127 ms lemur.lns.birmingham.access.planet.net.uk [195.9
2.168.21]
2 131 ms 132 ms 126 ms pbr-1.brm.as5388.net [195.92.168.2]
3 204 ms 208 ms 201 ms 195.66.224.105
4 384 ms 870 ms 926 ms lndnuk1lcx1-oc3.wcg.net [64.200.87.146]
5 196 ms 197 ms 200 ms nycmny2wcx3-atm14-3.wcg.net [64.200.87.237]
6 235 ms 236 ms 239 ms nycmny2wcx2-oc48.wcg.net [64.200.87.77]
7 232 ms 232 ms 235 ms hrndva1wcx2-oc48.wcg.net [64.200.240.46]
8 235 ms 238 ms 236 ms hrndva1wcx3.oc48.wcg.net [64.200.95.78]
9 239 ms 237 ms 235 ms drvlga1wcx2-pos.wcg.net [64.200.210.57]
10 222 ms 215 ms 212 ms atlnga6lce1-pos5-0.wcg.net [64.200.127.62]
11 224 ms 212 ms 222 ms atlnga6lce1-cuttingedge-atm.wcg.net [64.200.126.
70]
12 227 ms 225 ms 220 ms 10.30.30.2
13 1419 ms 1432 ms 1437 ms cet-dv2.transit.dv2.net [209.51.130.33]
14 1478 ms 1480 ms 1466 ms server.com [209.51.xxx.xxx]

out from DV2:

traceroute to 217.135..xxx.xxx (217.135..xxx.xxx), 30 hops max, 38 byte packets
1 209.51.xxx.xx(209.51..xxx.xxx) 0.446 ms 0.387 ms 0.395 ms
2 f13.ba01.b000173-0.atl01.atlas.cogentco.com (66.28.28.253) 1.074 ms 6.550 ms 0.840 ms
3 g0-2.core01.atl01.atlas.cogentco.com (66.28.5.241) 0.375 ms 0.738 ms 0.583 ms
4 p15-0.core01.jax01.atlas.cogentco.com (66.28.4.137) 7.371 ms 6.988 ms 8.754 ms
5 p14-0.core01.mco01.atlas.cogentco.com (66.28.4.153) 10.404 ms 9.939 ms 10.580 ms
6 p14-0.core01.tpa01.atlas.cogentco.com (66.28.4.142) 11.700 ms 12.059 ms 11.713 ms
7 p5-0.core01.iah01.atlas.cogentco.com (66.28.4.45) 32.765 ms 31.352 ms 31.884 ms
8 p14-0.core01.san01.atlas.cogentco.com (66.28.4.6) 62.801 ms 62.057 ms 62.026 ms
9 p4-0.core01.lax01.atlas.cogentco.com (66.28.4.77) 64.756 ms 64.691 ms 64.883 ms
10 p14-0.core01.sjc01.atlas.cogentco.com (66.28.4.74) 76.548 ms 75.764 ms 75.805 ms
11 p4-0.core01.sfo01.atlas.cogentco.com (66.28.4.93) 77.567 ms 76.993 ms 77.158 ms
12 p15-0.core02.sfo01.atlas.cogentco.com (66.28.4.70) 154.793 ms 272.028 ms 237.516 ms
13 p6-0.tr1.sfr1.netrail.net (66.28.28.58) 77.593 ms 77.453 ms 77.650 ms
14 p4-0.pr1.SanFrancisco1.CA.us.netrail.net (205.215.12.2) 77.890 ms 77.603 ms 77.592 ms
15 205.215.2.78 (205.215.2.78) 1238.029 ms 1231.279 ms 1223.153 ms
16 p6-0.snjpca1-br1.bbnplanet.net (4.24.7.61) 1199.910 ms 1200.062 ms 1211.049 ms
17 p9-0.snjpca1-br2.bbnplanet.net (4.24.9.130) 1214.299 ms 1196.910 ms 1181.172 ms
18 p3-0.dnvtco1-br2.bbnplanet.net (4.0.6.226) 1308.654 ms 1425.656 ms 1250.178 ms
19 so-0-0-0.chcgil2-br2.bbnplanet.net (4.24.9.61) 1204.236 ms 1220.485 ms 1216.964 ms
20 so-7-0-0.chcgil2-br1.bbnplanet.net (4.24.5.217) 1227.335 ms 1217.833 ms 1234.977 ms
21 p13-0.iplvin1-br1.bbnplanet.net (4.24.9.58) 1210.119 ms 1237.143 ms 1338.148 ms
22 p15-0.iplvin1-br2.bbnplanet.net (4.24.10.154) 1197.247 ms 1212.944 ms 1196.056 ms
23 p13-0.phlapa1-br1.bbnplanet.net (4.24.10.181) 1196.710 ms 1188.407 ms 1184.948 ms
24 p7-0.london2-cr3.bbnplanet.net (195.16.175.250) 1316.777 ms 1312.835 ms 1309.148 ms
25 p1-0.london2-cr4.bbnplanet.net (195.16.175.174) 1329.811 ms 1325.304 ms 1305.244 ms
26 gigabitethernet1-0.energisuk.bbnplanet.net (212.133.14.98) 1325.390 ms 1322.119 ms 1324.284 ms
27 lemur.lns.birmingham.access.planet.net.uk (195.92.168.21) 1318.870 ms 1372.018 ms 1347.283 ms

On the same note:

Tracing to bbnplanet.net from home and from dv2 outwards is clean and fast - looks like when DV2 send out on cogent and it crosses over to bbn then the issues occur.

ALSO - Looks like when you are tracing into DV2, it looks like Williams line is the problem but infact it may not be here...

13 p6-0.tr1.sfr1.netrail.net (66.28.28.58) 77.593 ms 77.453 ms 77.650 ms
14 p4-0.pr1.SanFrancisco1.CA.us.netrail.net (205.215.12.2) 77.890 ms 77.603 ms 77.592 ms

There's your problem


netrail:smash:

[...]
7 p16-7-0-0.r01.mclnva02.us.bb.verio.net (129.250.5.11) 121.613 ms 123.353 ms 123.10 ms
8 p16-0-0-0.r00.atlnga03.us.bb.verio.net (129.250.2.49) 136.91 ms 137.986 ms 137.225 ms
9 ge-0-0-0.a00.atlnga03.us.ra.verio.net (129.250.26.227) 136.741 ms 136.471 ms 137.186 ms
10 ge-1-1.a02.atlnga03.us.ra.verio.net (129.250.26.229) 137.69 ms 137.955 ms ge-1-2.a02.atlnga03.us.ra.verio.net (129.250.25.68) 135.796 ms
11 ge-3-3.a02.atlnga03.us.ce.verio.net (157.238.161.42) 133.596 ms 134.51 ms 133.793 ms
12 66.205.207.1 (66.205.207.1) 135.615 ms 134.952 ms 133.678 ms
13 10.30.30.2 (10.30.30.2) 133.657 ms 133.810 ms 133.687 ms
14 cet-dv2.transit.dv2.net (209.51.130.33) 676.421 ms 652.369 ms 668.637 ms
15 core-a.dv2.net (209.51.131.1) 675.994 ms 638.737 ms 620.62 ms
[...]

looks like the problem is located at DV2, not williams, nor verio.

trace out from your server at dv2 and see what the return route is like - trace routes can sometimes be misleading if the response is coming back on a different route you will get slow pings from when ever they come back on the bad route...

It is getting worse to me :bawling:


From my home ...
9 343 ms 344 ms 343 ms agr3-so-0-0-0.Chicago.cw.net [208.175.10.10]
10 343 ms 1126 ms 329 ms acr2-loopback.Chicago.cw.net [208.172.2.62]
11 82 ms 82 ms 69 ms williams-communications-inc.Chicago.cw.net [208.172.1.130]
12 96 ms 82 ms 69 ms chcgil1wcx2-oc48.wcg.net [64.200.103.73]
13 82 ms 110 ms 82 ms chcgil1wcx2-pos.wcg.net [64.200.240.73]
14 96 ms 69 ms 69 ms atlnga6lce1-pos5-0.wcg.net [64.200.127.62]
15 69 ms 68 ms 83 ms atlnga6lce1-cuttingedge-atm.wcg.net [64.200.126.70]
16 68 ms 69 ms 69 ms 10.30.30.2
17 * * * Request timed out.
18 * * 3488 ms 209.51.130.242
... then to my server

Getting better now, but still slow... I normally get <70ms
This problem happened yesterday night (24 hours ago)


9 124 ms 96 ms 82 ms agr3-so-0-0-0.Chicago.cw.net [208.175.10.10]
10 302 ms 275 ms 275 ms acr2-loopback.Chicago.cw.net [208.172.2.62]
11 68 ms 83 ms 68 ms williams-communications-inc.Chicago.cw.net [208.172.1.130]
12 69 ms 54 ms 69 ms chcgil1wcx2-oc48.wcg.net [64.200.103.73]
13 96 ms 82 ms 69 ms chcgil1wcx2-pos.wcg.net [64.200.240.73]
14 69 ms 69 ms 55 ms atlnga6lce1-pos5-0.wcg.net [64.200.127.62]
15 82 ms 69 ms 68 ms atlnga6lce1-cuttingedge-atm.wcg.net [64.200.126.70]
16 72ms 96 ms 68 ms 10.30.30.2
17 920 ms 934 ms 975 ms cet-dv2.transit.dv2.net [209.51.130.33]
18 920 ms 934 ms 907 ms 209.51.130.242

Whats the trace out from dv2 to the up you are coming from like?

E:\>tracert 208.175.10.10

Tracing route to agr3-so-0-0-0.Chicago.cw.net [208.175.10.10]
over a maximum of 30 hops:

1 * * * Request timed out.
2 10 ms <10 ms <10 ms dv2-atl-core-a.dv2.net [209.51.128.1]
3 <10 ms 10 ms <10 ms core-b.dv2.net [209.51.131.2]
4 <10 ms <10 ms 11 ms dv2-cet.transit.dv2.net [209.51.130.34]
5 10 ms <10 ms <10 ms 10.30.30.1
6 10 ms <10 ms <10 ms atlnga6lce1-atm.wcg.net [64.200.126.69]
7 <10 ms 10 ms <10 ms drvlga1wcx1-pos4-0.wcg.net [64.200.127.81]
8 20 ms 20 ms 20 ms dllstx1wcx3-oc48.wcg.net [64.200.240.21]
9 20 ms 30 ms 20 ms acr2-so-6-0-0.Dallas.cw.net [208.172.129.225]
10 20 ms 20 ms 20 ms agr4-loopback.Dallas.cw.net [208.172.130.104]
11 20 ms 20 ms 31 ms dcr1-so-1-3-0.Dallas.cw.net [208.172.139.29]
12 30 ms 40 ms 40 ms dcr1-loopback.Chicago.cw.net [208.172.2.99]
13 60 ms 30 ms 40 ms agr3-so-0-0-0.Chicago.cw.net [208.175.10.10]

traceroute from my server to 208.175.10.10


traceroute to 208.175.10.10 (208.175.10.10), 30 hops max, 38 byte packets
1 209.51.139.113 (209.51.139.113) 0.847 ms 0.489 ms 0.424 ms
2 209.51.130.241 (209.51.130.241) 0.474 ms 0.349 ms 0.339 ms
3 dv2-cet.transit.dv2.net (209.51.130.34) 0.664 ms 0.476 ms 0.402 ms
4 10.30.30.1 (10.30.30.1) 62.906 ms 44.155 ms 0.804 ms
5 atlnga6lce1-atm.wcg.net (64.200.126.69) 1.041 ms 0.865 ms 0.779 ms
6 drvlga1wcx1-pos4-0.wcg.net (64.200.127.81) 1.221 ms 1.380 ms 1.423 ms
7 dllstx1wcx3-oc48.wcg.net (64.200.240.21) 19.202 ms 18.944 ms 18.986 ms
8 acr2-so-6-0-0.Dallas.cw.net (208.172.129.225) 19.553 ms 19.769 ms 19.823 ms
9 agr4-loopback.Dallas.cw.net (208.172.130.104) 20.114 ms 20.235 ms 19.969 ms
10 dcr2-so-1-3-0.Dallas.cw.net (208.172.139.157) 20.079 ms 19.702 ms 20.075 ms
11 dcr1-loopback.Chicago.cw.net (208.172.2.99) 32.668 ms 32.498 ms 32.913 ms
12 agr3-so-0-0-0.Chicago.cw.net (208.175.10.10) 32.618 ms 32.649 ms 32.666 ms


but from my home to the server, it is still sluggish


7 28 ms 27 ms 27 ms gw01.wlfdle.phub.net.cable.rogers.com [66.185.80.14]
8 55 ms 55 ms 54 ms dcr1-so-3-1-0.Chicago.cw.net [208.175.10.85]
9 69 ms 68 ms 69 ms agr3-so-0-0-0.Chicago.cw.net [208.175.10.10]
10 69 ms 68 ms 69 ms acr2-loopback.Chicago.cw.net [208.172.2.62]
11 110 ms 69 ms 68 ms williams-communications-inc.Chicago.cw.net [208.172.1.130]
12 69 ms 68 ms 69 ms chcgil1wcx2-oc48.wcg.net [64.200.103.73]
13 82 ms 69 ms 68 ms chcgil1wcx2-pos.wcg.net [64.200.240.73]
14 69 ms 69 ms 68 ms atlnga6lce1-pos5-0.wcg.net [64.200.127.62]
15 68 ms 69 ms 83 ms atlnga6lce1-cuttingedge-atm.wcg.net [64.200.126.70]
16 68 ms 69 ms 55 ms 10.30.30.2
17 2788 ms 2773 ms 2733 ms cet-dv2.transit.dv2.net [209.51.130.33]
18 2747 ms 2760 ms 2788 ms 209.51.139.113


:(

a MS-dos screen shot

It is suddenly back to normal now!!! :)

Is there problems again???

Im getting no response via http to a few different servers?