koitsu
Premium
join:2002-07-16
Mountain View, CA
2 edits | [General] SBC NorCal routers being DoS'd?
This is a new one -- never seen this before.
==> Wed Aug 3 22:15:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.801 ms 0.740 ms 0.920 ms
2 192.168.0.1 (192.168.0.1) 1.469 ms 1.412 ms 1.415 ms
3 adsl-64-171-255-254.dsl.snfc21.pacbell.net (64.171.255.254) 101.317 ms 146.064 ms 1
*87.635 ms
4 dist1-vlan50.snfc21.pbi.net (206.171.134.130) 209.954 ms 269.173 ms 250.977 ms
5 bb1-10g2-0.snfcca.sbcglobal.net (216.102.176.224) 211.704 ms 214.532 ms 150.327 ms
6 core1-p6-1.crsfca.sbcglobal.net (151.164.243.121) 216.203 ms 177.351 ms *
7 bb1-p8-0.crsfca.sbcglobal.net (151.164.243.2) 104.714 ms 121.827 ms 109.490 ms
8 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 123.766 ms 165.217 ms 143.856 ms
9 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 245.367 ms 209.666 ms 283.982 ms
10 151.164.248.222 (151.164.248.222) 243.676 ms 226.126 ms 229.653 ms
11 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 255.125 ms 170.940 ms 98.224 ms
12 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 103.812 ms 149.644 ms 191.309 ms
13 pentarou.parodius.com (64.62.145.226) 277.723 ms 336.619 ms 345.882 ms
(*) WARNING 1 long line(s) split
I figured it might have something to do with the netblock I was assigned to (i.e. some packet kid just taking out one gateway), so I continually beat on my DSL bridge until I was able to get an IP which didn't rely on 64.171.255.254.
Made no difference:
==> Wed Aug 3 22:31:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.802 ms 0.777 ms 0.728 ms
2 192.168.0.1 (192.168.0.1) 1.474 ms 1.528 ms 1.465 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 330.669 ms 234.025 ms 230
*.359 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 197.067 ms 145.332 ms 77.752 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 39.952 ms 31.246 ms 26.827 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 39.705 ms 10.042 ms 10.345 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 13.838 ms 13.803 ms 10.585 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 11.722 ms 10.185 ms 9.586 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 11.595 ms 15.010 ms 12.336 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 17.717 ms 16.306 ms 12.086 ms
11 151.164.248.222 (151.164.248.222) 14.968 ms 11.372 ms 12.342 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 12.714 ms 12.424 ms 13.334 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 15.970 ms 18.544 ms 13.711 ms
14 pentarou.parodius.com (64.62.145.226) 20.989 ms 36.815 ms 61.320 ms
(*) WARNING 1 long line(s) split
This started at approximately 2110 (9:10pm) PDT, and has gradually gotten worse and worse as the night went on.
I assure you everything on my local network is *just fine* (i.e. nothing pwned, yadda yadda). I've run tcpdump numerous times on my own LAN gateway to ensure this, and things look how they should be.
Also, this is *NOT* ICMP prioritisation -- I can "feel the lag" across non-local SSH sessions, and general browsing is slow as sh**:
PING 4.2.2.1 (4.2.2.1): 56 data bytes
64 bytes from 4.2.2.1: icmp_seq=0 ttl=245 time=191.009 ms
64 bytes from 4.2.2.1: icmp_seq=1 ttl=245 time=364.751 ms
64 bytes from 4.2.2.1: icmp_seq=2 ttl=245 time=413.839 ms
64 bytes from 4.2.2.1: icmp_seq=3 ttl=245 time=423.696 ms
64 bytes from 4.2.2.1: icmp_seq=4 ttl=245 time=360.715 ms
64 bytes from 4.2.2.1: icmp_seq=5 ttl=245 time=198.886 ms
64 bytes from 4.2.2.1: icmp_seq=6 ttl=245 time=30.978 ms
64 bytes from 4.2.2.1: icmp_seq=7 ttl=245 time=13.841 ms
64 bytes from 4.2.2.1: icmp_seq=8 ttl=245 time=141.276 ms
64 bytes from 4.2.2.1: icmp_seq=9 ttl=245 time=145.085 ms
64 bytes from 4.2.2.1: icmp_seq=10 ttl=245 time=113.624 ms
64 bytes from 4.2.2.1: icmp_seq=11 ttl=245 time=151.103 ms
64 bytes from 4.2.2.1: icmp_seq=12 ttl=245 time=262.901 ms
64 bytes from 4.2.2.1: icmp_seq=13 ttl=245 time=353.958 ms
64 bytes from 4.2.2.1: icmp_seq=14 ttl=245 time=202.908 ms
64 bytes from 4.2.2.1: icmp_seq=15 ttl=245 time=236.488 ms
64 bytes from 4.2.2.1: icmp_seq=16 ttl=245 time=36.206 ms
64 bytes from 4.2.2.1: icmp_seq=17 ttl=245 time=144.020 ms
64 bytes from 4.2.2.1: icmp_seq=18 ttl=245 time=134.260 ms
64 bytes from 4.2.2.1: icmp_seq=19 ttl=245 time=54.908 ms
--
Making life hard for others since 1977. In memory of 2005... |
|
koitsu
Premium
join:2002-07-16
Mountain View, CA
1 edit | Here's some additional statistics-over-time information. Be sure to note the Worst and Avg times.
Host Loss% Snt Last Avg Best Wrst StDev
1. gw.home.lan 0.0% 145 0.7 0.7 0.6 1.1 0.1
2. 192.168.0.1 0.0% 145 1.0 1.0 0.9 1.8 0.1
3. adsl-64-169-95-254.dsl.snfc21.pacbell.net 0.0% 145 331.8 83.2 9.6 378.0 79.0
4. dist2-vlan60.snfc21.pbi.net 0.7% 145 386.1 79.7 10.0 386.1 74.6
5. bb2-10g2-0.snfcca.sbcglobal.net 0.0% 145 374.9 111.9 10.2 2871. 247.5
6. bb1-p4-0.snfcca.sbcglobal.net 0.0% 145 362.4 91.6 10.1 396.0 86.5
7. core1-p6-0.crsfca.sbcglobal.net 0.0% 144 340.1 97.7 10.3 380.0 83.7
8. bb1-p8-0.crsfca.sbcglobal.net 0.7% 144 342.8 96.5 10.5 438.3 86.6
9. ex1-p3-0.eqsjca.sbcglobal.net 0.7% 144 376.5 97.2 11.7 376.5 79.5
10. ge-6-13.car4.SanJose1.Level3.net 0.7% 144 380.7 93.5 11.3 386.6 79.9
11. ge-10-1.core1.SanJose1.Level3.net 0.0% 144 394.3 89.3 12.2 414.6 81.8
12. vnsc-pri.sys.gtei.net 0.7% 144 366.4 100.0 12.5 2085. 185.2
Host Loss% Snt Last Avg Best Wrst StDev
1. gw.home.lan 0.0% 700 1.0 0.6 0.6 1.7 0.1
2. 192.168.0.1 0.0% 700 1.0 0.9 0.9 1.7 0.1
3. adsl-64-169-95-254.dsl.snfc21.pacbell.net 0.1% 699 160.0 150.5 9.6 809.1 171.3
4. dist2-vlan60.snfc21.pbi.net 0.1% 699 169.4 150.5 9.7 833.1 170.9
5. bb2-10g2-0.snfcca.sbcglobal.net 0.1% 699 211.0 161.3 10.1 816.9 176.4
6. bb1-p4-0.snfcca.sbcglobal.net 0.3% 699 193.8 163.3 9.8 884.3 173.0
7. core1-p6-0.crsfca.sbcglobal.net 0.3% 699 176.5 169.6 10.2 796.1 174.4
8. bb1-p8-0.crsfca.sbcglobal.net 0.3% 699 178.5 160.9 10.2 816.6 172.8
9. ex1-p3-0.eqsjca.sbcglobal.net 0.1% 699 190.1 164.4 11.5 925.7 175.2
10. ge-6-13.car4.SanJose1.Level3.net 0.3% 699 193.0 159.0 11.3 811.7 170.6
11. ge-10-1.core1.SanJose1.Level3.net 0.1% 699 189.8 155.4 11.6 785.7 169.7
12. vnsc-pri.sys.gtei.net 0.1% 699 148.0 154.6 12.3 770.4 170.4
--
Making life hard for others since 1977. In memory of 2005... |
|
Hiryuu
join:2003-01-17
San Jose, CA
| reply to koitsu
Having the same exact problem with the router hop being anywhere from 30-900ms and killing my dl speed. I've done speed tests and upload seems to be running at the right speed still.
Here, I'll tracert the same site as you:
Tracing route to pentarou.parodius.com [64.62.145.226]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms home [192.168.1.254]
2 394 ms 376 ms 287 ms adsl-63-202-183-254.dsl.snfc21.pacbell.net [63.2
02.183.254]
3 255 ms 226 ms 244 ms dist1-vlan50.snfc21.pbi.net [206.171.134.130]
4 316 ms 364 ms 421 ms bb1-10g2-0.snfcca.sbcglobal.net [216.102.176.224
]
5 203 ms 127 ms 110 ms core1-p14-0.crsfca.sbcglobal.net [151.164.243.12
5]
6 197 ms 226 ms 218 ms bb1-p8-0.crsfca.sbcglobal.net [151.164.243.2]
7 234 ms 281 ms 329 ms ex1-p14-0.eqsjca.sbcglobal.net [151.164.41.10]
8 228 ms 360 ms 327 ms ex2-p10-0.eqsjca.sbcglobal.net [151.164.191.67]
9 433 ms 356 ms 380 ms 151.164.248.222
10 659 ms 727 ms 624 ms pos1-1.gsr12416.fmt.he.net [66.220.10.125]
11 392 ms 390 ms 470 ms pos3-0.gsr12012.fmt.he.net [66.220.3.105]
12 506 ms 506 ms 524 ms pentarou.parodius.com [64.62.145.226]
Trace complete. |
|
koitsu
Premium
join:2002-07-16
Mountain View, CA
| Hiryuu,
The problem definitely isn't our equipment or our networks. It's something on SBCs end, and since it's gateway-related, it doesn't matter what destination / endpoint you're trying to reach (4.2.2.1, my co-lo, Google, etc.).
I'm seeing latencies at this point of OVER 1 full second, which means the problem is getting substantially worse:
==> Wed Aug 3 23:23:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.742 ms 1.020 ms 0.660 ms
2 192.168.0.1 (192.168.0.1) 1.476 ms 1.422 ms 1.417 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 462.348 ms 497.771 ms 567
*.588 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 659.000 ms 619.330 ms 738.119 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 743.600 ms 754.969 ms 749.234 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 679.980 ms 824.312 ms 945.756 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 976.094 ms 939.375 ms 867.026 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 1017.201 ms 1079.040 ms 1010.204 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 1074.534 ms 1289.427 ms 1302.793 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 975.593 ms 748.956 ms 796.724 ms
11 151.164.248.222 (151.164.248.222) 1028.060 ms 902.717 ms 1017.700 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 883.521 ms 801.198 ms 742.709 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 719.914 ms 723.124 ms 785.230 ms
14 pentarou.parodius.com (64.62.145.226) 923.085 ms 1034.366 ms 948.461 ms
(*) WARNING 1 long line(s) split
If this is a Redback equipment problem, is there some particular reason the interfaces are *NOT* being monitored 24x7? I refuse to believe this issue could go on for 2.5 hours without someone in a NOC noticing.
This is very, very disappointing...
--
Making life hard for others since 1977. In memory of 2005... |
|
TOTC
I only exist to make you cry
Premium
join:2001-05-16
Van Nuys, CA | reply to koitsu
comcast norcal customers are being affected too...
»[Connectivity] NorCal high pings, slow speeds
--
My name is the one they call and I approve this message. |
|
koitsu
Premium
join:2002-07-16
Mountain View, CA
| Uh, what? Comcast's network is completely unrelated to SBCs network. I can't corrolate these two issues right now, sadly. But if they *ARE* related, then I'm definitely going to go with the opinion that this is DoS/DDoS related. Packet kids probably wanted some IRC channel somewhere and decided to take out numerous people...
In other (and more important) news:
This issue I've mentioned has been completely circumvented at 23:50. I don't know why / who did it / what's going on, but the issue is gone.
--
Making life hard for others since 1977. In memory of 2005... |
|
a2nxtcrav3r
Pokes People With Stick
Premium
join:2003-07-13
San Jose, CA
 ·DSL EXTREME
