Seems they're having issues, no internet routing for several coax based customers in Northern VA: Tracing route to google-public-dns-a.google.com [8.8.8.8] over a maximum of 30 hops: 4 15 ms 19 ms 12 ms 96.108.140.117 5 * * * Request timed out. 6 57 ms 28 ms 20 ms be-21508-cr02.ashburn.va.ibone.comcast.net [68.8 6.91.53] 7 23 ms 33 ms 16 ms be-10189-pe07.ashburn.va.ibone.comcast.net [68.8 6.83.66] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. KP
Can you unicast one of their source IPs to me? I'll take a look and see what's up. Thanks, John On Mon, Nov 12, 2018 at 12:41 PM Kenneth Padgett via Outages < outages@outages.org> wrote:
Seems they're having issues, no internet routing for several coax based customers in Northern VA:
Tracing route to google-public-dns-a.google.com [8.8.8.8] over a maximum of 30 hops:
4 15 ms 19 ms 12 ms 96.108.140.117 5 * * * Request timed out. 6 57 ms 28 ms 20 ms be-21508-cr02.ashburn.va.ibone.comcast.net [68.8 6.91.53] 7 23 ms 33 ms 16 ms be-10189-pe07.ashburn.va.ibone.comcast.net [68.8 6.83.66] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out.
KP _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Looks OK here in Baltimore/DC metro area: Tracing route to google-public-dns-a.google.com [8.8.8.8] over a maximum of 30 hops: 4 1 ms 1 ms 1 ms 96.108.111.33 5 2 ms 3 ms 2 ms xe-7-1-7-0-ar01.capitolhghts.md.bad.comcast.net [68.85.114.209] 6 4 ms 4 ms 5 ms ae-14-ar01.capitolhghts.md.bad.comcast.net [68.87.168.53] 7 8 ms 8 ms 7 ms be-33657-cr02.ashburn.va.ibone.comcast.net [68.86.90.57] 8 6 ms 6 ms 5 ms be-10189-pe07.ashburn.va.ibone.comcast.net [68.86.83.66] 9 6 ms 5 ms 6 ms as4436-1-c.111eighthave.ny.ibone.comcast.net [173.167.57.162] 10 * * * Request timed out. 11 11 ms 10 ms 11 ms 209.85.246.134 12 7 ms 5 ms 6 ms 209.85.254.73 13 6 ms 6 ms 7 ms google-public-dns-a.google.com [8.8.8.8] Thanks, Dave Robbins From: Outages <outages-bounces@outages.org> On Behalf Of John Neiberger via Outages Sent: Monday, November 12, 2018 2:53 PM To: Kenneth Padgett <kenneth@itlifesaver.com> Cc: outages@outages.org Subject: Re: [outages] Comcast routing / peering issues in Ashburn, VA Can you unicast one of their source IPs to me? I'll take a look and see what's up. Thanks, John On Mon, Nov 12, 2018 at 12:41 PM Kenneth Padgett via Outages <outages@outages.org<mailto:outages@outages.org>> wrote: Seems they're having issues, no internet routing for several coax based customers in Northern VA: Tracing route to google-public-dns-a.google.com<http://google-public-dns-a.google.com> [8.8.8.8] over a maximum of 30 hops: 4 15 ms 19 ms 12 ms 96.108.140.117 5 * * * Request timed out. 6 57 ms 28 ms 20 ms be-21508-cr02.ashburn.va.ibone.comcast.net<http://be-21508-cr02.ashburn.va.ibone.comcast.net> [68.8 6.91.53] 7 23 ms 33 ms 16 ms be-10189-pe07.ashburn.va.ibone.comcast.net<http://be-10189-pe07.ashburn.va.ibone.comcast.net> [68.8 6.83.66] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. KP _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages This message may contain confidential or privileged information and is intended only for the individuals addressed in the body of the email. Nothing in this message shall be construed as making or accepting an offer to form a contract unless this message is followed by a written signed confirmation. If you have received this message in error, please notify the sender and then delete the message and all copies. Thank you.
Is any one still seeing peering issues? So far we have client sites using spectrum and comcast routing weirdly to our internap data center in NJ Hop IP Sent Recv Loss Best Worst Average Last Host 1 10.1.10.1 100 100 0% 1 11 4 3 2 96.120.49.61 100 100 0% 5 13 10 10 3 68.86.235.145 100 100 0% 6 13 8 7 po-103-rur01.plymouth.mn.minn.comcast.net 4 68.87.174.146 100 100 0% 5 12 9 10 po-2-rur02.plymouth.mn.minn.comcast.net 5 68.87.174.93 100 100 0% 7 13 11 10 be-9-ar01.roseville.mn.minn.comcast.net 6 68.86.94.81 100 100 0% 16 26 18 18 be-13367-cr02.350ecermak.il.ibone.comcast.net 7 64.86.137.25 100 100 0% 13 26 18 17 ix-xe-5-0-5-0.tcore1.ct8-chicago.as6453.net 8 64.86.21.104 100 100 0% 59 82 65 65 if-ae-29-2.tcore2.sqn-san-jose.as6453.net 9 63.243.205.1 100 100 0% 59 68 63 66 if-ae-1-2.tcore1.sqn-san-jose.as6453.net 10 63.243.205.131 100 100 0% 69 82 72 75 if-ae-18-2.tcore2.sv1-santa-clara.as6453.net 11 63.243.251.1 100 100 0% 68 82 73 74 if-ae-0-2.tcore1.sv1-santa-clara.as6453.net 12 66.110.59.8 100 100 0% 67 83 71 73 if-ae-8-2.tcore1.lvw-los-angeles.as6453.net 13 66.110.59.2 100 100 0% 67 89 73 75 if-ae-2-2.tcore2.lvw-los-angeles.as6453.net 14 180.87.15.25 100 100 0% 239 248 243 245 if-ae-7-2.tcore2.svw-singapore.as6453.net 15 180.87.96.21 100 100 0% 230 247 236 235 if-ae-20-2.tcore1.svq-singapore.as6453.net 16 120.29.215.242 100 77 22% 255 281 261 258 17 0.0.0.0 100 0 100% 0 0 0 0 18 202.127.73.101 100 86 14% 222 260 229 228 unknown.telstraglobal.net 19 202.84.224.189 100 86 14% 224 233 228 227 i-93.sgpl-core02.telstraglobal.net 20 202.84.140.46 100 92 8% 56 65 60 60 i-10850.eqnx-core02.telstraglobal.net 21 202.84.247.17 100 91 9% 56 97 60 59 i-92.eqnx03.telstraglobal.net 22 0.0.0.0 100 0 100% 0 0 0 0 23 64.95.158.178 100 88 12% 66 156 72 70 bbr2.ae7.sje.pnap.net 24 64.95.159.21 100 89 11% 73 87 78 74 bbr2.xe-1-1-1.inapbb-chg-sje-8.chg.pnap.net 25 64.95.159.18 100 87 13% 95 133 102 100 bbr1.xe-4-0-0.inapbb-chg-nym-12.nym007.pnap.net 26 64.95.158.234 100 86 14% 95 116 108 112 tsr1.e6-1.nyj004.pnap.net 27 ***.***.***.** 100 86 14% 280 296 287 285 On 2018-11-12 14:56, Robbins, David via Outages wrote:
Looks OK here in Baltimore/DC metro area:
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
4 1 ms 1 ms 1 ms 96.108.111.33
5 2 ms 3 ms 2 ms xe-7-1-7-0-ar01.capitolhghts.md.bad.comcast.net [68.85.114.209]
6 4 ms 4 ms 5 ms ae-14-ar01.capitolhghts.md.bad.comcast.net [68.87.168.53]
7 8 ms 8 ms 7 ms be-33657-cr02.ashburn.va.ibone.comcast.net [68.86.90.57]
8 6 ms 6 ms 5 ms be-10189-pe07.ashburn.va.ibone.comcast.net [68.86.83.66]
9 6 ms 5 ms 6 ms as4436-1-c.111eighthave.ny.ibone.comcast.net [173.167.57.162]
10 * * * Request timed out.
11 11 ms 10 ms 11 ms 209.85.246.134
12 7 ms 5 ms 6 ms 209.85.254.73
13 6 ms 6 ms 7 ms google-public-dns-a.google.com [8.8.8.8]
Thanks,
DAVE ROBBINS
FROM: Outages <outages-bounces@outages.org> ON BEHALF OF John Neiberger via Outages SENT: Monday, November 12, 2018 2:53 PM TO: Kenneth Padgett <kenneth@itlifesaver.com> CC: outages@outages.org SUBJECT: Re: [outages] Comcast routing / peering issues in Ashburn, VA
Can you unicast one of their source IPs to me? I'll take a look and see what's up.
Thanks,
John
On Mon, Nov 12, 2018 at 12:41 PM Kenneth Padgett via Outages <outages@outages.org> wrote:
Seems they're having issues, no internet routing for several coax based customers in Northern VA:
Tracing route to google-public-dns-a.google.com [1] [8.8.8.8]
over a maximum of 30 hops:
4 15 ms 19 ms 12 ms 96.108.140.117
5 * * * Request timed out.
6 57 ms 28 ms 20 ms be-21508-cr02.ashburn.va.ibone.comcast.net [2] [68.8
6.91.53]
7 23 ms 33 ms 16 ms be-10189-pe07.ashburn.va.ibone.comcast.net [3] [68.8
6.83.66]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
KP
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages This message may contain confidential or privileged information and is intended only for the individuals addressed in the body of the email. Nothing in this message shall be construed as making or accepting an offer to form a contract unless this message is followed by a written signed confirmation. If you have received this message in error, please notify the sender and then delete the message and all copies. Thank you.
Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Links: ------ [1] http://google-public-dns-a.google.com [2] http://be-21508-cr02.ashburn.va.ibone.comcast.net [3] http://be-10189-pe07.ashburn.va.ibone.comcast.net
I've been seeing some weirdness with AWS EC2 connectivity in northern Virginia since Monday. I've just assumed that they are related to whatever is causing Comcast issues as well. Still seeing the AWS issues as of today. Seems like something is definitely up in that area. -- Jeremy Gault, KD4NED Senior Engineer, Voiceopia office: (423) 954-7102 toll-free: (855) 203-6363 x 102 fax: (423) 244-0565 On Wed, Nov 14, 2018, 11:48 Guillermo via Outages <outages@outages.org wrote:
Is any one still seeing peering issues? So far we have client sites using spectrum and comcast routing weirdly to our internap data center in NJ
Hop IP Sent Recv Loss Best Worst Average Last Host 1 10.1.10.1 100 100 0% 1 11 4 3 2 96.120.49.61 100 100 0% 5 13 10 10 3 68.86.235.145 100 100 0% 6 13 8 7 po-103-rur01.plymouth.mn.minn.comcast.net 4 68.87.174.146 100 100 0% 5 12 9 10 po-2-rur02.plymouth.mn.minn.comcast.net 5 68.87.174.93 100 100 0% 7 13 11 10 be-9-ar01.roseville.mn.minn.comcast.net 6 68.86.94.81 100 100 0% 16 26 18 18 be-13367-cr02.350ecermak.il.ibone.comcast.net 7 64.86.137.25 100 100 0% 13 26 18 17 ix-xe-5-0-5-0.tcore1.ct8-chicago.as6453.net 8 64.86.21.104 100 100 0% 59 82 65 65 if-ae-29-2.tcore2.sqn-san-jose.as6453.net 9 63.243.205.1 100 100 0% 59 68 63 66 if-ae-1-2.tcore1.sqn-san-jose.as6453.net 10 63.243.205.131 100 100 0% 69 82 72 75 if-ae-18-2.tcore2.sv1-santa-clara.as6453.net 11 63.243.251.1 100 100 0% 68 82 73 74 if-ae-0-2.tcore1.sv1-santa-clara.as6453.net 12 66.110.59.8 100 100 0% 67 83 71 73 if-ae-8-2.tcore1.lvw-los-angeles.as6453.net 13 66.110.59.2 100 100 0% 67 89 73 75 if-ae-2-2.tcore2.lvw-los-angeles.as6453.net 14 180.87.15.25 100 100 0% 239 248 243 245 if-ae-7-2.tcore2.svw-singapore.as6453.net 15 180.87.96.21 100 100 0% 230 247 236 235 if-ae-20-2.tcore1.svq-singapore.as6453.net 16 120.29.215.242 100 77 22% 255 281 261 258 17 0.0.0.0 100 0 100% 0 0 0 0 18 202.127.73.101 100 86 14% 222 260 229 228 unknown.telstraglobal.net 19 202.84.224.189 100 86 14% 224 233 228 227 i-93.sgpl-core02.telstraglobal.net 20 202.84.140.46 100 92 8% 56 65 60 60 i-10850.eqnx-core02.telstraglobal.net 21 202.84.247.17 100 91 9% 56 97 60 59 i-92.eqnx03.telstraglobal.net 22 0.0.0.0 100 0 100% 0 0 0 0 23 64.95.158.178 100 88 12% 66 156 72 70 bbr2.ae7.sje.pnap.net 24 64.95.159.21 100 89 11% 73 87 78 74 bbr2.xe-1-1-1.inapbb-chg-sje-8.chg.pnap.net 25 64.95.159.18 100 87 13% 95 133 102 100 bbr1.xe-4-0-0.inapbb-chg-nym-12.nym007.pnap.net 26 64.95.158.234 100 86 14% 95 116 108 112 tsr1.e6-1.nyj004.pnap.net 27 ***.***.***.** 100 86 14% 280 296 287 285
On 2018-11-12 14:56, Robbins, David via Outages wrote:
Looks OK here in Baltimore/DC metro area:
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
4 1 ms 1 ms 1 ms 96.108.111.33
5 2 ms 3 ms 2 ms xe-7-1-7-0-ar01.capitolhghts.md.bad.comcast.net [68.85.114.209]
6 4 ms 4 ms 5 ms ae-14-ar01.capitolhghts.md.bad.comcast.net [68.87.168.53]
7 8 ms 8 ms 7 ms be-33657-cr02.ashburn.va.ibone.comcast.net [68.86.90.57]
8 6 ms 6 ms 5 ms be-10189-pe07.ashburn.va.ibone.comcast.net [68.86.83.66]
9 6 ms 5 ms 6 ms as4436-1-c.111eighthave.ny.ibone.comcast.net [173.167.57.162]
10 * * * Request timed out.
11 11 ms 10 ms 11 ms 209.85.246.134
12 7 ms 5 ms 6 ms 209.85.254.73
13 6 ms 6 ms 7 ms google-public-dns-a.google.com [8.8.8.8]
Thanks,
*Dave Robbins*
*From:* Outages <outages-bounces@outages.org> *On Behalf Of *John Neiberger via Outages *Sent:* Monday, November 12, 2018 2:53 PM *To:* Kenneth Padgett <kenneth@itlifesaver.com> *Cc:* outages@outages.org *Subject:* Re: [outages] Comcast routing / peering issues in Ashburn, VA
Can you unicast one of their source IPs to me? I'll take a look and see what's up.
Thanks,
John
On Mon, Nov 12, 2018 at 12:41 PM Kenneth Padgett via Outages < outages@outages.org> wrote:
Seems they're having issues, no internet routing for several coax based customers in Northern VA:
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
4 15 ms 19 ms 12 ms 96.108.140.117
5 * * * Request timed out.
6 57 ms 28 ms 20 ms be-21508-cr02.ashburn.va.ibone.comcast.net [68.8
6.91.53]
7 23 ms 33 ms 16 ms be-10189-pe07.ashburn.va.ibone.comcast.net [68.8
6.83.66]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
KP
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
This message may contain confidential or privileged information and is intended only for the individuals addressed in the body of the email. Nothing in this message shall be construed as making or accepting an offer to form a contract unless this message is followed by a written signed confirmation. If you have received this message in error, please notify the sender and then delete the message and all copies. Thank you. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
FWIW we haven’t seen any issues with connectivity to AWS EC2 NoVA at all this week. We are on Comcast in the Balto/DC metro area. Thanks, Dave Robbins From: Outages <outages-bounces@outages.org> On Behalf Of Jeremy Gault, KD4NED (Senior Engineer) via Outages Sent: Wednesday, November 14, 2018 12:03 PM To: outages@outages.org Subject: Re: [outages] Comcast routing / peering issues in Ashburn, VA I've been seeing some weirdness with AWS EC2 connectivity in northern Virginia since Monday. I've just assumed that they are related to whatever is causing Comcast issues as well. Still seeing the AWS issues as of today. Seems like something is definitely up in that area. -- Jeremy Gault, KD4NED Senior Engineer, Voiceopia office: (423) 954-7102 toll-free: (855) 203-6363 x 102 fax: (423) 244-0565 On Wed, Nov 14, 2018, 11:48 Guillermo via Outages <outages@outages.org<mailto:outages@outages.org> wrote: Is any one still seeing peering issues? So far we have client sites using spectrum and comcast routing weirdly to our internap data center in NJ Hop IP Sent Recv Loss Best Worst Average Last Host 1 10.1.10.1 100 100 0% 1 11 4 3 2 96.120.49.61 100 100 0% 5 13 10 10 3 68.86.235.145 100 100 0% 6 13 8 7 po-103-rur01.plymouth.mn.minn.comcast.net<http://po-103-rur01.plymouth.mn.minn.comcast.net> 4 68.87.174.146 100 100 0% 5 12 9 10 po-2-rur02.plymouth.mn.minn.comcast.net<http://po-2-rur02.plymouth.mn.minn.comcast.net> 5 68.87.174.93 100 100 0% 7 13 11 10 be-9-ar01.roseville.mn.minn.comcast.net<http://be-9-ar01.roseville.mn.minn.comcast.net> 6 68.86.94.81 100 100 0% 16 26 18 18 be-13367-cr02.350ecermak.il.ibone.comcast.net<http://be-13367-cr02.350ecermak.il.ibone.comcast.net> 7 64.86.137.25 100 100 0% 13 26 18 17 ix-xe-5-0-5-0.tcore1.ct8-chicago.as6453.net<http://ix-xe-5-0-5-0.tcore1.ct8-chicago.as6453.net> 8 64.86.21.104 100 100 0% 59 82 65 65 if-ae-29-2.tcore2.sqn-san-jose.as6453.net<http://if-ae-29-2.tcore2.sqn-san-jose.as6453.net> 9 63.243.205.1 100 100 0% 59 68 63 66 if-ae-1-2.tcore1.sqn-san-jose.as6453.net<http://if-ae-1-2.tcore1.sqn-san-jose.as6453.net> 10 63.243.205.131 100 100 0% 69 82 72 75 if-ae-18-2.tcore2.sv1-santa-clara.as6453.net<http://if-ae-18-2.tcore2.sv1-santa-clara.as6453.net> 11 63.243.251.1 100 100 0% 68 82 73 74 if-ae-0-2.tcore1.sv1-santa-clara.as6453.net<http://if-ae-0-2.tcore1.sv1-santa-clara.as6453.net> 12 66.110.59.8 100 100 0% 67 83 71 73 if-ae-8-2.tcore1.lvw-los-angeles.as6453.net<http://if-ae-8-2.tcore1.lvw-los-angeles.as6453.net> 13 66.110.59.2 100 100 0% 67 89 73 75 if-ae-2-2.tcore2.lvw-los-angeles.as6453.net<http://if-ae-2-2.tcore2.lvw-los-angeles.as6453.net> 14 180.87.15.25 100 100 0% 239 248 243 245 if-ae-7-2.tcore2.svw-singapore.as6453.net<http://if-ae-7-2.tcore2.svw-singapore.as6453.net> 15 180.87.96.21 100 100 0% 230 247 236 235 if-ae-20-2.tcore1.svq-singapore.as6453.net<http://if-ae-20-2.tcore1.svq-singapore.as6453.net> 16 120.29.215.242 100 77 22% 255 281 261 258 17 0.0.0.0 100 0 100% 0 0 0 0 18 202.127.73.101 100 86 14% 222 260 229 228 unknown.telstraglobal.net<http://unknown.telstraglobal.net> 19 202.84.224.189 100 86 14% 224 233 228 227 i-93.sgpl-core02.telstraglobal.net<http://i-93.sgpl-core02.telstraglobal.net> 20 202.84.140.46 100 92 8% 56 65 60 60 i-10850.eqnx-core02.telstraglobal.net<http://i-10850.eqnx-core02.telstraglobal.net> 21 202.84.247.17 100 91 9% 56 97 60 59 i-92.eqnx03.telstraglobal.net<http://i-92.eqnx03.telstraglobal.net> 22 0.0.0.0 100 0 100% 0 0 0 0 23 64.95.158.178 100 88 12% 66 156 72 70 bbr2.ae7.sje.pnap.net<http://bbr2.ae7.sje.pnap.net> 24 64.95.159.21 100 89 11% 73 87 78 74 bbr2.xe-1-1-1.inapbb-chg-sje-8.chg.pnap.net<http://bbr2.xe-1-1-1.inapbb-chg-sje-8.chg.pnap.net> 25 64.95.159.18 100 87 13% 95 133 102 100 bbr1.xe-4-0-0.inapbb-chg-nym-12.nym007.pnap.net<http://bbr1.xe-4-0-0.inapbb-chg-nym-12.nym007.pnap.net> 26 64.95.158.234 100 86 14% 95 116 108 112 tsr1.e6-1.nyj004.pnap.net<http://tsr1.e6-1.nyj004.pnap.net> 27 ***.***.***.** 100 86 14% 280 296 287 285 On 2018-11-12 14:56, Robbins, David via Outages wrote: Looks OK here in Baltimore/DC metro area: Tracing route to google-public-dns-a.google.com<http://google-public-dns-a.google.com> [8.8.8.8] over a maximum of 30 hops: 4 1 ms 1 ms 1 ms 96.108.111.33 5 2 ms 3 ms 2 ms xe-7-1-7-0-ar01.capitolhghts.md.bad.comcast.net<http://xe-7-1-7-0-ar01.capitolhghts.md.bad.comcast.net> [68.85.114.209] 6 4 ms 4 ms 5 ms ae-14-ar01.capitolhghts.md.bad.comcast.net<http://ae-14-ar01.capitolhghts.md.bad.comcast.net> [68.87.168.53] 7 8 ms 8 ms 7 ms be-33657-cr02.ashburn.va.ibone.comcast.net<http://be-33657-cr02.ashburn.va.ibone.comcast.net> [68.86.90.57] 8 6 ms 6 ms 5 ms be-10189-pe07.ashburn.va.ibone.comcast.net<http://be-10189-pe07.ashburn.va.ibone.comcast.net> [68.86.83.66] 9 6 ms 5 ms 6 ms as4436-1-c.111eighthave.ny.ibone.comcast.net<http://as4436-1-c.111eighthave.ny.ibone.comcast.net> [173.167.57.162] 10 * * * Request timed out. 11 11 ms 10 ms 11 ms 209.85.246.134 12 7 ms 5 ms 6 ms 209.85.254.73 13 6 ms 6 ms 7 ms google-public-dns-a.google.com<http://google-public-dns-a.google.com> [8.8.8.8] Thanks, Dave Robbins From: Outages <outages-bounces@outages.org<mailto:outages-bounces@outages.org>> On Behalf Of John Neiberger via Outages Sent: Monday, November 12, 2018 2:53 PM To: Kenneth Padgett <kenneth@itlifesaver.com<mailto:kenneth@itlifesaver.com>> Cc: outages@outages.org<mailto:outages@outages.org> Subject: Re: [outages] Comcast routing / peering issues in Ashburn, VA Can you unicast one of their source IPs to me? I'll take a look and see what's up. Thanks, John On Mon, Nov 12, 2018 at 12:41 PM Kenneth Padgett via Outages <outages@outages.org<mailto:outages@outages.org>> wrote: Seems they're having issues, no internet routing for several coax based customers in Northern VA: Tracing route to google-public-dns-a.google.com<http://google-public-dns-a.google.com> [8.8.8.8] over a maximum of 30 hops: 4 15 ms 19 ms 12 ms 96.108.140.117 5 * * * Request timed out. 6 57 ms 28 ms 20 ms be-21508-cr02.ashburn.va.ibone.comcast.net<http://be-21508-cr02.ashburn.va.ibone.comcast.net> [68.8 6.91.53] 7 23 ms 33 ms 16 ms be-10189-pe07.ashburn.va.ibone.comcast.net<http://be-10189-pe07.ashburn.va.ibone.comcast.net> [68.8 6.83.66] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. KP _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages This message may contain confidential or privileged information and is intended only for the individuals addressed in the body of the email. Nothing in this message shall be construed as making or accepting an offer to form a contract unless this message is followed by a written signed confirmation. If you have received this message in error, please notify the sender and then delete the message and all copies. Thank you. _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages This message may contain confidential or privileged information and is intended only for the individuals addressed in the body of the email. Nothing in this message shall be construed as making or accepting an offer to form a contract unless this message is followed by a written signed confirmation. If you have received this message in error, please notify the sender and then delete the message and all copies. Thank you.
participants (5)
-
Guillermo -
Jeremy Gault, KD4NED (Senior Engineer) -
John Neiberger -
Kenneth Padgett -
Robbins, David