January 2002 - Test - lists.nanog.org

SWBell NOC contact #
by Brian Wallingford 09 Jan '02

09 Jan '02

I've checked their site as well as Jared's NOC list and any *nic and ARIN contact info to no avail. I'd appreciate a phone number if someone can provide such. We're under what appears to be an attempted DOS attack from a DSL customer of theirs. tia, brian

1 0

South Florida outage
by crimson 09 Jan '02

09 Jan '02

I'm in South Florida, on a DS3 from XO. I just experince about 10 mins ago a brief internet connectivity loss. Lasted 2-3 mins. I couldn't leave the XO network. Anyone else experince this?

1 0

RE: Canadian Outage?
by CARL.P.HIRSCH＠sargentlundy.com 09 Jan '02

09 Jan '02

Thanks Blake. I'll keep that bookmarked. Is there a central site with all providers' status pages? Dare I dream? I'm told that Bell Canada has experienced a switch failure which has taken out a good chunk of Toronto/Ontario. Hence the loop. thanks, -carl "Blake Crosby" To: <CARL.P.HIRSCH(a)sargentlundy.com>, <nanog(a)merit.edu> <dev@samurai. cc: com> Subject: RE: Canadian Outage? 01/09/02 03:12 PM You might want to check: http://netmon.canet3.net/outage/ Blake > -----Original Message----- > From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of > CARL.P.HIRSCH(a)sargentlundy.com > Sent: January 9, 2002 4:02 PM > To: nanog(a)merit.edu > Subject: Canadian Outage? > > > > Is anybody aware of any kind of outage in Canadia right now? I'm seeing > large chunks of Canada as unreachable from several different networks. > > Unfortunately, I'm not a Bellnexxia customer, or I'd take it to > the vendor. > > thanks, > -carl > > traceroute to 216.183.136.2 (216.183.136.2), 30 hops max, 38 byte packets > 1 gateway (216.36.101.177) 2.474 ms 1.643 ms 1.642 ms > 2 sdsl-64-32-208-1.dsl.chi.megapath.net (64.32.208.1) 5.711 ms 12.251 > > * > 25 * *^C > > >

1 0

Canadian Outage?
by CARL.P.HIRSCH＠sargentlundy.com 09 Jan '02

09 Jan '02

Is anybody aware of any kind of outage in Canadia right now? I'm seeing large chunks of Canada as unreachable from several different networks. Unfortunately, I'm not a Bellnexxia customer, or I'd take it to the vendor. thanks, -carl traceroute to 216.183.136.2 (216.183.136.2), 30 hops max, 38 byte packets 1 gateway (216.36.101.177) 2.474 ms 1.643 ms 1.642 ms 2 sdsl-64-32-208-1.dsl.chi.megapath.net (64.32.208.1) 5.711 ms 12.251 ms 5. 784 ms 3 216.33.81.177 (216.33.81.177) 6.650 ms 6.334 ms 6.192 ms 4 dcr03-g1-0.okbr01.exodus.net (216.33.64.17) 12.241 ms 12.454 ms 12.201 ms 5 ibr02-g4-0.okbr01.exodus.net (216.34.183.67) 5.866 ms 5.947 ms 5.541 ms 6 209.1.169.106 (209.1.169.106) 12.921 ms 12.843 ms 12.849 ms 7 core1-chicago23-pos11-0.in.bellnexxia.net (206.108.103.137) 12.854 ms 13.1 24 ms 12.842 ms 8 core4-toronto12-pos6-3.in.bellnexxia.net (206.108.103.133) 20.061 ms 23.98 1 ms 190.847 ms 9 core2-toronto12-pos2-0.in.bellnexxia.net (64.230.242.206) 19.863 ms 26.220 ms 19.672 ms 10 dis2-toronto12-pos10-1-0.in.bellnexxia.net (206.108.97.82) 26.616 ms 20.10 5 ms 26.421 ms 11 206.108.111.98 (206.108.111.98) 97.461 ms 100.695 ms 100.874 ms 12 dis2-toronto12-atm1-1-0-42.in.bellnexxia.net (206.108.111.97) 91.930 ms * 87.838 ms 13 206.108.111.98 (206.108.111.98) 128.606 ms 166.102 ms 165.326 ms 14 dis2-toronto12-atm1-1-0-42.in.bellnexxia.net (206.108.111.97) 156.424 ms 1 54.577 ms 160.717 ms 15 206.108.111.98 (206.108.111.98) 227.861 ms 232.778 ms 215.834 ms 16 dis2-toronto12-atm1-1-0-42.in.bellnexxia.net (206.108.111.97) 202.247 ms 2 17.963 ms 256.100 ms 17 206.108.111.98 (206.108.111.98) 337.063 ms 351.338 ms * 18 dis2-toronto12-atm1-1-0-42.in.bellnexxia.net (206.108.111.97) 214.777 ms 2 95.202 ms * 19 206.108.111.98 (206.108.111.98) 304.315 ms 766.205 ms 409.070 ms 20 dis2-toronto12-atm1-1-0-42.in.bellnexxia.net (206.108.111.97) 296.539 ms 2 97.997 ms 292.225 ms 21 206.108.111.98 (206.108.111.98) 320.808 ms * 450.700 ms 22 dis2-toronto12-atm1-1-0-42.in.bellnexxia.net (206.108.111.97) 468.613 ms * 421.227 ms 23 206.108.111.98 (206.108.111.98) 426.012 ms 450.852 ms 481.729 ms 24 dis2-toronto12-atm1-1-0-42.in.bellnexxia.net (206.108.111.97) 429.893 ms * * 25 * *^C

