North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: AT&T crap performance!
On Mon, Dec 21, 1998 at 10:29:53AM -0800, Chris Cappuccio put this into my mailbox: > Hey, I've been using AT&T's network for a while now, and I have a lot of very > poor performance issues like this for a long time. The easy answer would be > to trash AT&T but we've got a contract with them that hasn't expired yet. > Since these are network related issues, I'm wondering if anyone on NANOG has > a clue as to what is going on/the best people to approach. I've been calling > folks at AT&T for several months to get answers that amount to "we are > upgrading this link to an OC3" and even after the upgrade, the performace > still sucks. Because most of 12/8 is vulnerable as smurf amplifiers, has been for at least 2 years now, and nobody seems to give a rat's ass about fixing it, so all the skr1ptk1dd13z are using it to attack other people, thus sucking up all the bandwidth that might be available for legitmate use? PING 126.96.36.199: 56 data bytes 64 bytes from 188.8.131.52: icmp_seq=0. time=83. ms 64 bytes from 184.108.40.206: icmp_seq=0. time=84. ms 64 bytes from 220.127.116.11: icmp_seq=0. time=85. ms 64 bytes from 18.104.22.168: icmp_seq=0. time=85. ms 64 bytes from 22.214.171.124: icmp_seq=0. time=194. ms 64 bytes from 126.96.36.199: icmp_seq=0. time=329. ms 64 bytes from 188.8.131.52: icmp_seq=0. time=329. ms 64 bytes from 184.108.40.206: icmp_seq=0. time=329. ms 64 bytes from 220.127.116.11: icmp_seq=0. time=330. ms 64 bytes from 18.104.22.168: icmp_seq=0. time=351. ms 64 bytes from 22.214.171.124: icmp_seq=0. time=352. ms 64 bytes from 126.96.36.199: icmp_seq=0. time=352. ms 64 bytes from 188.8.131.52: icmp_seq=0. time=352. ms 64 bytes from 184.108.40.206: icmp_seq=0. time=461. ms 64 bytes from 220.127.116.11: icmp_seq=0. time=572. ms 64 bytes from 18.104.22.168: icmp_seq=0. time=689. ms 64 bytes from 22.214.171.124: icmp_seq=0. time=824. ms 64 bytes from 126.96.36.199: icmp_seq=0. time=934. ms 64 bytes from 188.8.131.52: icmp_seq=0. time=955. ms 64 bytes from 184.108.40.206: icmp_seq=0. time=1067. ms 64 bytes from 220.127.116.11: icmp_seq=0. time=1175. ms 64 bytes from 18.104.22.168: icmp_seq=0. time=1284. ms 64 bytes from 22.214.171.124: icmp_seq=0. time=1404. ms 64 bytes from 126.96.36.199: icmp_seq=0. time=1425. ms 64 bytes from 188.8.131.52: icmp_seq=0. time=1565. ms 64 bytes from 184.108.40.206: icmp_seq=0. time=1675. ms 64 bytes from 220.127.116.11: icmp_seq=0. time=1782. ms ^C ----18.104.22.168 PING Statistics---- 1 packets transmitted, 27 packets received, 27.00 times amplification round-trip (ms) min/avg/max = 83/706/1782 -dalvenjah -- Dalvenjah FoxFire (aka Sven Nielsen) "Sir, your wit ambles well; Founder, the DALnet IRC Network it goes easily." e-mail: [email protected] WWW: http://www.dal.net/~dalvenjah/ whois: SN90 Try DALnet! http://www.dal.net/