Frank Bulk via Outages | 23 Sep 22:25 2014

www.facebook.com

Our monitoring system has seen HTTPv6 access to www.facebook.com timeout
(happens at 10 seconds) over a dozen times this afternoon, starting at 2:07
pm Central.

Anyone else seeing something similar over IPv4 or v6?

Frank

root <at> nagios:~# tcptraceroute6 www.facebook.com
traceroute to edge-star6-shv-01-ash5.facebook.com
(2a03:2880:2050:1f08:face:b00c:0:1) from 2607:fe28:0:1000::5, port 80, from
port 57678, 30 hops max, 60 bytes packets
 1  router-core.mtcnet.net (2607:fe28:0:1000::1)  0.285 ms  0.229 ms  0.202
ms
 2  sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197)  0.193 ms  0.130 ms  0.132
ms
 3  v6-premier.sxcy-mlx.fbnt.netins.net (2001:5f8:7f0a:2::1)  1.634 ms
1.584 ms  1.610 ms
 4  v6-ins-db4-te-0-6-0-4-219.desm.netins.net (2001:5f8:1:1::1)  8.184 ms
7.962 ms  7.683 ms
 5  v6-ins-dc1-te-7-4.desm.netins.net (2001:5f8::26:2)  7.783 ms  7.785 ms
7.778 ms
 6  v6-ins-kc2-po20.kmrr.netins.net (2001:5f8::8:2)  9.023 ms  9.017 ms
9.001 ms
 7  v6-ins-kc1-po21.kmrr.netins.net (2001:5f8::14:1)  9.105 ms  9.012 ms
9.033 ms
 8  2001:438:fffe::e99 (2001:438:fffe::e99)  46.100 ms  14.780 ms  14.797 ms
 9  ae5.cr1.ord2.us.above.net (2001:438:ffff::407d:1e59)  23.269 ms  48.526
ms  23.277 ms
10  ae4.er1.ord7.us.above.net (2001:438:ffff::407d:1c32)  23.340 ms  23.337
(Continue reading)

Radde, Darrin via Outages | 19 Sep 23:25 2014

[outages] TimeWarner Congestion in Seattle?

 

Noticing loss through TimeWarner in Seattle to Internet destinations, any known congestion or other issues with TimeWarner in the area?

 

To Google (8.8.8.8)

Success rate is 99 percent (9939/10000), round-trip min/avg/max = 4/7/36 ms

 

To 66.192.253.122 (Time Warner internal hop, second in a traceroute to 8.8.8.8) from my router connected to TimeWarner

Success rate is 99 percent (9963/10000), round-trip min/avg/max = 1/1/76 ms

 

To 4.2.2.1

Success rate is 99 percent (9990/10000), round-trip min/avg/max = 16/19/44 ms

 

To 64.129.234.202 (Time Warner internal hop, second hop in a traceroute to 4.2.2.1) from my router connected to TimeWarner

Success rate is 99 percent (9981/10000), round-trip min/avg/max = 16/21/108 ms

 

Darrin

 

 

 

 

This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
<div>
<div class="WordSection1">
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Noticing loss through TimeWarner in Seattle to Internet destinations, any known congestion or other issues with TimeWarner in the area?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">To Google (8.8.8.8)<p></p></p>
<p class="MsoNormal">Success rate is 99 percent (9939/10000), round-trip min/avg/max = 4/7/36 ms<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">To 66.192.253.122 (Time Warner internal hop, second in a traceroute to 8.8.8.8) from my router connected to TimeWarner<p></p></p>
<p class="MsoNormal">Success rate is 99 percent (9963/10000), round-trip min/avg/max = 1/1/76 ms<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">To 4.2.2.1<p></p></p>
<p class="MsoNormal">Success rate is 99 percent (9990/10000), round-trip min/avg/max = 16/19/44 ms<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">To 64.129.234.202 (Time Warner internal hop, second hop in a traceroute to 4.2.2.1) from my router connected to TimeWarner<p></p></p>
<p class="MsoNormal">Success rate is 99 percent (9981/10000), round-trip min/avg/max = 16/21/108 ms<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Darrin<p></p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="190">
<tr>
<td>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
</td>
</tr>
<tr>
<td valign="top">
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
</td>
</tr>
</table>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>