2 1

RE: Blocking Internet Gaming
by Paul Lantinga 09 Jan '02

09 Jan '02

-----Original Message----- From: Stephen Griffin [mailto:stephen.griffin@rcn.com] [snip] >What needs to be done is to balance the knee-jerk IT folks reactions >to make life as miserable as possible for the greatest number vs. >allowing some amount of employee usage, to increase satisfaction, >_increase_ productivity, and basically make it worth going into the >office. That's an excellent point Stephen. Killing employee morale can have longlasting repurcussions. I had the pleasure of experiencing a good decision of this type about 3 years ago when I worked in India. The execs decided NOT to block outbound port 80, even though it was taking up 75% of the bandwidth on a 128k link. They paid for an upgrade to 256k (SFO -> Bangalore, not cheap!) and decided not to block port 80, as the damage to employee morale would be too severe. -Paul.

1 0

Outage: North Carolina???
by Andrew Dorsett 09 Jan '02

09 Jan '02

Hey we are seeing fast busy signals when calling Mebane from Burlington and was told it's a fiber cut, however I don't think so.....Anybody have any information or know where I can locate it? Thanks, Andrew --- <zerocool(a)netpath.net> http://www.andrewsworld.net/ ICQ: 2895251 Cisco Certified Network Associate Development Assistant: Netpath/Stratonet, Inc. (http://www.netpath.net/) Email: dorsett(a)netpath.net "Learn from the mistakes of others. You won't live long enough to make all of them yourself."

1 0

arin.net offline?
by Dan Hollis 09 Jan '02

09 Jan '02

Did I miss something? whois.arin.net, www.arin.net etc.. dead -Dan -- [-] Omae no subete no kichi wa ore no mono da. [-]

8 8

ARIN Outage...
by Matt Levine 09 Jan '02

