[outages] Cogent outage ???

[Mitch]

Most recent post on their status page( http://status.cogentco.com/)

*Network Status Description*

Welcome to the Cogent Communications status page. Customers located in the
New York City area may be experiencing an outage. This is currently being
investigated by the Cogent NOC. There is no Estimated time to repair. The
master case is HD5267626.

For customers hosted and provisioned through our New York hosting center at
33 Whitehall: Power is being supplied by generator and there is No
Estimated Time of Repair for commercial power to be restored to the
building. We will update our Network status page if there is any change.

On Thu, Dec 6, 2012 at 12:17 PM, Aubrey Wells <aubrey at vocalcloud.com> wrote:

> Our L2 stuff in Atlanta and Dallas looks fine, but we don't have any L3
> service from them. I also get a busy signal if I call their 877-7cogent
> number or their local DC number.
>
>  ------------------
> Aubrey Wells
> Director | Network Services
> VocalCloud
> 678.248.2637
> support at vocalcloud.com
> www.vocalcloud.com
>
>
>
> On Thu, Dec 6, 2012 at 12:12 PM, Matthew Huff <mhuff at ox.com> wrote:
>
>>  About 10 minutes ago we stopped being able to pass traffic through
>> cogent. I de-peered us from Cogent, and everything appears
>> better. When I call cogent, all I get is a busy signal (must be a major
>> outage). Anyone else seeing anything?
>>
>> ----
>> Matthew Huff             | 1 Manhattanville Rd
>> Director of Operations   | Purchase, NY 10577
>> OTA Management LLC       | Phone: 914-460-4039
>> aim: matthewbhuff        | Fax:   914-460-4139
>>
>>
>>
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
>>
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20121206/28bb682c/attachment.htm>