Dovid Bender via Outages | 31 Oct 04:38 2014

Re: [outages] Peerless down

They seem to be back up. It seems they were down for about an hour.

Regards,

Dovid

-----Original Message-----
From: "Dovid Bender" <dovid@...>
Date: Fri, 31 Oct 2014 03:15:08 
To: <outages@...>
Reply-To: dovid@...
Subject: Peerless down

Peerless voice services are down. They are aware of the issue and currently there is no ETA.

Regards,

Dovid
Dovid Bender via Outages | 31 Oct 04:15 2014

[outages] Peerless down

Peerless voice services are down. They are aware of the issue and currently there is no ETA.

Regards,

Dovid

Re: [outages] 3, 2, 1 who is going to be the first to ask if fb is down

It's not down, I got a fine blank page no problem.

brandon
Chaim Rieger via Outages | 29 Oct 00:19 2014

[outages] 3,2,1 who is going to be the first to ask if fb is down


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
<div>
<br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</div>
Collin Rose | 28 Oct 20:09 2014
Picon

OT: Verizon Business AS 701

Anybody have a sales contact for VZ Business AS 701?   


Collin Rose
DayStarr Communications
P: (989) 720-1000
F: (989) 720-6060
<div><div dir="ltr">Anybody have a sales contact for VZ Business AS 701? &nbsp;&nbsp;<div><br></div>
<div>
<br clear="all"><div>Collin Rose<br>DayStarr Communications<br>P: (989) 720-1000<br>F: (989) 720-6060</div>
</div>
</div></div>
Tim Glen via Outages | 28 Oct 20:03 2014

[outages] Level 3 Network Event Affecting Voice Service in Phila

We have voice and data with L3, this is affecting our voice service with but not our data…

 

Network Event Ticket ID  8525393

 

10/28/2014 6:50 PM GMT

The Transport NOC reports that a card failure in Philadelphia, PA is affecting protected services. Tier III is actively engaged and is investigating at this time.

 

 

<div><div class="WordSection1">
<p class="MsoNormal"><span>We have voice and data with L3, this is affecting our voice service with but not our data&hellip;<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Network Event Ticket ID&nbsp; 8525393<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>10/28/2014 6:50 PM GMT<p></p></span></p>
<p class="MsoNormal"><span>The Transport NOC reports that a card failure in Philadelphia, PA is affecting protected services. Tier III is actively engaged and is investigating at this time.<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
</div></div>
Jim Popovitch | 28 Oct 02:47 2014
Picon

Re: Mixed Case of.mil MX Servers?

On Mon, Oct 27, 2014 at 7:58 PM, Jeremy Chadwick via Outages
<outages@...> wrote:
> Is it possible for someone to provide output from something like
> "dig mx navy.mil. +trace" ?

Here's some relevant bits of interest from USA and EU queries in which
I see 3 different cases for the word "navy"  (nAVy, naVy, nAvy) (also:
.MIL and .miL).  What's up with the case sensitivity?

Atlanta:
MX 20 sec-jeemsg.eemsg.mail.MIl. from server 199.252.180.234 in 30 ms.
MX 30 mx14.nmci.nAVy.MIl. from server 199.252.180.234 in 30 ms.
MX 30 mx13.nmci.nAVy.MIl. from server 199.252.180.234 in 30 ms.
MX 10 pri-jeemsg.eemsg.mail.MIl. from server 199.252.180.234 in 30 ms.
MX 30 mx15.nmci.nAVy.MIl. from server 199.252.180.234 in 30 ms.

Seattle:
MX 10 pri-jeemsg.eemsg.mail.miL. from server 199.252.155.234 in 80 ms.
MX 20 sec-jeemsg.eemsg.mail.miL. from server 199.252.155.234 in 80 ms.
MX 30 mx15.nmci.naVy.miL. from server 199.252.155.234 in 80 ms.
MX 30 mx14.nmci.naVy.miL. from server 199.252.155.234 in 80 ms.
MX 30 mx13.nmci.naVy.miL. from server 199.252.155.234 in 80 ms.

Netherlands:
MX 30 mx13.nmci.nAvy.miL. from server 199.252.154.234 in 20 ms.
MX 30 mx15.nmci.nAvy.miL. from server 199.252.154.234 in 20 ms.
MX 20 sec-jeemsg.eemsg.mail.miL. from server 199.252.154.234 in 20 ms.
MX 10 pri-jeemsg.eemsg.mail.miL. from server 199.252.154.234 in 20 ms.
MX 30 mx14.nmci.nAvy.miL. from server 199.252.154.234 in 20 ms.

-Jim P.
Ray Van Dolson via Outages | 27 Oct 16:57 2014

[outages] .mil MX Servers?

Seeing issues connecting to a number of .mil MX servers this morning
(via port 25).

I'm able to reproduce the issue from external hosts so I don't
*believe* it's just us, but still investigating.

Anyone else seeing this?

Ray
Clayton Dukes via Outages | 25 Oct 06:31 2014

[outages] Dynamic blocklists to IOS ACL

Sorry for the off-topic post, but Google has not yielded much so I thought I would ask here.

Does anyone know of, or have a script that can take in ip blocklists from https://www.iblocklist.com/lists.php and update a router's ACL? (IOS 12.x)




______________________________________________________________

Clayton Dukes
______________________________________________________________
<div><div dir="ltr">Sorry for the off-topic post, but Google has not yielded much so I thought I would ask here.<div>
<br><div>Does anyone know of, or have a script that can take in ip blocklists from&nbsp;<a href="https://www.iblocklist.com/lists.php">https://www.iblocklist.com/lists.php</a> and update a router's ACL? (IOS 12.x)</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div>
<br clear="all"><div>______________________________________________________________ <br><br>Clayton Dukes<br>______________________________________________________________</div>
</div>
</div>
</div></div>
Bill McGonigle via Outages | 24 Oct 11:34 2014

[outages] Intermittent Comcast DNS issues from VT

Since about midnight (Eastern) Comcast's DNS (75.75.75.7[5,6]) has been giving timeouts and the occasional 'no route to host' from Vermont.   Switched our resolvers to use Google's Public DNS (via the same Comcast line) and all services returned to normal.

Packet traces aren't interesting (just outbound traffic, no responses) and traceroutes to the cdn usually succeed.  dns.comcast.net reports no problems.  Queries at the command line sometimes succeed, sometimes fail, sometimes take a long time to finish.

-Bill

<div><div dir="ltr">
<div>
<div>Since about midnight (Eastern) Comcast's DNS (75.75.75.7[5,6]) has been giving timeouts and the occasional 'no route to host' from Vermont.&nbsp;&nbsp; Switched our resolvers to use Google's Public DNS (via the same Comcast line) and all services returned to normal.<br><br>
</div>Packet traces aren't interesting (just outbound traffic, no responses) and traceroutes to the cdn usually succeed.&nbsp; <a href="http://dns.comcast.net">dns.comcast.net</a> reports no problems.&nbsp; Queries at the command line sometimes succeed, sometimes fail, sometimes take a long time to finish.<br><br>
</div>-Bill<br><br>
</div></div>

www.apple.com is gone?

Our monitoring system alerted me to that.  Almost all our DNS servers have
aged it out, except two:

Here's what they return from dig AAAA www.apple.com +short
DNS server: 192.168.0.93
www.isg-apple.com.akadns.net.
www.apple.com.edgekey.net.
e3191.dscc.akamaiedge.net.
e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net.

Frank


Gmane