| reply to koitsu
im from san jose... and or norcal of course and im getting ridiculously slow speeds, 56k is faster than my dsl right now.
»/quality/nil/1808919
thats my line test... WHOA MAMA THATS BAD
--
i need money |
|
koitsu
Premium
join:2002-07-16
Mountain View, CA
1 edit | reply to koitsu
At exactly 2101 tonight, this issue has resurfaced. Here's a traceroute from 2100 and 2101:
==> Thu Aug 4 21:00:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 1.740 ms 1.687 ms 1.701 ms
2 192.168.0.1 (192.168.0.1) 3.042 ms 1.415 ms 1.458 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 12.095 ms 14.648 ms 12.95
*6 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 9.848 ms 9.432 ms 9.584 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 157.418 ms 210.401 ms 42.943 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 9.464 ms 9.934 ms 11.828 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 10.720 ms 10.672 ms 10.588 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 22.589 ms 192.835 ms 142.900 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 10.944 ms 11.909 ms 11.712 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 11.346 ms 11.683 ms 12.212 ms
11 151.164.248.222 (151.164.248.222) 11.844 ms 12.475 ms 28.830 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 11.969 ms 12.173 ms 12.211 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 13.097 ms 12.286 ms 12.336 ms
14 pentarou.parodius.com (64.62.145.226) 13.220 ms 12.259 ms 12.351 ms
==> Thu Aug 4 21:01:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.788 ms 0.668 ms 0.727 ms
2 192.168.0.1 (192.168.0.1) 1.477 ms 1.416 ms 1.468 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 375.424 ms 372.266 ms 423
*.937 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 376.286 ms 377.152 ms 370.999 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 321.023 ms 357.154 ms 426.241 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 344.392 ms 332.820 ms 289.277 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 263.821 ms 341.652 ms 497.202 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 655.598 ms 411.884 ms 406.222 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 406.719 ms 333.317 ms 293.895 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 325.543 ms 390.398 ms 495.659 ms
11 151.164.248.222 (151.164.248.222) 552.925 ms 514.264 ms 607.487 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 623.705 ms 676.835 ms 709.054 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 659.187 ms 680.490 ms 600.616 ms
14 pentarou.parodius.com (64.62.145.226) 551.870 ms 563.047 ms 669.707 ms
(*) WARNING 1 long line(s) split
And present:
==> Thu Aug 4 22:13:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.733 ms 0.672 ms 0.729 ms
2 192.168.0.1 (192.168.0.1) 1.473 ms 1.539 ms 1.466 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 839.321 ms 772.466 ms 874
*.741 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 917.458 ms 907.734 ms 1022.146 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 963.052 ms 920.585 ms 849.381 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 950.186 ms 699.766 ms 692.991 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 784.403 ms 734.757 ms 763.185 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 737.832 ms 932.606 ms 808.534 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 789.916 ms 849.903 ms 788.077 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 938.816 ms 1061.277 ms 885.594 ms
11 151.164.248.222 (151.164.248.222) 895.233 ms 909.315 ms 1002.149 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 833.513 ms 871.594 ms 727.847 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 666.361 ms 726.995 ms 659.630 ms
14 pentarou.parodius.com (64.62.145.226) 749.059 ms 914.877 ms 948.688 ms
(*) WARNING 1 long line(s) split
--
Making life hard for others since 1977. In memory of 2005... |
|
koitsu
Premium
join:2002-07-16
Mountain View, CA
| reply to koitsu
And, just like last night, this issue has cleared up at approximately midnight.
==> Fri Aug 5 00:09:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.763 ms 0.756 ms 0.670 ms
2 192.168.0.1 (192.168.0.1) 1.468 ms 1.417 ms 1.415 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 471.603 ms 534.380 ms 446
*.752 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 416.446 ms 427.425 ms 367.183 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 283.894 ms 222.661 ms 116.462 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 44.880 ms 12.187 ms 12.523 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 10.587 ms 10.068 ms 10.156 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 10.711 ms 26.566 ms 10.029 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 11.067 ms 12.298 ms 11.282 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 11.335 ms 11.318 ms 12.310 ms
11 151.164.248.222 (151.164.248.222) 11.488 ms 13.116 ms 11.655 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 12.205 ms 12.548 ms 13.899 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 13.831 ms 12.033 ms 12.033 ms
14 pentarou.parodius.com (64.62.145.226) 11.849 ms 12.160 ms 12.419 ms
==> Fri Aug 5 00:10:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 1.004 ms 0.756 ms 0.674 ms
2 192.168.0.1 (192.168.0.1) 1.473 ms 1.397 ms 1.414 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 27.338 ms 19.800 ms 19.40
*3 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 24.191 ms 28.489 ms 29.275 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 19.569 ms 43.520 ms 35.886 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 43.561 ms 41.670 ms 9.884 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 10.088 ms 10.686 ms 11.532 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 12.212 ms 14.251 ms 14.344 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 15.337 ms 11.308 ms 15.658 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 148.514 ms 161.602 ms 170.328 ms
11 151.164.248.222 (151.164.248.222) 35.750 ms 34.458 ms 46.513 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 41.195 ms 36.638 ms 33.634 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 32.571 ms 33.642 ms 41.138 ms
14 pentarou.parodius.com (64.62.145.226) 43.441 ms 57.294 ms 41.527 ms
==> Fri Aug 5 00:11:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 1.602 ms 1.794 ms 1.318 ms
2 192.168.0.1 (192.168.0.1) 2.882 ms 1.423 ms 1.412 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 9.718 ms 10.031 ms 9.901
*ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 9.529 ms 12.283 ms 17.156 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 10.578 ms 9.055 ms 10.525 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 9.463 ms 11.323 ms 10.285 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 10.339 ms 11.331 ms 10.030 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 14.082 ms 24.428 ms 41.269 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 64.434 ms 60.302 ms 43.505 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 38.443 ms 29.807 ms 11.159 ms
11 151.164.248.222 (151.164.248.222) 10.935 ms 11.880 ms 11.789 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 13.040 ms 12.540 ms 12.911 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 12.095 ms 12.417 ms 12.026 ms
14 pentarou.parodius.com (64.62.145.226) 12.212 ms 12.319 ms 12.053 ms
(*) WARNING 3 long line(s) split
This is, sadly, looking to be maintenance-related. At this point, and I apologise for sounding crass, I really don't care; this is unacceptable. At a BARE MINIMUM, we -- customers -- need to know how much longer this is going to last, and also, what exactly is being done on the gateways (my guess is the Redbacks) to induce this issue.
--
Making life hard for others since 1977. In memory of 2005... |
|
nwrickert
sand groper
Premium,MVM
join:2004-09-04
Geneva, IL
 ·AT&T U-Verse