This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.<br>
</div>
Bill Woodcock via Outages | 19 Sep 19:36 2014
Stephen Repetski | 19 Sep 15:23 2014
Picon

"Why the internet broke today"

<div><div dir="ltr">
<div>
<a href="http://www.renesys.com/2014/09/why-the-internet-broke-today/">http://www.renesys.com/2014/09/why-the-internet-broke-today/</a><br>
</div>
<div>
<br clear="all"><div><div dir="ltr">Stephen Repetski<br>
</div></div>
</div>
</div></div>
Bill Wichers via Outages | 18 Sep 18:34 2014

[outages] Possible XO/ATT peering issue in Chicago

Is anyone else seeing excessive packet loss between ATT and XO in Chicago? We started seeing this this morning, and the problem looks like it might actually be within XO’s network in Chicago but I’m not 100% certain. I have no info from either carrier as of yet.

 

Hop #6 is 216.156.0.185

Hop #9 is 12.122.133.34

Hop #10 in the lower mtr output is 12.122.2.206

 

Packets               Pings

Host                                                Loss%  Last   Avg  Best  Wrst StDev

5. ae1d0.mcr1.southfield-mi.us.xo.net                0.0%   8.0  10.8   6.6  48.9   7.0

6. vb1730.rar3.chicago-il.us.xo.net                  0.0%   9.8  10.0   6.6  14.7   1.4

7. 207.88.14.194.ptr.us.xo.net                      46.4%   7.9   8.4   6.5  44.9   3.7

8. 206.111.2.90.ptr.us.xo.net                       12.9%  39.5  41.8  38.4  60.6   1.9

9. cr1.cgcil.ip.att.net                             15.5%  49.7  49.6  46.3  52.8   1.5

10. 12.122.99.26                                     17.8%  49.9  48.4  45.0  51.5   1.4

 

And

 

5. ae1d0.mcr1.southfield-mi.us.xo.net                    0.0%   7.7   9.6   6.5  80.1   7.3

6. vb1730.rar3.chicago-il.us.xo.net                      0.0%  10.4   9.0   6.6  11.6   1.3

7. 207.88.14.194.ptr.us.xo.net                          44.4%   6.6   7.5   6.5  32.8   2.9

8. 206.111.2.90.ptr.us.xo.net                           12.1%  41.5  41.4  38.1  64.2   2.1

9. cr1.cgcil.ip.att.net                                 14.2%  65.4  66.2  63.8  76.0   1.5

10. cr1.cl2oh.ip.att.net                                 15.2%  67.5  67.0  64.0 123.6   4.7

11. cr2.nsvtn.ip.att.net                                 15.2%  69.3  68.6  64.3 163.8   9.3

 

   -Bill

<div>
<div class="WordSection1">
<p class="MsoNormal">Is anyone else seeing excessive packet loss between ATT and XO in Chicago? We started seeing this this morning, and the problem looks like it might actually be within XO&rsquo;s network in Chicago but I&rsquo;m not 100% certain. I have no info from
 either carrier as of yet.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Hop #6 is 216.156.0.185<p></p></p>
