to service resolution, ticket closure,
or post incident review, details may evolve.
From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Randall (Randy)
Raitz via Outages
Sent: Thursday, January 11, 2018 7:46 AM
To: 'outages@outages.org' <outages@outages.org>
Subject: [outages]
We have two PRIs down in Denver. Anyone else having voice issues with Level3?
Disclaimer
The information contained in this communication from the sender is
confidential. It is intended solely for use by the recipient and others
authorized to receive it. If you are not the recipient, you are
We experienced issues with VZW customers not being able to dial our TFs today
too.
Sent from my iPhone
On Aug 17, 2017, at 11:31 PM, Samual Carman via Outages
> wrote:
On Depoe Bay Oregon the ATT Network has been up
And down through the day best
Having problems in Denver and Los Angeles reaching a Level3 resource.
Everything dies at 67.72.92.113
:\Users\randy.raitz>tracert 4.59.248.127
Tracing route to moderator-cfer.atlanta2.level3.net [4.59.248.127]
over a maximum of 30 hops:
1<1 ms 2 ms 3 ms 192.168.70.253
2 1
A buddy of mine just forwarded this story my way. It gives some insight as to
what may have triggered the events.
https://krebsonsecurity.com/2016/10/ddos-on-dyn-impacts-twitter-spotify-reddit/
-Original Message-
From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Andrew
I'm seeing Comcast cable modem issues from my house here in Denver. Details
from my account portal indicate an ETR of 7AM Denver time
Sent from my iPhone
On Oct 11, 2016, at 3:01 AM, Dave Pascoe via Outages
> wrote:
FWIW...seems like Comcast
Has anyone received anything about the outage that includes details on the
fire? So far, below is what I’ve received:
Outage Start: October 4, 2016 14:06 GMT Outage Stop: October 4, 2016 15:31 GMT
Root Cause: Calls were not present in Level 3 voice switches, impacting voice
services in
We are seeing outbound issues on both LD and local call types. Denver area
Level3 pris
Sent from my iPhone
On Oct 4, 2016, at 8:37 AM, Kevin Kastelic via Outages
> wrote:
We are also seeing it in Sussex, WI on Level3. Local calling seems to
Internap reported that Cogent had a fiber cut in the LAX market and repairs
were completed at approx. 11:25PM MDT. Internap continued to monitor their
peering connection with Cogent until 5AM when our session was brought back up.
From: Outages [mailto:outages-boun...@outages.org] On Behalf Of
We just observed similar issues with Cogent in the path as well. We’re in the
El Segundo / LAX area.
From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Silvey, David
via Outages
Sent: Monday, September 19, 2016 12:47 PM
To: 'Nick W'
Cc: outages@outages.org
Subject: Re: [outages]
This is affecting services in my data center in the El Segundo / LAX area as
well. Updates from Internap point to a fiber cut that Zayo is expecting to have
repaired by 6PM PDT.
Sent from my iPhone
On Sep 9, 2016, at 9:20 AM, jd via Outages
>
I am not seeing these issues from LAX via Cogent, Denver via Level3 or Denver
via Hurricane Electric. I am seeing some packet loss on certain hops on Level3
and Zayo's backbones, but it is not persistent through the remaining hops,
indicating some ICMP rate limiting or something.
From:
12 matches
Mail list logo