·AT&T Midwest
| As a safety check, I suggest a virus scan of your computer. When it is next bad, look at the activity light of your modem.
It is possible that your computer has been trojanized, and the infection is filling your upstream pipe. You need to eliminate that possibility before you can be sure that it is a problem at the reback. |
|
koitsu
Premium
join:2002-07-16
Mountain View, CA
| I guess you missed the traceroute from another SBC customer who confirmed the same problem. Should we both scan for viruses and watch der blinkenlights on our "modems"?
--
Making life hard for others since 1977. In memory of 2005... |
|
Defcon888
Premium
join:2003-07-22
San Bruno, CA
·AT&T Yahoo
·DSL EXTREME
| reply to nwrickert
said by nwrickert  :As a safety check, I suggest a virus scan of your computer. When it is next bad, look at the activity light of your modem. It is possible that your computer has been trojanized, and the infection is filling your upstream pipe. I've had a similar problem to koitsu, at least in the symptoms (not as severe though), but was way in the past. It was believed (supposedly) to be a problem in the rb, then in the co. (I think, if I remember correctly  )
--
defcon888@gmail.com
.i use sbc internet services
.ppl who call ie a pos are usually too dumb to know how to lock it down =)
|
|
machater
join:2003-04-30
Turlock, CA
| reply to koitsu
I have been working with Sprint (our backbone provider) and it looks like a fiber issue with SBC.
From my MNS logs, it looks like the on call SBC technician ended his shift last night and just left. After that the shift supervisor called everyone on his list and no one responded. This was between 3-6 AM PDT. By 6 am a technician was finally out to look into the Fiber issue and initiate a repair.
This all started yesterday afternoon as a possible DS3 outage.
the moral? You don't go home until the work is done SBC  |
|
nwrickert
sand groper
Premium,MVM
join:2004-09-04
Geneva, IL
·AT&T U-Verse
·AT&T Midwest
| reply to koitsu
said by koitsu :I guess you missed the traceroute from another SBC customer who confirmed the same problem. Should we both scan for viruses and watch der blinkenlights on our "modems"? I indeed saw that.
Still, it is always a good cross check. It doesn't take much effort to look at the blinking lights.
The high first hop ping could be due to several things. Your upstream pipe being full due to other traffic is one of them. A DOS against the redback is another. There could also be a problem on the non-visible ATM network that connects the DSLAM to the redback. A noisy line is also a possibility, although you would probably lose sync in that case. |
|
koitsu
Premium
join:2002-07-16
Mountain View, CA
| reply to koitsu
Issue has re-appeared again, this time starting at a little after 2200, and ending literally as I began typing this up:
==> Fri Aug 5 22:09:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.792 ms 0.669 ms 0.728 ms
2 192.168.0.1 (192.168.0.1) 1.476 ms 1.495 ms 1.460 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 11.224 ms 12.445 ms 9.710
* ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 10.346 ms 11.676 ms 13.211 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 11.843 ms 10.668 ms 13.710 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 12.353 ms 10.422 ms 12.211 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 10.845 ms 10.689 ms 10.962 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 9.971 ms 10.067 ms 10.587 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 12.097 ms 11.303 ms 11.085 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 12.596 ms 11.687 ms 11.962 ms
11 151.164.248.222 (151.164.248.222) 19.712 ms 17.609 ms 19.956 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 23.616 ms 18.463 ms 20.079 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 16.218 ms 13.668 ms 16.454 ms
14 pentarou.parodius.com (64.62.145.226) 17.968 ms 23.749 ms 24.721 ms
==> Fri Aug 5 22:10:01 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.787 ms 0.788 ms 0.725 ms
2 192.168.0.1 (192.168.0.1) 1.477 ms 1.530 ms 1.463 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 79.187 ms 54.299 ms 89.66
*5 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 58.318 ms 59.140 ms 53.687 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 52.977 ms 35.925 ms 36.693 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 25.087 ms 32.048 ms 22.703 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 265.589 ms 222.039 ms 231.542 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 20.830 ms 37.526 ms 52.719 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 51.391 ms 30.275 ms 23.204 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 12.969 ms 11.691 ms 11.960 ms
11 151.164.248.222 (151.164.248.222) 13.842 ms 16.116 ms 17.957 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 19.217 ms 22.163 ms 12.336 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 12.467 ms 12.414 ms 15.718 ms
14 pentarou.parodius.com (64.62.145.226) 14.077 ms 19.243 ms 14.349 ms
==> Fri Aug 5 22:11:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 1.806 ms 1.713 ms 1.087 ms
2 192.168.0.1 (192.168.0.1) 2.360 ms 2.528 ms 1.481 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 203.000 ms 154.794 ms 139
*.645 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 185.227 ms 117.588 ms 101.905 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 107.666 ms 197.186 ms 150.591 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 127.687 ms 117.041 ms 123.135 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 131.522 ms 249.910 ms 227.355 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 168.964 ms 127.567 ms 169.606 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 127.529 ms 157.897 ms 107.899 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 144.547 ms 103.303 ms 77.081 ms
11 151.164.248.222 (151.164.248.222) 59.770 ms 48.537 ms 50.563 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 286.064 ms 107.159 ms 100.651 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 80.328 ms 62.808 ms 47.937 ms
14 pentarou.parodius.com (64.62.145.226) 75.431 ms 80.233 ms 71.031 ms
...
==> Fri Aug 5 23:12:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.792 ms 0.666 ms 0.727 ms
2 192.168.0.1 (192.168.0.1) 1.475 ms 1.411 ms 1.465 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 202.749 ms 178.888 ms 188
*.601 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 252.856 ms 235.236 ms 260.655 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 212.579 ms 239.792 ms 225.357 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 197.065 ms 217.296 ms 267.304 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 198.512 ms 199.499 ms 178.958 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 171.854 ms 223.518 ms 237.955 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 202.744 ms 182.761 ms 225.434 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 242.080 ms 345.972 ms 353.593 ms
11 151.164.248.222 (151.164.248.222) 325.138 ms 284.183 ms 319.372 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 271.908 ms 297.736 ms 304.773 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 288.873 ms 342.190 ms 387.249 ms
14 pentarou.parodius.com (64.62.145.226) 358.707 ms 274.619 ms 228.318 ms
==> Fri Aug 5 23:13:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.740 ms 0.671 ms 0.728 ms
2 192.168.0.1 (192.168.0.1) 1.476 ms 1.416 ms 1.464 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 9.849 ms 9.668 ms 9.587 m
*s
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 9.096 ms 9.680 ms 10.337 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 61.070 ms 199.209 ms 200.496 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 9.670 ms 9.439 ms 10.097 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 10.328 ms 10.421 ms 10.206 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 9.595 ms 10.884 ms 10.833 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 11.095 ms 11.316 ms 11.336 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 11.096 ms 11.821 ms 12.337 ms
11 151.164.248.222 (151.164.248.222) 12.092 ms 11.868 ms 12.077 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 119.035 ms 137.689 ms 15.204 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 12.884 ms 12.710 ms 12.337 ms
14 pentarou.parodius.com (64.62.145.226) 13.219 ms 13.005 ms 11.975 ms
(*) WARNING 5 long line(s) split
--
Making life hard for others since 1977. In memory of 2005... |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to machater
said by machater :I have been working with Sprint (our backbone provider) and it looks like a fiber issue with SBC. From my MNS logs, it looks like the on call SBC technician ended his shift last night and just left. After that the shift supervisor called everyone on his list and no one responded. This was between 3-6 AM PDT. By 6 am a technician was finally out to look into the Fiber issue and initiate a repair. This all started yesterday afternoon as a possible DS3 outage. the moral? You don't go home until the work is done SBC Well, SBC does. I had a problem with a voice line; hard failure between about 2230 and 0630. Alas, they won't roll a truck earlier than 0700, nor do they stay out past 1900, or so. Period. No overtime pay. Period. So we, the customers, suffer.
--
Norman
~A deam, dream, no dream
~Voices of the night go across the forest
~A dream, dream, no dream
~Good night my good child |
|
jwillard72
@pacbell.n
| I've been having similar latency problems, for two nights in a row. Both nights the problems started around 9pm PST and ended around midnight PST. I play an online game so it was easy for me to tell when the issues started. When doing download speed tests they're all over the map during this time. But most have been coming in UNDER 100kbps, when I normally score above 1mbps using the same tests.
When looking at the activity light on the modem, it's as if there's a pause in the download stream. The light will quickly blink then pause and do nothing for a bit, then blink again.
Anyways it's been very frustrating. |
|
Hiryuu
join:2003-01-17
San Jose, CA | reply to koitsu
Problem is back again, once again noticed it starting around 10 PST. |
|
koitsu
Premium
join:2002-07-16
Mountain View, CA
2 edits | reply to koitsu
Agree with Hiryuu, problem has definitely resurfaced. Looks like the start time was shortly before 2100 (9pm) PDT.
==> Mon Aug 8 20:42:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.900 ms 0.671 ms 0.729 ms
2 192.168.0.1 (192.168.0.1) 1.474 ms 1.406 ms 1.466 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 11.347 ms 15.047 ms 11.58
*3 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 9.346 ms 9.708 ms 9.796 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 39.829 ms 207.271 ms 25.564 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 11.720 ms 11.175 ms 9.337 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 10.597 ms 10.448 ms 11.243 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 93.121 ms 212.905 ms 178.623 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 16.193 ms 11.291 ms 12.335 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 15.719 ms 16.308 ms 18.458 ms
11 151.164.248.222 (151.164.248.222) 18.216 ms 12.227 ms 11.962 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 120.310 ms 224.726 ms 24.070 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 11.718 ms 14.290 ms 12.824 ms
14 pentarou.parodius.com (64.62.145.226) 12.845 ms 12.378 ms 12.599 ms
==> Mon Aug 8 20:43:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.832 ms 0.668 ms 0.729 ms
2 192.168.0.1 (192.168.0.1) 1.476 ms 1.412 ms 1.466 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 282.603 ms 202.235 ms 251
*.690 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 223.485 ms 181.642 ms 164.269 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 280.520 ms 172.904 ms 208.360 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 148.351 ms 148.970 ms 165.579 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 177.245 ms 186.679 ms 148.882 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 180.718 ms 230.163 ms 237.668 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 173.999 ms 152.692 ms 146.758 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 169.603 ms 184.698 ms 216.800 ms
11 151.164.248.222 (151.164.248.222) 254.211 ms 243.560 ms 304.170 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 288.909 ms 177.390 ms 168.007 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 162.600 ms 206.794 ms 211.305 ms
14 pentarou.parodius.com (64.62.145.226) 169.247 ms 146.198 ms 155.964 ms
(*) WARNING 2 long line(s) split
And as of present:
==> Mon Aug 8 23:24:00 PDT 2005
traceroute to pentarou.parodius.com (64.62.145.226), 22 hops max, 40 byte packets
1 gw (192.168.1.254) 0.781 ms 0.696 ms 0.727 ms
2 192.168.0.1 (192.168.0.1) 1.600 ms 1.413 ms 1.465 ms
3 adsl-64-169-95-254.dsl.snfc21.pacbell.net (64.169.95.254) 153.018 ms 94.853 ms 92.5
*35 ms
4 dist2-vlan60.snfc21.pbi.net (216.102.187.131) 93.176 ms 131.335 ms 131.132 ms
5 bb2-10g2-0.snfcca.sbcglobal.net (216.102.176.226) 131.524 ms 85.249 ms 89.919 ms
6 bb1-p4-0.snfcca.sbcglobal.net (151.164.190.189) 78.259 ms 63.743 ms 47.310 ms
7 core1-p14-1.crsfca.sbcglobal.net (151.164.242.65) 73.684 ms 66.786 ms 86.533 ms
8 bb1-p1-0.crsfca.sbcglobal.net (151.164.240.134) 84.664 ms 78.150 ms 76.574 ms
9 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 99.216 ms 87.035 ms 89.144 ms
10 ex2-p2-0.eqsjca.sbcglobal.net (151.164.191.202) 249.607 ms 240.984 ms 213.578 ms
11 151.164.248.222 (151.164.248.222) 95.288 ms 142.006 ms 204.729 ms
12 pos1-1.gsr12416.fmt.he.net (66.220.10.125) 214.431 ms 250.126 ms 210.861 ms
13 pos10-0.gsr12012.fmt.he.net (66.220.20.138) 164.585 ms 168.035 ms 115.861 ms
14 pentarou.parodius.com (64.62.145.226) 100.040 ms 85.083 ms 62.313 ms
(*) WARNING 1 long line(s) split
--
Making life hard for others since 1977. In memory of 2005... |
|
sragle
join:2005-08-08
San Jose, CA
 ·Vitelity VOIP
·AT&T U-Verse
 ·Comcast
|
I have the same problem started around 9pm and ended at 12:30am.....
This happen to me Friday, Saturday and Sunday. I called SBC open many tickets and they said because its my Computer, or my Modem, they just want to point the finger at me with out looking at their own equipment.... and man this night i was getting down to 28k down and 312k up!? my upload is way faster then my download, i am hanging off of dist1-vlan60.snfc21.pbi.net
in the 95132 zip. I wonder if SBC is selling more bandwidth then they can provide. |
|