<p class="MsoNormal">Hop #9 is 12.122.133.34<p></p></p>
<p class="MsoNormal">Hop #10 in the lower mtr output is 12.122.2.206<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Packets&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pings<p></p></p>
<p class="MsoNormal">Host&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Loss%&nbsp; Last&nbsp;&nbsp; Avg&nbsp; Best&nbsp; Wrst StDev<p></p></p>
<p class="MsoNormal">5. ae1d0.mcr1.southfield-mi.us.xo.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.0%&nbsp;&nbsp; 8.0&nbsp; 10.8&nbsp;&nbsp; 6.6&nbsp; 48.9&nbsp;&nbsp; 7.0<p></p></p>
<p class="MsoNormal">6. vb1730.rar3.chicago-il.us.xo.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.0%&nbsp;&nbsp; 9.8&nbsp; 10.0&nbsp;&nbsp; 6.6&nbsp; 14.7&nbsp;&nbsp; 1.4<p></p></p>
<p class="MsoNormal">7. 207.88.14.194.ptr.us.xo.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 46.4%&nbsp;&nbsp; 7.9&nbsp;&nbsp; 8.4&nbsp;&nbsp; 6.5&nbsp; 44.9&nbsp;&nbsp; 3.7<p></p></p>
<p class="MsoNormal">8. 206.111.2.90.ptr.us.xo.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 12.9%&nbsp; 39.5&nbsp; 41.8&nbsp; 38.4&nbsp; 60.6&nbsp;&nbsp; 1.9<p></p></p>
<p class="MsoNormal">9. cr1.cgcil.ip.att.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 15.5%&nbsp; 49.7&nbsp; 49.6&nbsp; 46.3&nbsp; 52.8&nbsp;&nbsp; 1.5<p></p></p>
<p class="MsoNormal">10. 12.122.99.26&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 17.8%&nbsp; 49.9&nbsp; 48.4&nbsp; 45.0&nbsp; 51.5&nbsp;&nbsp; 1.4<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">And<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">5. ae1d0.mcr1.southfield-mi.us.xo.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.0%&nbsp;&nbsp; 7.7&nbsp;&nbsp; 9.6&nbsp;&nbsp; 6.5&nbsp; 80.1&nbsp;&nbsp; 7.3<p></p></p>
<p class="MsoNormal">6. vb1730.rar3.chicago-il.us.xo.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.0%&nbsp; 10.4&nbsp;&nbsp; 9.0&nbsp;&nbsp; 6.6&nbsp; 11.6&nbsp;&nbsp; 1.3<p></p></p>
<p class="MsoNormal">7. 207.88.14.194.ptr.us.xo.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 44.4%&nbsp;&nbsp; 6.6&nbsp;&nbsp; 7.5&nbsp;&nbsp; 6.5&nbsp; 32.8&nbsp;&nbsp; 2.9<p></p></p>
<p class="MsoNormal">8. 206.111.2.90.ptr.us.xo.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 12.1%&nbsp; 41.5&nbsp; 41.4&nbsp; 38.1&nbsp; 64.2&nbsp;&nbsp; 2.1<p></p></p>
<p class="MsoNormal">9. cr1.cgcil.ip.att.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 14.2%&nbsp; 65.4&nbsp; 66.2&nbsp; 63.8&nbsp; 76.0&nbsp;&nbsp; 1.5<p></p></p>
<p class="MsoNormal">10. cr1.cl2oh.ip.att.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 15.2%&nbsp; 67.5&nbsp; 67.0&nbsp; 64.0 123.6&nbsp;&nbsp; 4.7<p></p></p>
<p class="MsoNormal">11. cr2.nsvtn.ip.att.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 15.2%&nbsp; 69.3&nbsp; 68.6&nbsp; 64.3 163.8&nbsp;&nbsp; 9.3<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">&nbsp;&nbsp; -Bill<p></p></p>
</div>
</div>
virendra rode via Outages | 16 Sep 01:42 2014

[outages] cogent issue loading youtube videos

Is anyone else experiencing youtube related issues off Cogent where
one is able to load the base site but not able to load videos? Per
Cogent support this is something google is blocking but I don't have
issues off Verizon peer

Unfortunately due to bandwidth reasons I cannot swing over to Verizon
so I'm stuck

Any validation will be greatly appreciated

regards,
/virendra
Owen Roth via Outages | 10 Sep 19:07 2014

[outages] Verizon fiber ring down in LA