09 Jan '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Does anyone have any information the current issues with the arin ns's ? scheduled maint perhaps? Whois/website are up and functioning via the IP addys fine. Additionally, they are serving responses for MX queries, it seems only the A records are not being returned. Details below. details: > dig arin.net @a.gtld-servers.net ;; AUTHORITY SECTION: arin.net. 2D IN NS L3.NSTLD.COM. arin.net. 2D IN NS A3.NSTLD.COM. arin.net. 2D IN NS C3.NSTLD.COM. arin.net. 2D IN NS F3.NSTLD.COM. arin.net. 2D IN NS G3.NSTLD.COM. arin.net. 2D IN NS BUCHU.arin.net. arin.net. 2D IN NS ARROWROOT.arin.net. ;; ADDITIONAL SECTION: L3.NSTLD.COM. 2D IN A 192.41.162.32 A3.NSTLD.COM. 2D IN A 192.5.6.32 C3.NSTLD.COM. 2D IN A 192.26.92.32 F3.NSTLD.COM. 2D IN A 192.35.51.32 G3.NSTLD.COM. 2D IN A 192.42.93.32 BUCHU.arin.net. 2D IN A 192.100.59.110 ARROWROOT.arin.net. 2D IN A 198.133.199.110 > dig www.arin.net @198.133.199.110 ;; AUTHORITY SECTION: www.arin.net. 2M IN NS rs1.arin.net. www.arin.net. 2M IN NS rs2.arin.net. ;; ADDITIONAL SECTION: rs1.arin.net. 3H IN A 192.149.252.21 rs2.arin.net. 3H IN A 192.149.252.22 > dig www.arin.net @192.149.252.22 ; <<>> DiG 8.3 <<>> www.arin.net @192.149.252.22 ; (1 server found) ;; res options: init recurs defnam dnsrch ;; res_nsend to server 192.149.252.22: Operation timed out > dig www.arin.net @192.149.252.21 ; <<>> DiG 8.3 <<>> www.arin.net @192.149.252.21 ; (1 server found) ;; res options: init recurs defnam dnsrch ;; res_nsend to server 192.149.252.21: Operation timed out Regards, Matt - -- Matt Levine @Home: matt(a)deliver3.com @Work: matt(a)eldosales.com ICQ : 17080004 PGP : http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0D04CF "The Trouble with doing anything right the first time is that nobody appreciates how difficult it was." -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> iQA/AwUBPDv6QMp0j1NsDQTPEQLofgCfbfGph4XvDVw3DWRJvniL9DMOslwAn2cL uvanqqAXEcrcHhzBqbL+BUUT =dbf8 -----END PGP SIGNATURE-----

2 1

Does NSI's domain update web site ever work?
by John R Levine 09 Jan '02

09 Jan '02

Dunno how operational this is, but it sure is a pain in the butt. I have a .com domain that I would dearly like to remove from NSI's clutches. In a moment of poor thinking a few years ago I registered it through Worldnic, so its email address is no.valid.email(a)WORLDNIC.NET, making it impossible to transfer since there's no address for the new registrar to ask whether the transfer's OK. No problem, I still have my account number that NSI assigned me in 1999, I can log into their web site and update the email address. Except that every single fricking time I try, it says: System is temporarily unavailable. Please try back later. It's been saying this for months. It worked for about 30 seconds last month, enough to pay them $35 to keep the domain alive, but I wasn't able to get back in to change the address. In the past I'd have let it expire and reregistered it the next day, but nowadays the vultures will beat you to it. E-mail requests asking when it'll be working again are sometimes ignored, sometimes answered three days later with boilerplate telling me that I can update my info through their wonderful web site. (I think this is known in the CRM biz as "excellent" service.) So is there any hope? Do I need to get a pizza and rent a couple of movies and camp by the phone while I wait on hold or what? Regards, John Levine, johnl(a)iecc.com, Primary Perpetrator of "The Internet for Dummies", Information Superhighwayman wanna-be, http://iecc.com/johnl, Sewer Commissioner Write for PGP key, f'print = 3A 5B D0 3F D9 A0 6A A4 2D AC 1E 9E A6 36 A3 47

6 7

Re: Road Runner
by mikenoc＠mindspring.com 09 Jan '02

09 Jan '02

This one should be what you are lookin for. Here is a URL which has NOC numbers as well. Mike F. Earthlink NOC http://puck.nether.net/netops/nocs.cgi Andy Brezinsky <andy(a)mbrez.com> wrote: > Hello, Does anyone have a contact for the NOC or a dns admin of Road Runner (Wisconsin)? One of their dns servers are reporting bad data. Regards, ~Andy Brezinsky ByteHosting Internet Services

10 11