Peering issue between Cogent and Tata?
We are having trouble resolving some web sites and Cogent says the issue appears to be with Tata. We can resolve the web sites from non-cogent networks. Is anyone seeing similar? Jon Miller | Chief Information Officer Bose McKinney & Evans LLP 111 Monument Circle | Suite 2700 | Indianapolis, Indiana 46204 JMiller@boselaw.com<mailto:JMiller@boselaw.com> | P 317-684-5108 | F 317-223-0608 Assistant Contact | Brad Cline | bcline@boselaw.com<mailto:bcline@boselaw.com> | P 317-684-5186 | F 317-223-0186 This message and any attachments may contain legally privileged or confidential information, and are intended only for the individual or entity identified above as the addressee. If you are not the addressee, or if this message has been addressed to you in error, you are not authorized to read, copy, or distribute this message and any attachments, and we ask that you please delete this message and attachments (including all copies) and notify the sender. Delivery of this message and any attachments to any person other than the intended recipient(s) is not intended in any way to waive confidentiality or a privilege. All personal messages express views only of the individual sender, and may not be copied or distributed without this statement.
Out of our Toronto connection to 174, I see about 30k prefixes from 174_6453_. Can you give some sample IPs you cant reach ? ---Mike On 1/10/2023 11:59 AM, Miller, Jon via Outages wrote:
We are having trouble resolving some web sites and Cogent says the issue appears to be with Tata. We can resolve the web sites from non-cogent networks. Is anyone seeing similar?
*Jon Miller**| *Chief Information Officer *Bose McKinney & Evans LLP* 111 Monument Circle*| *Suite 2700*| *Indianapolis, Indiana 46204 JMiller@boselaw.com <mailto:JMiller@boselaw.com>*| *P 317-684-5108*| *F 317-223-0608
/Assistant Contact/*/ | /*/Brad Cline /*/ | /*/bcline@boselaw.com <mailto:bcline@boselaw.com>///*/ | /*/P 317-684-5186 /*/ | /*/F 317-223-0186 /
This message and any attachments may contain legally privileged or confidential information, and are intended only for the individual or entity identified above as the addressee. If you are not the addressee, or if this message has been addressed to you in error, you are not authorized to read, copy, or distribute this message and any attachments, and we ask that you please delete this message and attachments (including all copies) and notify the sender. Delivery of this message and any attachments to any person other than the intended recipient(s) is not intended in any way to waive confidentiality or a privilege. All personal messages express views only of the individual sender, and may not be copied or distributed without this statement.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
35.209.30.41. Jon Miller | Chief Information Officer Bose McKinney & Evans LLP 111 Monument Circle | Suite 2700 | Indianapolis, Indiana 46204 JMiller@boselaw.com<mailto:JMiller@boselaw.com> | P 317-684-5108 | F 317-223-0608 Assistant Contact | Brad Cline | bcline@boselaw.com<mailto:bcline@boselaw.com> | P 317-684-5186 | F 317-223-0186 From: mike tancsa <mike@sentex.net> Sent: Tuesday, January 10, 2023 12:03 PM To: Miller, Jon <JMiller@boselaw.com>; outages@outages.org Subject: Re: [outages] Peering issue between Cogent and Tata? Out of our Toronto connection to 174, I see about 30k prefixes from 174_6453_. Can you give some sample IPs you cant reach ? ---Mike On 1/10/2023 11:59 AM, Miller, Jon via Outages wrote: We are having trouble resolving some web sites and Cogent says the issue appears to be with Tata. We can resolve the web sites from non-cogent networks. Is anyone seeing similar? Jon Miller | Chief Information Officer Bose McKinney & Evans LLP 111 Monument Circle | Suite 2700 | Indianapolis, Indiana 46204 JMiller@boselaw.com<mailto:JMiller@boselaw.com> | P 317-684-5108 | F 317-223-0608 Assistant Contact | Brad Cline | bcline@boselaw.com<mailto:bcline@boselaw.com> | P 317-684-5186 | F 317-223-0186 This message and any attachments may contain legally privileged or confidential information, and are intended only for the individual or entity identified above as the addressee. If you are not the addressee, or if this message has been addressed to you in error, you are not authorized to read, copy, or distribute this message and any attachments, and we ask that you please delete this message and attachments (including all copies) and notify the sender. Delivery of this message and any attachments to any person other than the intended recipient(s) is not intended in any way to waive confidentiality or a privilege. All personal messages express views only of the individual sender, and may not be copied or distributed without this statement. _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages<https://puck.nether.net/mailman/listinfo/outages>
That is a Route Validation issue. The IP 35.209.30.41 is part of 35.208.0.0/15 for which a ROA has been created by AS15169 to be originated by AS15169. If check the IP on the Cogent looking glass, Cogent shows that the IP is coming from AS19527 (which is not correct according to the ROA for this prefix… Kind regards, Robert Heuvel atom86 From: Outages <outages-bounces@outages.org> On Behalf Of Miller, Jon via Outages Sent: Tuesday, January 10, 2023 06:14 PM To: mike tancsa <mike@sentex.net>; outages@outages.org Subject: Re: [outages] Peering issue between Cogent and Tata? 35.209.30.41. Jon Miller | Chief Information Officer Bose McKinney & Evans LLP 111 Monument Circle | Suite 2700 | Indianapolis, Indiana 46204 JMiller@boselaw.com<mailto:JMiller@boselaw.com> | P 317-684-5108 | F 317-223-0608 Assistant Contact | Brad Cline | bcline@boselaw.com<mailto:bcline@boselaw.com> | P 317-684-5186 | F 317-223-0186 From: mike tancsa <mike@sentex.net<mailto:mike@sentex.net>> Sent: Tuesday, January 10, 2023 12:03 PM To: Miller, Jon <JMiller@boselaw.com<mailto:JMiller@boselaw.com>>; outages@outages.org<mailto:outages@outages.org> Subject: Re: [outages] Peering issue between Cogent and Tata? Out of our Toronto connection to 174, I see about 30k prefixes from 174_6453_. Can you give some sample IPs you cant reach ? ---Mike On 1/10/2023 11:59 AM, Miller, Jon via Outages wrote: We are having trouble resolving some web sites and Cogent says the issue appears to be with Tata. We can resolve the web sites from non-cogent networks. Is anyone seeing similar? Jon Miller | Chief Information Officer Bose McKinney & Evans LLP 111 Monument Circle | Suite 2700 | Indianapolis, Indiana 46204 JMiller@boselaw.com<mailto:JMiller@boselaw.com> | P 317-684-5108 | F 317-223-0608 Assistant Contact | Brad Cline | bcline@boselaw.com<mailto:bcline@boselaw.com> | P 317-684-5186 | F 317-223-0186 This message and any attachments may contain legally privileged or confidential information, and are intended only for the individual or entity identified above as the addressee. If you are not the addressee, or if this message has been addressed to you in error, you are not authorized to read, copy, or distribute this message and any attachments, and we ask that you please delete this message and attachments (including all copies) and notify the sender. Delivery of this message and any attachments to any person other than the intended recipient(s) is not intended in any way to waive confidentiality or a privilege. All personal messages express views only of the individual sender, and may not be copied or distributed without this statement. _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
Hi Robert, others, On Tue, Jan 10, 2023 at 05:23:58PM +0000, Robert Heuvel via Outages wrote:
That is a Route Validation issue.
I'm not sure it is!
The IP 35.209.30.41 is part of 35.208.0.0/15 for which a ROA has been created by AS15169 to be originated by AS15169.
If check the IP on the Cogent looking glass, Cogent shows that the IP is coming from AS19527 (which is not correct according to the ROA for this prefix…
There are two ROAs for this prefix, one authorising 15169 and the other authorising 19527: 19527: https://console.rpki-client.org/rpki.arin.net/repository/arin-rpki-ta/5e4a23... 15169: https://console.rpki-client.org/rpki.arin.net/repository/arin-rpki-ta/5e4a23... The RFC 6811 BGP route validation algorithm only requires a single (one) ROA to set the state of the route as "valid". Multiple ROAs for the same prefix do not conflict with each other. Kind regards, Job
Job, I have used the routinator client and that only shows AS15169 as being valid. R. -----Original Message----- From: Job Snijders <job@instituut.net> Sent: Tuesday, January 10, 2023 06:30 PM To: Robert Heuvel <RHeuvel@atom86.net> Cc: Miller, Jon <JMiller@boselaw.com>; mike tancsa <mike@sentex.net>; outages@outages.org Subject: Re: [outages] Peering issue between Cogent and Tata? Hi Robert, others, On Tue, Jan 10, 2023 at 05:23:58PM +0000, Robert Heuvel via Outages wrote:
That is a Route Validation issue.
I'm not sure it is!
The IP 35.209.30.41 is part of 35.208.0.0/15 for which a ROA has been created by AS15169 to be originated by AS15169.
If check the IP on the Cogent looking glass, Cogent shows that the IP is coming from AS19527 (which is not correct according to the ROA for this prefix…
There are two ROAs for this prefix, one authorising 15169 and the other authorising 19527: 19527: https://console.rpki-client.org/rpki.arin.net/repository/arin-rpki-ta/5e4a23... 15169: https://console.rpki-client.org/rpki.arin.net/repository/arin-rpki-ta/5e4a23... The RFC 6811 BGP route validation algorithm only requires a single (one) ROA to set the state of the route as "valid". Multiple ROAs for the same prefix do not conflict with each other. Kind regards, Job
I stand corrected (by Job). Output from our router shows that both AS-es are valid show validation database | match 35.208.0.0/15 35.208.0.0/15-15 15169 192.168.28.28 valid * 35.208.0.0/15-15 15169 192.168.28.29 valid * 35.208.0.0/15-15 19527 192.168.28.28 valid * 35.208.0.0/15-15 19527 192.168.28.29 valid * So my interpretation of info shown by routinator is not correct. Sorry for any confusion I may have caused! R. -----Original Message----- From: Outages <outages-bounces@outages.org> On Behalf Of Robert Heuvel via Outages Sent: Tuesday, January 10, 2023 06:34 PM To: Job Snijders <job@instituut.net> Cc: outages@outages.org Subject: Re: [outages] Peering issue between Cogent and Tata? Job, I have used the routinator client and that only shows AS15169 as being valid. R. -----Original Message----- From: Job Snijders <job@instituut.net> Sent: Tuesday, January 10, 2023 06:30 PM To: Robert Heuvel <RHeuvel@atom86.net> Cc: Miller, Jon <JMiller@boselaw.com>; mike tancsa <mike@sentex.net>; outages@outages.org Subject: Re: [outages] Peering issue between Cogent and Tata? Hi Robert, others, On Tue, Jan 10, 2023 at 05:23:58PM +0000, Robert Heuvel via Outages wrote:
That is a Route Validation issue.
I'm not sure it is!
The IP 35.209.30.41 is part of 35.208.0.0/15 for which a ROA has been created by AS15169 to be originated by AS15169.
If check the IP on the Cogent looking glass, Cogent shows that the IP is coming from AS19527 (which is not correct according to the ROA for this prefix…
There are two ROAs for this prefix, one authorising 15169 and the other authorising 19527: 19527: https://console.rpki-client.org/rpki.arin.net/repository/arin-rpki-ta/5e4a23... 15169: https://console.rpki-client.org/rpki.arin.net/repository/arin-rpki-ta/5e4a23... The RFC 6811 BGP route validation algorithm only requires a single (one) ROA to set the state of the route as "valid". Multiple ROAs for the same prefix do not conflict with each other. Kind regards, Job _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
It appears to be resolved now. Thank you all for taking a look. From: Robert Heuvel <RHeuvel@atom86.net> Sent: Tuesday, January 10, 2023 12:24 PM To: Miller, Jon <JMiller@boselaw.com>; mike tancsa <mike@sentex.net>; outages@outages.org Subject: RE: [outages] Peering issue between Cogent and Tata? That is a Route Validation issue. The IP 35.209.30.41<http://35.209.30.41> is part of 35.208.0.0/15<http://35.208.0.0/15> for which a ROA has been created by AS15169 to be originated by AS15169. If check the IP on the Cogent looking glass, Cogent shows that the IP is coming from AS19527 (which is not correct according to the ROA for this prefix… Kind regards, Robert Heuvel atom86 From: Outages <outages-bounces@outages.org> On Behalf Of Miller, Jon via Outages Sent: Tuesday, January 10, 2023 06:14 PM To: mike tancsa <mike@sentex.net>; outages@outages.org Subject: Re: [outages] Peering issue between Cogent and Tata? 35.209.30.41<http://35.209.30.41>. Jon Miller | Chief Information Officer Bose McKinney & Evans LLP 111 Monument Circle | Suite 2700 | Indianapolis, Indiana 46204 JMiller@boselaw.com<mailto:JMiller@boselaw.com> | P 317-684-5108 | F 317-223-0608 Assistant Contact | Brad Cline | bcline@boselaw.com<mailto:bcline@boselaw.com> | P 317-684-5186 | F 317-223-0186 From: mike tancsa <mike@sentex.net<mailto:mike@sentex.net>> Sent: Tuesday, January 10, 2023 12:03 PM To: Miller, Jon <JMiller@boselaw.com<mailto:JMiller@boselaw.com>>; outages@outages.org<mailto:outages@outages.org> Subject: Re: [outages] Peering issue between Cogent and Tata? Out of our Toronto connection to 174, I see about 30k prefixes from 174_6453_. Can you give some sample IPs you cant reach ? ---Mike On 1/10/2023 11:59 AM, Miller, Jon via Outages wrote: We are having trouble resolving some web sites and Cogent says the issue appears to be with Tata. We can resolve the web sites from non-cogent networks. Is anyone seeing similar? Jon Miller | Chief Information Officer Bose McKinney & Evans LLP 111 Monument Circle | Suite 2700 | Indianapolis, Indiana 46204 JMiller@boselaw.com<mailto:JMiller@boselaw.com> | P 317-684-5108 | F 317-223-0608 Assistant Contact | Brad Cline | bcline@boselaw.com<mailto:bcline@boselaw.com> | P 317-684-5186 | F 317-223-0186 This message and any attachments may contain legally privileged or confidential information, and are intended only for the individual or entity identified above as the addressee. If you are not the addressee, or if this message has been addressed to you in error, you are not authorized to read, copy, or distribute this message and any attachments, and we ask that you please delete this message and attachments (including all copies) and notify the sender. Delivery of this message and any attachments to any person other than the intended recipient(s) is not intended in any way to waive confidentiality or a privilege. All personal messages express views only of the individual sender, and may not be copied or distributed without this statement. _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages<https://puck.nether.net/mailman/listinfo/outages>
With a cogent src IP (yyz) traceroute -q1 -I 35.209.30.41 traceroute to 35.209.30.41 (35.209.30.41), 64 hops max, 48 byte packets 2 be2993.ccr21.cle04.atlas.cogentco.com (154.54.31.225) 7.238 ms 3 be2891.ccr41.dca01.atlas.cogentco.com (154.54.82.250) 18.586 ms 4 be2112.ccr41.atl01.atlas.cogentco.com (154.54.7.158) 35.174 ms 5 be2847.ccr41.atl04.atlas.cogentco.com (154.54.6.102) 35.344 ms 6 tata.atl04.atlas.cogentco.com (154.54.11.226) 35.221 ms 7 if-ae-43-2.tcore1.a56-atlanta.as6453.net (64.86.113.149) 52.854 ms 8 if-ae-27-2.tcore1.dt8-dallas.as6453.net (64.86.113.6) 53.101 ms 9 * 10 if-ae-22-2.tcore1.ct8-chicago.as6453.net (64.86.79.2) 52.747 ms 11 206.82.141.195 (206.82.141.195) 43.107 ms 12 41.30.209.35.bc.googleusercontent.com (35.209.30.41) 62.903 ms with one out of my ASN 11647 traceroute -q1 -I 35.209.30.41 traceroute to 35.209.30.41 (35.209.30.41) from 67.43.129.246, 64 hops max, 48 byte packets 2 be2993.ccr21.cle04.atlas.cogentco.com (154.54.31.225) 7.190 ms 3 be2891.ccr41.dca01.atlas.cogentco.com (154.54.82.250) 18.545 ms 4 be2112.ccr41.atl01.atlas.cogentco.com (154.54.7.158) 35.065 ms 5 be2847.ccr41.atl04.atlas.cogentco.com (154.54.6.102) 35.222 ms 6 tata.atl04.atlas.cogentco.com (154.54.11.226) 32.366 ms 7 if-ae-43-2.tcore1.a56-atlanta.as6453.net (64.86.113.149) 41.281 ms 8 if-ae-27-2.tcore1.dt8-dallas.as6453.net (64.86.113.6) 40.642 ms 9 if-ae-23-2.tcore2.ct8-chicago.as6453.net (64.86.79.120) 52.703 ms 10 if-ae-22-2.tcore1.ct8-chicago.as6453.net (64.86.79.2) 41.697 ms 11 206.82.141.195 (206.82.141.195) 51.818 ms 12 41.30.209.35.bc.googleusercontent.com (35.209.30.41) 50.296 ms On 1/10/2023 12:13 PM, Miller, Jon wrote:
35.209.30.41.
*Jon Miller**| *Chief Information Officer *Bose McKinney & Evans LLP* 111 Monument Circle*| *Suite 2700*| *Indianapolis, Indiana 46204 JMiller@boselaw.com <mailto:JMiller@boselaw.com>*| *P 317-684-5108*| *F 317-223-0608
/Assistant Contact/*/ | /*/Brad Cline /*/ | /*/bcline@boselaw.com <mailto:bcline@boselaw.com>///*/ | /*/P 317-684-5186 /*/ | /*/F 317-223-0186 /
*From:* mike tancsa <mike@sentex.net> *Sent:* Tuesday, January 10, 2023 12:03 PM *To:* Miller, Jon <JMiller@boselaw.com>; outages@outages.org *Subject:* Re: [outages] Peering issue between Cogent and Tata?
Out of our Toronto connection to 174, I see about 30k prefixes from 174_6453_. Can you give some sample IPs you cant reach ?
---Mike
On 1/10/2023 11:59 AM, Miller, Jon via Outages wrote:
We are having trouble resolving some web sites and Cogent says the issue appears to be with Tata. We can resolve the web sites from non-cogent networks. Is anyone seeing similar?
*Jon Miller**| *Chief Information Officer *Bose McKinney & Evans LLP* 111 Monument Circle*| *Suite 2700*| *Indianapolis, Indiana 46204 JMiller@boselaw.com <mailto:JMiller@boselaw.com>*| *P 317-684-5108*| *F 317-223-0608
/Assistant Contact/*/ | /*/Brad Cline /*/ | /*/bcline@boselaw.com <mailto:bcline@boselaw.com>///*/ | /*/P 317-684-5186 /*/ | /*/F 317-223-0186 /
This message and any attachments may contain legally privileged or confidential information, and are intended only for the individual or entity identified above as the addressee. If you are not the addressee, or if this message has been addressed to you in error, you are not authorized to read, copy, or distribute this message and any attachments, and we ask that you please delete this message and attachments (including all copies) and notify the sender. Delivery of this message and any attachments to any person other than the intended recipient(s) is not intended in any way to waive confidentiality or a privilege. All personal messages express views only of the individual sender, and may not be copied or distributed without this statement.
_______________________________________________
Outages mailing list
Outages@outages.org
participants (4)
-
Job Snijders -
mike tancsa -
Miller, Jon -
Robert Heuvel