Is anyone else being impacted or have more information about a Verizon fiber ring repair in LA that went
south yesterday afternoon? A client's fiber is STILL down more than 16 hours later, and the only
information I have is that it is a configuration/provisioning issue with no ETR! 

This is new ground -- I have never an outage of this type, and rarely of this duration. Any further
information is appreciated.

Regards,
------------
Owen Roth
NOC Manager
Impulse Advanced Communications
owen@...
805-884-6332

Frank Bulk via Outages | 10 Sep 18:10 2014

[outages] ipv6.cnn.com down

Access to ipv6.cnn.com went down at 10:45 am.  Level3's looking glass shows
that 2620:100:e000::/48 is still being advertised, but traceouroutes don't
get into TimeWarner's network.

root <at> nagios:# tcptraceroute6 ipv6.cnn.com
traceroute to ipv6.cnn.com (2620:100:e000::8001) from 2607:fe28:0:1000::5,
port 80, from port 43374, 30 hops max, 60 bytes packets
 1  router-core.mtcnet.net (2607:fe28:0:1000::1)  0.248 ms  0.217 ms  0.201
ms
 2  sxct.spnc.mtcnet.net (2607:fe28:11:1002::194)  0.198 ms  0.130 ms  0.127
ms
 3  v6-premier.movl-mlx.fbnt.netins.net (2001:5f8:7f0a:1::1)  4.921 ms
4.912 ms  4.909 ms
 4  v6-ins-kb1-te-12-2-3031.kmrr.netins.net (2001:5f8:2:2::1)  10.723 ms
10.657 ms  10.577 ms
 5  v6-ins-kc1-et-9-3.kmrr.netins.net (2001:5f8::28:1)  10.127 ms  10.028 ms
10.042 ms
 6  2001:438:fffe::e99 (2001:438:fffe::e99)  15.788 ms  15.803 ms  15.866 ms
 7  ae5.cr1.ord2.us.above.net (2001:438:ffff::407d:1e59)  31.760 ms  32.954
ms  24.212 ms
 8  ae4.er1.ord7.us.above.net (2001:438:ffff::407d:1c32)  24.282 ms  23.754
ms  23.685 ms
 9  2001:438:ffff::407d:c0a (2001:438:ffff::407d:c0a)  23.461 ms  84.608 ms
23.410 ms
10  vl-52.edge2.Chicago2.Level3.net (2001:1900:37:2::4)  23.534 ms  23.491
ms  23.533 ms
11  2001:1900:4:1::be (2001:1900:4:1::be)  37.618 ms  52.090 ms  37.627 ms
12  vl-4040.car1.Atlanta2.Level3.net (2001:1900:4:1::b1)  83.993 ms  53.707
ms  53.662 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
root <at> nagios:#

This is the record from our daily archive (~2 am today):

traceroute to ipv6.cnn.com (2620:100:e000::8001) from 2607:fe28:0:1000::5,
port 80, from port 60821, 30 hops max, 60 bytes packets
 1  router-core.mtcnet.net (2607:fe28:0:1000::1)  0.258 ms  0.203 ms  0.213
ms
 2  sxct.spnc.mtcnet.net (2607:fe28:11:1002::194)  0.206 ms  0.124 ms  0.194
ms
 3  v6-premier.movl-mlx.fbnt.netins.net (2001:5f8:7f0a:1::1)  4.943 ms
4.948 ms  4.942 ms
 4  v6-ins-kb1-te-12-2-3031.kmrr.netins.net (2001:5f8:2:2::1)  10.633 ms
10.735 ms  10.822 ms
 5  v6-ins-kc1-et-9-3.kmrr.netins.net (2001:5f8::28:1)  10.041 ms  10.032 ms
11.672 ms
 6  2001:438:fffe::e99 (2001:438:fffe::e99)  15.798 ms  15.814 ms  15.784 ms
 7  ae5.cr1.ord2.us.above.net (2001:438:ffff::407d:1e59)  24.273 ms  24.270
