800-number outage?

Does anyone know about this outage?
  Seems like every 800-type number in the country is out right
now...is it a network problem somewhere?

Ralph M. Los
Asst. Vice-President, Internet Systems and Security
EnvestnetPMC
rlos@envestnet.com
(312) 827-3945 (direct)
(312) 296-9003 (wireless w/voicemail)
* If you haven't been hacked, you don't know where your vulnerabilities lie*

"Los, Ralph" wrote:

Does anyone know about this outage?
        Seems like every 800-type number in the country is out right
now...is it a network problem somewhere?

Ralph M. Los
Asst. Vice-President, Internet Systems and Security
EnvestnetPMC
rlos@envestnet.com
(312) 827-3945 (direct)
(312) 296-9003 (wireless w/voicemail)
* If you haven't been hacked, you don't know where your vulnerabilities lie*

Not for me from Verizon country.

Every one I tried worked.

"Los, Ralph" wrote:

Does anyone know about this outage?
        Seems like every 800-type number in the country is out right
now...is it a network problem somewhere?

This seems to be an Ameritech 5-state problem with the translation
database for all toll-free numbers. I'm in Illinois and its affecting
us and neighboring states. Sorry that's all I've heard.

John

Date: Wed, 3 Oct 2001 10:18:24 -0500
From: "Los, Ralph" <rlos@EnvestNet.com>

Does anyone know about this outage?
  Seems like every 800-type number in the country is out right
now...is it a network problem somewhere?

I just tried two of ours and another one... no problems. It
might help to specify your calling CLLI, or at least NPA/NXX.

Eddy

I'm hearing reports that Ameritech is having issues. Apparently their
SCP's are in trouble.

I've got a trouble ticket open with Ameritech on it...no ETA yet.

-Eric

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We are having trouble with our 800 numbers, reportedly due to a
problem at Ameritech.

Sorry for the lack of detail other than to confirm trouble...

- -----Original Message-----

This isn't really a NANOG issue but it does affect most of us so...

It looks to me like there is a switch problem with some of the long haul carriers. The interesting thing is that most of the numbers that are unreachable from LAN lines, are accessible from cell phones. It looks more like a switch software issue than a cable cut or other physical outage.

Date: Wed, 3 Oct 2001 08:26:51 -0700
From: BillT@Mahagonny.com

This isn't really a NANOG issue but it does affect most of us so...

[ snip ]

Hmmmm.... Nathan's list would probably be a good choice:

http://www.robotics.net/clec/cleclist.htm

Disclaimer: I have not connection with Nathan. He doesn't even
know who I am.

Eddy

This isn't really a NANOG issue but it does affect most of us so...

Only in the sense you should always have a non-1-800 number for your
NOC, and for NOC to NOC communications. Toll free numbers require
more technology to work than a direct-dial number.

It looks to me like there is a switch problem with some of the long
haul carriers. The interesting thing is that most of the numbers that
are unreachable from LAN lines, are accessible from cell phones. It
looks more like a switch software issue than a cable cut or other
physical outage.

Generally wireless and cell providers use Illuminet for their SS7
switching, while ILECs use an internal network. So it is possible for
one to work, and the other one to break.

I couldn't reach Verizon's business service center 800 number from
Verizon country this morning. Working now tho.

As of 12:35 PM CDT, Ameritech reported it was up and operational. (or at
least that is what they told me)

Still not sure why it died, but I have lots of people who want to know...

-Eric

Probably the same problem here in Ohio - "call can not be completed" from
the PBX, fast busy from the cell.