Hello, Having multiple customers call in about reachability - common thread is their side users are all on Comcast. Not to mention the fact that we can't even hit www.comcast.com from our network currently. We have Level3 (Cincinnati) and Qwest (Chicago). Traceroutes from us outbound seem to prefer Qwest and then die in Comcast. I can post traceroutes if need be - just wanted to see if anyone knew anything before I call my upstreams and wade through phone tree hell. -- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 8779 B023 7637 CEC8 C5C6 4052 664D 7E08 3CBB 1739 "SH1-0151. This is the serial number, of our orbital gun."
Yes, please post a traceroute. Thanks, John On Fri, Jun 22, 2012 at 11:54 AM, Brandon Applegate <brandon@burn.net> wrote:
Hello,
Having multiple customers call in about reachability - common thread is their side users are all on Comcast. Not to mention the fact that we can't even hit www.comcast.com from our network currently.
We have Level3 (Cincinnati) and Qwest (Chicago). Traceroutes from us outbound seem to prefer Qwest and then die in Comcast.
I can post traceroutes if need be - just wanted to see if anyone knew anything before I call my upstreams and wade through phone tree hell.
-- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 8779 B023 7637 CEC8 C5C6 4052 664D 7E08 3CBB 1739 "SH1-0151. This is the serial number, of our orbital gun."
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I meant to say that I'm not aware of any outages, but I'm not on the backbone team. I can take a look at the traceroute and get it to the right people. Thanks again, John On Fri, Jun 22, 2012 at 11:58 AM, John Neiberger <jneiberger@gmail.com> wrote:
Yes, please post a traceroute.
Thanks, John
On Fri, Jun 22, 2012 at 11:54 AM, Brandon Applegate <brandon@burn.net> wrote:
Hello,
Having multiple customers call in about reachability - common thread is their side users are all on Comcast. Not to mention the fact that we can't even hit www.comcast.com from our network currently.
We have Level3 (Cincinnati) and Qwest (Chicago). Traceroutes from us outbound seem to prefer Qwest and then die in Comcast.
I can post traceroutes if need be - just wanted to see if anyone knew anything before I call my upstreams and wade through phone tree hell.
-- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 8779 B023 7637 CEC8 C5C6 4052 664D 7E08 3CBB 1739 "SH1-0151. This is the serial number, of our orbital gun."
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Traceroute from Lincoln, Nebraska: (My connection is via Unite Private Networks fiber) Last login: Thu Jun 21 20:52:10 on console 618-Andy-Ringsmuth:~ andyring$ traceroute comcast.com traceroute: Warning: comcast.com has multiple addresses; using 69.241.45.4 traceroute to comcast.com (69.241.45.4), 64 hops max, 52 byte packets 1 192.168.1.2 (192.168.1.2) 0.494 ms 0.209 ms 0.219 ms 2 ge1/2.224_ne_lnk_off_7606.upnllc.com (208.82.104.193) 0.662 ms 0.566 ms 0.582 ms 3 65.125.9.33 (65.125.9.33) 1.995 ms 2.543 ms 2.488 ms 4 chp-brdr-04.inet.qwest.net (67.14.8.234) 19.505 ms 19.259 ms 19.527 ms 5 63.146.26.14 (63.146.26.14) 19.556 ms 19.500 ms 19.514 ms 6 64.86.79.1 (64.86.79.1) 19.617 ms * 19.643 ms 7 173.167.59.149 (173.167.59.149) 26.930 ms 173.167.59.165 (173.167.59.165) 27.209 ms 173.167.59.169 (173.167.59.169) 31.145 ms 8 * * * 9 * * * 10 * * * Won't pull up in a Web browser either. --- Andy Ringsmuth (402) 304-0083 andyring@inebraska.com On Jun 22, 2012, at 12:58 PM, John Neiberger wrote:
Yes, please post a traceroute.
Thanks, John
On Fri, Jun 22, 2012 at 11:54 AM, Brandon Applegate <brandon@burn.net> wrote:
Hello,
Having multiple customers call in about reachability - common thread is their side users are all on Comcast. Not to mention the fact that we can't even hit www.comcast.com from our network currently.
We have Level3 (Cincinnati) and Qwest (Chicago). Traceroutes from us outbound seem to prefer Qwest and then die in Comcast.
I can post traceroutes if need be - just wanted to see if anyone knew anything before I call my upstreams and wade through phone tree hell.
-- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 8779 B023 7637 CEC8 C5C6 4052 664D 7E08 3CBB 1739 "SH1-0151. This is the serial number, of our orbital gun."
_______________________________________________ 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
Their site comes up for me but Comcast is one of our direct peers (and we are transiting them to reach their site). Our traffic levels on our link to them appear normal for the past 24 hours too. This is what I see from my Comcast edge router: Concast-Edge>traceroute comcast.com Type escape sequence to abort. Tracing the route to comcast.com (69.241.45.20) 1 107.1.83.229 [AS 7922] 24 msec 0 msec 0 msec 2 te-0-11-0-7-ar01.taylor.mi.michigan.comcast.net (69.139.254.77) [AS 33668] 12 msec 12 msec 12 msec 3 pos-1-14-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.181) [AS 7922] 16 msec 16 msec 16 msec 4 pos-0-7-0-0-ar01.westchester.pa.bo.comcast.net (68.86.91.214) [AS 7922] 20 msec 20 msec pos-1-8-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.88.50) [AS 7922] 20 msec 5 pos-4-6-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.88.153) [AS 7922] 28 msec 32 msec 32 msec 6 te-7-1-ar01.philadelphia.pa.bo.comcast.net (68.86.93.14) [AS 7922] 28 msec 32 msec ext-ssl02.westchester.pa.bo.comcast.net (76.96.69.6) [AS 7922] 20 msec 7 te-1-1-ar02.philadelphia.pa.bo.comcast.net (68.85.215.178) [AS 7922] 32 msec 28 msec 32 msec 8 * * * 9 te-0-3-0-2-ar01.westchester.pa.bo.comcast.net (68.86.228.110) [AS 7922] 28 msec 32 msec 28 msec 10 * * te-4-1-ur07.westchester.pa.bo.comcast.net (68.85.215.146) [AS 7922] 28 msec 11 ext-ssl02.westchester.pa.bo.comcast.net (76.96.69.6) [AS 7922] 32 msec * !H Concast-Edge> -Bill
-----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Andy Ringsmuth Sent: Friday, June 22, 2012 2:06 PM To: John Neiberger Cc: outages@outages.org Subject: Re: [outages] Comcast - East Coast issues ?
Traceroute from Lincoln, Nebraska:
(My connection is via Unite Private Networks fiber)
Last login: Thu Jun 21 20:52:10 on console 618-Andy-Ringsmuth:~ andyring$ traceroute comcast.com traceroute: Warning: comcast.com has multiple addresses; using 69.241.45.4 traceroute to comcast.com (69.241.45.4), 64 hops max, 52 byte packets 1 192.168.1.2 (192.168.1.2) 0.494 ms 0.209 ms 0.219 ms 2 ge1/2.224_ne_lnk_off_7606.upnllc.com (208.82.104.193) 0.662 ms 0.566 ms 0.582 ms 3 65.125.9.33 (65.125.9.33) 1.995 ms 2.543 ms 2.488 ms 4 chp-brdr-04.inet.qwest.net (67.14.8.234) 19.505 ms 19.259 ms 19.527 ms 5 63.146.26.14 (63.146.26.14) 19.556 ms 19.500 ms 19.514 ms 6 64.86.79.1 (64.86.79.1) 19.617 ms * 19.643 ms 7 173.167.59.149 (173.167.59.149) 26.930 ms 173.167.59.165 (173.167.59.165) 27.209 ms 173.167.59.169 (173.167.59.169) 31.145 ms 8 * * * 9 * * * 10 * * *
Won't pull up in a Web browser either.
Thanks, all. We're checking into it. John On Fri, Jun 22, 2012 at 12:21 PM, Bill Wichers <billw@waveform.net> wrote:
Type escape sequence to abort. Tracing the route to comcast.com (69.241.45.20)
1 107.1.83.229 [AS 7922] 24 msec 0 msec 0 msec 2 te-0-11-0-7-ar01.taylor.mi.michigan.comcast.net (69.139.254.77) [AS 33668] 12 msec 12 msec 12 msec 3 pos-1-14-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.181) [AS 7922] 16 msec 16 msec 16 msec 4 pos-0-7-0-0-ar01.westchester.pa.bo.comcast.net (68.86.91.214) [AS 7922] 20 msec 20 msec pos-1-8-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.88.50) [AS 7922] 20 msec 5 pos-4-6-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.88.153) [AS 7922] 28 msec 32 msec 32 msec 6 te-7-1-ar01.philadelphia.pa.bo.comcast.net (68.86.93.14) [AS 7922] 28 msec 32 msec ext-ssl02.westchester.pa.bo.comcast.net (76.96.69.6) [AS 7922] 20 msec 7 te-1-1-ar02.philadelphia.pa.bo.comcast.net (68.85.215.178) [AS 7922] 32 msec 28 msec 32 msec 8 * * * 9 te-0-3-0-2-ar01.westchester.pa.bo.comcast.net (68.86.228.110) [AS 7922] 28 msec 32 msec 28 msec 10 * * te-4-1-ur07.westchester.pa.bo.comcast.net (68.85.215.146) [AS 7922] 28 msec 11 ext-ssl02.westchester.pa.bo.comcast.net (76.96.69.6) [AS 7922] 32 msec * !H
We've also received a call from customer on Comcast that can't reach us. We come in from XO and our trace ends at the same point. traceroute to www.g.comcast.com (69.241.45.20), 64 hops max, 40 byte packets 1 roc-core3 (69.55.64.3) 0.537 ms 0.337 ms 0.308 ms 2 roc-edge2 (69.55.64.2) 0.522 ms 0.553 ms 0.377 ms 3 roc-edge4 (69.55.64.4) 0.475 ms 0.415 ms 0.441 ms 4 nysys-gw (69.55.69.36) 1.980 ms 1.905 ms 2.286 ms 5 66.238.116.197.ptr.us.xo.net (66.238.116.197) 8.049 ms 7.548 ms 9.537 ms 6 216.156.8.13.ptr.us.xo.net (216.156.8.13) 8.689 ms 7.299 ms 6.940 ms 7 vb1111.rar3.chicago-il.us.xo.net (216.156.0.53) 20.504 ms 22.675 ms 19.280 ms 8 * 207.88.14.194.ptr.us.xo.net (207.88.14.194) 25.729 ms 17.183 ms 9 206.111.2.206.ptr.us.xo.net (206.111.2.206) 17.062 ms 18.956 ms 16.786 ms 10 64.86.79.1 (64.86.79.1) 16.639 ms 23.481 ms 21.564 ms 11 173.167.59.161 (173.167.59.161) 27.794 ms 173.167.59.153 (173.167.59.153) 27.395 ms 34.985 ms 12 * * * On 06/22/2012 02:05 PM, Andy Ringsmuth wrote:
Traceroute from Lincoln, Nebraska:
(My connection is via Unite Private Networks fiber)
Last login: Thu Jun 21 20:52:10 on console 618-Andy-Ringsmuth:~ andyring$ traceroute comcast.com traceroute: Warning: comcast.com has multiple addresses; using 69.241.45.4 traceroute to comcast.com (69.241.45.4), 64 hops max, 52 byte packets 1 192.168.1.2 (192.168.1.2) 0.494 ms 0.209 ms 0.219 ms 2 ge1/2.224_ne_lnk_off_7606.upnllc.com (208.82.104.193) 0.662 ms 0.566 ms 0.582 ms 3 65.125.9.33 (65.125.9.33) 1.995 ms 2.543 ms 2.488 ms 4 chp-brdr-04.inet.qwest.net (67.14.8.234) 19.505 ms 19.259 ms 19.527 ms 5 63.146.26.14 (63.146.26.14) 19.556 ms 19.500 ms 19.514 ms 6 64.86.79.1 (64.86.79.1) 19.617 ms * 19.643 ms 7 173.167.59.149 (173.167.59.149) 26.930 ms 173.167.59.165 (173.167.59.165) 27.209 ms 173.167.59.169 (173.167.59.169) 31.145 ms 8 * * * 9 * * * 10 * * *
Won't pull up in a Web browser either.
--- Andy Ringsmuth (402) 304-0083 andyring@inebraska.com
On Jun 22, 2012, at 12:58 PM, John Neiberger wrote:
Yes, please post a traceroute.
Thanks, John
On Fri, Jun 22, 2012 at 11:54 AM, Brandon Applegate <brandon@burn.net> wrote:
Hello,
Having multiple customers call in about reachability - common thread is their side users are all on Comcast. Not to mention the fact that we can't even hit www.comcast.com from our network currently.
We have Level3 (Cincinnati) and Qwest (Chicago). Traceroutes from us outbound seem to prefer Qwest and then die in Comcast.
I can post traceroutes if need be - just wanted to see if anyone knew anything before I call my upstreams and wade through phone tree hell.
-- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 8779 B023 7637 CEC8 C5C6 4052 664D 7E08 3CBB 1739 "SH1-0151. This is the serial number, of our orbital gun."
_______________________________________________ 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- micah brandon netsville.com p585.232.5670
I think it's Qwest in Chicago -> Comcast. Looks like that's what Andy is using as well (edit: same router - chp-brdr-04.inet.qwest.net (67.14.8.234)) I think we are going to give Qwest a call. Here's a before: traceroute to www.comcast.com (69.241.45.20), 30 hops max, 60 byte packets 1 216.143.11.114 (216.143.11.114) 0.529 ms 0.571 ms 0.635 ms 2 G-4-8.core1-5.cncndc.net (67.208.157.69) 0.327 ms 0.382 ms 0.435 ms 3 tenG-1-1.core0-ev.cncndc.net (67.208.157.6) 0.806 ms 0.858 ms 0.895 ms 4 tenG-1-0-0.transit0-ch.cncndc.net (67.208.157.182) 8.516 ms 8.522 ms 8.522 ms 5 cer-edge-17.inet.qwest.net (63.148.112.17) 8.623 ms 8.627 ms 8.668 ms 6 chp-brdr-04.inet.qwest.net (67.14.8.234) 8.667 ms 8.630 ms 8.625 ms 7 63.146.26.14 (63.146.26.14) 7.800 ms 7.821 ms 7.804 ms 8 64.86.79.1 (64.86.79.1) 7.815 ms 7.837 ms * 9 * * * 10 * * * The I denied _7922_ inbound on Qwest, and now: traceroute to www.comcast.com (69.241.45.4), 30 hops max, 60 byte packets 1 216.143.11.114 (216.143.11.114) 0.358 ms 0.597 ms 0.676 ms 2 G-4-8.core1-5.cncndc.net (67.208.157.69) 0.339 ms 0.391 ms 0.458 ms 3 tenG-0-2-0.transit1-5.cncndc.net (67.208.157.194) 0.208 ms 0.215 ms 0.214 ms 4 xe-8-1-0.bar2.Cincinnati1.Level3.net (4.59.42.9) 0.379 ms 0.432 ms 0.430 ms 5 ae-7-7.ebr2.Atlanta2.Level3.net (4.69.136.218) 13.782 ms 13.955 ms 14.021 ms 6 ae-2-52.edge5.Atlanta2.Level3.net (4.69.150.78) 13.200 ms 13.207 ms 13.203 ms 7 4.71.252.6 (4.71.252.6) 14.621 ms 14.248 ms 14.240 ms 8 pos-4-7-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.87.85) 27.095 ms 27.092 ms 27.085 ms 9 pos-0-7-0-0-ar01.westchester.pa.bo.comcast.net (68.86.91.214) 29.653 ms 29.687 ms 29.674 ms 10 te-4-1-ur07.westchester.pa.bo.comcast.net (68.85.215.146) 29.651 ms 29.637 ms 29.570 ms 11 wwwcomcast-vip.westchester.pa.bo.comcast.net (69.241.45.4) 29.884 ms 29.725 ms 29.539 ms -- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 8779 B023 7637 CEC8 C5C6 4052 664D 7E08 3CBB 1739 "SH1-0151. This is the serial number, of our orbital gun." On Fri, 22 Jun 2012, Andy Ringsmuth wrote:
Traceroute from Lincoln, Nebraska:
(My connection is via Unite Private Networks fiber)
Last login: Thu Jun 21 20:52:10 on console 618-Andy-Ringsmuth:~ andyring$ traceroute comcast.com traceroute: Warning: comcast.com has multiple addresses; using 69.241.45.4 traceroute to comcast.com (69.241.45.4), 64 hops max, 52 byte packets 1 192.168.1.2 (192.168.1.2) 0.494 ms 0.209 ms 0.219 ms 2 ge1/2.224_ne_lnk_off_7606.upnllc.com (208.82.104.193) 0.662 ms 0.566 ms 0.582 ms 3 65.125.9.33 (65.125.9.33) 1.995 ms 2.543 ms 2.488 ms 4 chp-brdr-04.inet.qwest.net (67.14.8.234) 19.505 ms 19.259 ms 19.527 ms 5 63.146.26.14 (63.146.26.14) 19.556 ms 19.500 ms 19.514 ms 6 64.86.79.1 (64.86.79.1) 19.617 ms * 19.643 ms 7 173.167.59.149 (173.167.59.149) 26.930 ms 173.167.59.165 (173.167.59.165) 27.209 ms 173.167.59.169 (173.167.59.169) 31.145 ms 8 * * * 9 * * * 10 * * *
Won't pull up in a Web browser either.
--- Andy Ringsmuth (402) 304-0083 andyring@inebraska.com
On Jun 22, 2012, at 12:58 PM, John Neiberger wrote:
Yes, please post a traceroute.
Thanks, John
On Fri, Jun 22, 2012 at 11:54 AM, Brandon Applegate <brandon@burn.net> wrote:
Hello,
Having multiple customers call in about reachability - common thread is their side users are all on Comcast. Not to mention the fact that we can't even hit www.comcast.com from our network currently.
We have Level3 (Cincinnati) and Qwest (Chicago). Traceroutes from us outbound seem to prefer Qwest and then die in Comcast.
I can post traceroutes if need be - just wanted to see if anyone knew anything before I call my upstreams and wade through phone tree hell.
-- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 8779 B023 7637 CEC8 C5C6 4052 664D 7E08 3CBB 1739 "SH1-0151. This is the serial number, of our orbital gun."
_______________________________________________ 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
Looks good from AS53347, going through Sprint. Tracing route to 69.241.45.20 [www.wcprdf2.comcast.com] on port 80 Over a maximum of 30 hops. 1 48 ms 46 ms 51 ms 199.120.69.254 [router-core-inside.mtcnet.net] 2 48 ms 47 ms 47 ms 167.142.156.194 [sxct.movl.mtcnet.net] 3 52 ms 53 ms * 173.215.60.1 [premier.movl-mlx.fbnt.netins.net] 4 54 ms 78 ms 89 ms 167.142.64.253 [ins-kb1-te-13-2-220.kmrr.netins.net] 5 73 ms 75 ms 54 ms 167.142.67.53 [ins-kc1-et-9-2.kmrr.netins.net] 6 69 ms 68 ms 62 ms 144.223.35.225 [sl-crs2-chi-lc1-.sprintlink.net] 7 * * 1979 ms 144.232.8.186 [sl-st31-chi-0-4-0-0.sprintlink.net] 8 64 ms 68 ms 64 ms 144.232.6.102 9 * * 774 ms 68.86.84.189 [be-12-cr01.350ecermak.il.ibone.comcast.net] 10 99 ms 97 ms 119 ms 68.86.88.169 [pos-4-10-0-0-cr01.newyork.ny.ibone.comcast.net] 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * 2596 ms 98 ms 69.139.244.58 [te-0-4-0-5-ar01.westchester.pa.bo.comcast.net] 15 * * * Request timed out. 16 Destination Reached in 2355 ms. Connection established to 69.241.45.20 Trace Complete. -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Brandon Applegate Sent: Friday, June 22, 2012 12:54 PM To: outages@outages.org Subject: [outages] Comcast - East Coast issues ? Hello, Having multiple customers call in about reachability - common thread is their side users are all on Comcast. Not to mention the fact that we can't even hit www.comcast.com from our network currently. We have Level3 (Cincinnati) and Qwest (Chicago). Traceroutes from us outbound seem to prefer Qwest and then die in Comcast. I can post traceroutes if need be - just wanted to see if anyone knew anything before I call my upstreams and wade through phone tree hell. -- Brandon Applegate - CCIE 10273 PGP Key fingerprint: 8779 B023 7637 CEC8 C5C6 4052 664D 7E08 3CBB 1739 "SH1-0151. This is the serial number, of our orbital gun." _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
We have transit through AS209(Qwest/CL), AS701(VZ), and AS7018(ATT). While AS7018 peers directly with Comcast, AS209 and AS701 are only reachable from Comcast via TATA (formerly Teleglobe) AS6453. We are unable to reach any of our prefixes that have to transit AS6453. Reachable via AS209 or AS701: ============================================================== traceroute to www.exantebankbis.com (168.183.130.50), 30 hops max, 40 byte packets 1 leviathan (192.168.0.1) 0.177 ms 0.212 ms 0.211 ms 2 173-8-x-x-Minnesota.hfc.comcastbusiness.net (173.8.x.x) 0.685 ms 1.092 ms 1.424 ms 3 73.205.28.1 (73.205.28.1) 8.518 ms 9.500 ms 11.392 ms 4 te-4-2-ur02.brooklynpark.mn.minn.comcast.net (68.85.165.181) 14.241 ms 14.593 ms 14.899 ms 5 te-8-3-ur01.brooklynpark.mn.minn.comcast.net (68.87.174.25) 13.253 ms 14.487 ms 14.692 ms 6 te-0-2-0-7-ar01.crosstown.mn.minn.comcast.net (68.87.174.245) 20.913 ms 21.416 ms 21.523 ms 7 te-0-1-0-2-ar01.roseville.mn.minn.comcast.net (69.139.176.174) 17.644 ms 18.191 ms 18.185 ms 8 pos-0-13-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.94.73) 27.098 ms 22.970 ms 25.999 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * ============================================================== Reachable via AS7018: ============================================================== traceroute to custinst3.exantebankbis.com (168.183.144.100), 30 hops max, 40 byte packets 1 leviathan (192.168.0.1) 0.167 ms 0.162 ms 0.200 ms 2 173-8-x-x-Minnesota.hfc.comcastbusiness.net (173.8.x.x) 0.764 ms 1.179 ms 1.407 ms 3 73.205.28.1 (73.205.28.1) 10.048 ms 11.169 ms 11.384 ms 4 te-4-2-ur01.brooklynpark.mn.minn.comcast.net (68.85.165.177) 11.570 ms 11.699 ms 11.823 ms 5 te-0-2-0-6-ar01.crosstown.mn.minn.comcast.net (68.87.174.21) 20.859 ms 21.068 ms 21.203 ms 6 te-0-1-0-0-ar01.roseville.mn.minn.comcast.net (68.87.174.2) 14.887 ms 18.349 ms 19.320 ms 7 pos-0-13-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.94.73) 26.212 ms 26.568 ms 26.501 ms 8 pos-1-2-0-0-pe01.350ecermak.il.ibone.comcast.net (68.86.86.78) 26.531 ms 66.968 ms 67.172 ms 9 192.205.37.21 (192.205.37.21) 66.352 ms 66.284 ms 66.546 ms 10 cr2.cgcil.ip.att.net (12.122.132.158) 67.642 ms 67.747 ms 68.009 ms 11 cr1.n54ny.ip.att.net (12.122.1.1) 68.480 ms 68.365 ms 68.535 ms 12 cr83.n54ny.ip.att.net (12.122.105.50) 66.645 ms 66.430 ms 66.512 ms 13 gar20.n54ny.ip.att.net (12.122.131.249) 67.271 ms 67.009 ms 42.918 ms 14 12.88.161.114 (12.88.161.114) 46.082 ms 46.853 ms 46.850 ms 15 168.183.148.29 (168.183.148.29) 46.618 ms 46.778 ms * 16 * * * 17 * * * 18 * * * 19 * * * 20 * custinst3.exantebankbis.com (168.183.144.100) 40.997 ms 46.641 ms ============================================================== My strong suspicion at this time is that it's an issue with AS6453, or at least the peering between AS7922 and AS6453. -Eric
Looks like we have connectivity again as of 14:08 CDT, although it looks like Comcast/TATA peering is now shutdown in Chicago. Traffic is now routing through Ashburn, but with 15-20% packet loss. Take the bad with the good, I guess. -Eric
Thanks for the update. Can you send me a trace of the path with packet loss? John On Fri, Jun 22, 2012 at 1:25 PM, Eric Spaeth <eric@spaethco.com> wrote:
Looks like we have connectivity again as of 14:08 CDT, although it looks like Comcast/TATA peering is now shutdown in Chicago.
Traffic is now routing through Ashburn, but with 15-20% packet loss.
Take the bad with the good, I guess.
-Eric _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
http://web.hostleasing.net/~repstein/traceroutes.jpg -- Steve Rubin ser@layer42.net Layer42 Networks http://www.layer42.net/ Expect More from A Web Solutions Provider (408)450-5742
Wise words! :) On Fri, Jun 22, 2012 at 4:54 PM, Steve Rubin <ser@layer42.net> wrote:
http://web.hostleasing.net/~repstein/traceroutes.jpg
-- Steve Rubin ser@layer42.net Layer42 Networks http://www.layer42.net/ Expect More from A Web Solutions Provider (408)450-5742
The routing issues appear to be back... At least between XO and comcast. Anyone else seeing this? On Fri, Jun 22, 2012 at 7:53 PM, John Neiberger <jneiberger@gmail.com>wrote:
Wise words! :)
On Fri, Jun 22, 2012 at 4:54 PM, Steve Rubin <ser@layer42.net> wrote:
http://web.hostleasing.net/~repstein/traceroutes.jpg
-- Steve Rubin
ser@layer42.net
Layer42 Networks http://www.layer42.net/ Expect More from A Web Solutions Provider (408)450-5742
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Yes. We are having reachability issues from Century Link in Mpls to Comcast sites. TwTelco in Mpls seems to be working. From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Metro-Inet Netops Sent: Wednesday, June 27, 2012 6:53 AM To: John Neiberger Cc: outages@outages.org Subject: Re: [outages] Comcast - East Coast issues ? The routing issues appear to be back... At least between XO and comcast. Anyone else seeing this? On Fri, Jun 22, 2012 at 7:53 PM, John Neiberger <jneiberger@gmail.com<mailto:jneiberger@gmail.com>> wrote: Wise words! :) On Fri, Jun 22, 2012 at 4:54 PM, Steve Rubin <ser@layer42.net<mailto:ser@layer42.net>> wrote:
http://web.hostleasing.net/~repstein/traceroutes.jpg
-- Steve Rubin ser@layer42.net<mailto:ser@layer42.net> Layer42 Networks http://www.layer42.net/ Expect More from A Web Solutions Provider (408)450-5742<tel:%28408%29450-5742>
_______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
Could you share an MTR or something similar with this group? Frank From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Metro-Inet Netops Sent: Wednesday, June 27, 2012 6:53 AM To: John Neiberger Cc: outages@outages.org Subject: Re: [outages] Comcast - East Coast issues ? The routing issues appear to be back... At least between XO and comcast. Anyone else seeing this? On Fri, Jun 22, 2012 at 7:53 PM, John Neiberger <jneiberger@gmail.com> wrote: Wise words! :) On Fri, Jun 22, 2012 at 4:54 PM, Steve Rubin <ser@layer42.net> wrote:
http://web.hostleasing.net/~repstein/traceroutes.jpg
-- Steve Rubin
ser@layer42.net
Layer42 Networks http://www.layer42.net/ Expect More from A Web Solutions Provider (408)450-5742 <tel:%28408%29450-5742>
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
From Minneapolis:
5 61 ms 63 ms 85 ms 67.134.59.197 6 70 ms 73 ms 73 ms 67.14.8.238 7 67 ms 73 ms 73 ms 63.146.26.14 8 71 ms 74 ms 73 ms 64.86.79.1 9 77 ms 70 ms 83 ms 173.167.59.157 10 * * * Request timed out. 11 * * * Request timed out. From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Frank Bulk Sent: Wednesday, June 27, 2012 7:10 AM To: 'Metro-Inet Netops' Cc: outages@outages.org Subject: Re: [outages] Comcast - East Coast issues ? Could you share an MTR or something similar with this group? Frank From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Metro-Inet Netops Sent: Wednesday, June 27, 2012 6:53 AM To: John Neiberger Cc: outages@outages.org Subject: Re: [outages] Comcast - East Coast issues ? The routing issues appear to be back... At least between XO and comcast. Anyone else seeing this? On Fri, Jun 22, 2012 at 7:53 PM, John Neiberger <jneiberger@gmail.com<mailto:jneiberger@gmail.com>> wrote: Wise words! :) On Fri, Jun 22, 2012 at 4:54 PM, Steve Rubin <ser@layer42.net<mailto:ser@layer42.net>> wrote:
http://web.hostleasing.net/~repstein/traceroutes.jpg
-- Steve Rubin ser@layer42.net<mailto:ser@layer42.net> Layer42 Networks http://www.layer42.net/ Expect More from A Web Solutions Provider (408)450-5742<tel:%28408%29450-5742>
_______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
participants (10)
-
Andy Ringsmuth -
Bill Wichers -
Brandon Applegate -
Dylan Ebner -
Eric Spaeth -
Frank Bulk -
John Neiberger -
Metro-Inet Netops -
Micah Brandon -
Steve Rubin