ms  24.640 ms
 8  ae4.er1.ord7.us.above.net (2001:438:ffff::407d:1c32)  23.940 ms  23.895
ms  23.913 ms
 9  2001:438:ffff::407d:c0a (2001:438:ffff::407d:c0a)  54.277 ms  23.479 ms
23.482 ms
10  vl-51.edge2.Chicago2.Level3.net (2001:1900:37:1::4)  28.617 ms  23.589
ms  23.586 ms
11  2001:1900:4:1::be (2001:1900:4:1::be)  37.561 ms  37.553 ms  37.538 ms
12  vl-4040.car1.Atlanta2.Level3.net (2001:1900:4:1::b1)  54.006 ms  53.890
ms  53.989 ms
13  vl-52.ear1.Atlanta2.Level3.net (2001:1900:1c:2::13)  933.251 ms  871.418
ms  528.468 ms
14  TIME-WARNER.ear1.Atlanta2.Level3.net (2001:1900:2100::442)  76.361 ms
76.329 ms  76.337 ms
15  2620:100:e000:ffff::96 (2620:100:e000:ffff::96)  76.655 ms  76.631 ms
76.660 ms
16  2620:100:e000:ffff::111 (2620:100:e000:ffff::111)  165.671 ms  77.386 ms
76.685 ms
17  2620:100:e000::d (2620:100:e000::d)  77.111 ms  76.686 ms  76.808 ms
18  2620:100:e000::19 (2620:100:e000::19)  76.638 ms  76.602 ms  76.590 ms
19  2620:100:e000::8001 (2620:100:e000::8001)  76.341 ms [open]  76.341 ms
76.313 ms

root <at> nagios:/home/fbulk#

joel jaeggli via Outages | 9 Sep 07:31 2014

[outages] widespread level3 issue amsterdam/western europe?

is anyone else seeing routing implosion on l3 or first symtoms were in
western europe.

I had packets bound for l3 ips in ams making lazy circles. started circa
0430 utc

joel

is anyone else seeing routing implosion on l3 or first symtoms were in
western europe.

I had packets bound for l3 ips in ams making lazy circles. started circa
0430 utc

joel

jd via Outages | 6 Sep 17:18 2014

[outages] pacwest is down again

at least it is for me, their toll free does not ring either.

looks like last call i saw was 6:40 am pdt.
Tim Huffman via Outages | 5 Sep 22:49 2014

[outages] FW: HD5844551 Mass Outage - New York / New York

This is twice I've seen Cogent go down in NY this afternoon. Anybody know what's going on there?

Tim Huffman
Director of Engineering
Business Only Broadband
999 Oak Creek Dr, Lombard, IL 60148
Direct: 630.590.6012 | Main: 630.590.6000 | Fax: 630.986.2496 
thuffman <at> bobbroadband.com  |  http://www.bobbroadband.com/
Cell:  630.340.1925 | Toll-Free Customer Support:  877.262.4553
  Follow Us on LinkedIn  |    Follow Us on Twitter
 please consider the environment prior to printing

-----Original Message-----
From: Cogent Support [mailto:Support <at> Cogentco.com] 
Sent: Friday, September 05, 2014 3:39 PM
To: noc
Subject: HD5844551 Mass Outage - New York / New York
Importance: High

Dear Cogent Customer,

We are currently experiencing a Mass Outage on our network. We are working to resolve this as quickly as
possible. Please check http://status.cogentco.com for updates on this event.

If you need to open an individual ticket on this event, please e-mail support <at> cogentco.com and reference
the mass outage HD5844551.

Impacted Region: New York / New York
Order(s) Impacted: 1-76060967
Mass Outage Ticket: HD5844551
Status:

Thank You,

Cogent Support
support <at> cogentco.com
877-726-4368

_______________________________________________
Outages mailing list
Outages <at> outages.org
https://puck.nether.net/mailman/listinfo/outages

Gmane