<div dir="ltr">I would expect Verizon to be able to contact CT and figure out why they aren't passing the correct routes just as I might expect Baidu to do the same thing, I suppose. Ultimately, whose responsibility is it other than CT? That is my question. Maybe in this instance, it is common in the industry for this to be the responsibility of Baidu. That seems counterintuitive to me as it is Verizon without the proper route ultimately, but I am not an expert.<div>Certainly, I think it is incorrect to ask the customer to try to resolve these issues after bringing it to the attention of these services. If Verizon couldn't reach one of Google's edge servers, would it be Verizon or Google's responsibility to fix that if the issue were an intermediate peer failing to broadcase the correct route? I have the sneaking suspicion that Verizon might actually take some action in that instance...</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jul 21, 2022 at 9:31 AM Tom Beecher <<a href="mailto:beecher@beecher.cc">beecher@beecher.cc</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Unfortunately it seems like policy that Verizon pushes any issues that aren't internal routing issues to an external party, but surely they have a responsibility to maintain their peering and routes to external services as well.<br></blockquote><div><br></div><div>Baidu is behind CT. If CT is not passing on routes to 701 , what exactly do you expect Verizon to do about it? <br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 20, 2022 at 6:40 PM holow29 <<a href="mailto:holow29@gmail.com" target="_blank">holow29@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"></div>To follow up on this:<div>I've engaged Verizon's executive office to finally try to get to a network engineer (because I don't have a contact myself). The (proxied) response from the engineer was that they aren't receiving any announcements for these routes to AS701, and I would need to take it up with Baidu. I guess I would like to understand if that seems reasonable to people since it is my presumption that Baidu would return and say something similar (that they advertise their routes to their peers correctly and to take it up with Verizon). To me, it seems like there is clearly a failing in one of Verizon's peers where they are not advertising or accepting this route correctly, but that it would be incumbent on Verizon to do the legwork to fix it since they are the ones who know their peering agreements and have these contacts. Unfortunately it seems like policy that Verizon pushes any issues that aren't internal routing issues to an external party, but surely they have a responsibility to maintain their peering and routes to external services as well. In other words, this type of buckpassing does not seem right to me (and I've heard it from them on other routing issues before), especially given that they are the ones empowered to fix it. Any thoughts?</div><div><br></div><div>(As it happens, <a href="http://pan.baidu.com" target="_blank">pan.baidu.com</a> now resolves to an IP range that is routable by Verizon, but it could always revert, and it seems like Verizon should have these routes regardless.)</div><div><br></div><div>Thanks.<br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 24, 2022 at 7:41 AM Matthew Huff <<a href="mailto:mhuff@ox.com" target="_blank">mhuff@ox.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p class="MsoNormal">From my limited vantage point it appears that there is some issue between Verizon & Baidu. Baidu has <a href="http://182.61.0.0/16" target="_blank">182.61.0.0/16</a> registered, but is only advertising pieces of it globally (or at least from what I can see). In our tables,we are receiving
none from Verizon of the subnets that are advertised directly from Baidu (origin AS of 38365). The few within that registered range that have a different origin AS are coming to us from Verizon. For example:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.0.0/19" target="_blank">182.61.0.0/19</a> 144.121.203.141 0 46887 3356 4134 58466 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.0.0/18" target="_blank">182.61.0.0/18</a> 144.121.203.141 0 46887 6461 4134 58466 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.32.0/19" target="_blank">182.61.32.0/19</a> 144.121.203.141 0 46887 3356 4134 58466 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:red">*> <a href="http://182.61.64.0/18" target="_blank">182.61.64.0/18</a> 204.148.121.221 0 701 6453 55967 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""><span style="color:red">* <a href="http://182.61.128.0/23" target="_blank">182.61.128.0/23</a> 204.148.121.221 0 701 4134 4134 4134 4134 4134 58540 ?<u></u><u></u></span></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.130.0/24" target="_blank">182.61.130.0/24</a> 144.121.203.141 0 46887 6461 4134 23724 38365 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.130.0/23" target="_blank">182.61.130.0/23</a> 144.121.203.141 0 46887 6461 4134 58466 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.131.0/24" target="_blank">182.61.131.0/24</a> 144.121.203.141 0 46887 6461 4134 23724 38365 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.132.0/23" target="_blank">182.61.132.0/23</a> 144.121.203.141 0 46887 3356 4134 58466 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.132.0/22" target="_blank">182.61.132.0/22</a> 144.121.203.141 0 46887 6461 4134 58466 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.134.0/23" target="_blank">182.61.134.0/23</a> 144.121.203.141 0 46887 3356 4134 58466 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.136.0/22" target="_blank">182.61.136.0/22</a> 144.121.203.141 0 46887 3356 4134 58466 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.136.0/21" target="_blank">182.61.136.0/21</a> 144.121.203.141 0 46887 6461 4134 58466 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.140.0/22" target="_blank">182.61.140.0/22</a> 144.121.203.141 0 46887 3356 4134 58466 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.144.0/21" target="_blank">182.61.144.0/21</a> 144.121.203.141 0 46887 3356 4134 58466 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.144.0/20" target="_blank">182.61.144.0/20</a> 144.121.203.141 0 46887 6461 4134 58466 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New";color:red">*> <a href="http://182.61.160.0/19" target="_blank">182.61.160.0/19</a> 204.148.121.221 0 701 6453 55967 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.192.0/23" target="_blank">182.61.192.0/23</a> 144.121.203.141 0 46887 3356 4134 58540 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.194.0/23" target="_blank">182.61.194.0/23</a> 144.121.203.141 0 46887 3356 4134 58540 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.200.0/22" target="_blank">182.61.200.0/22</a> 144.121.203.141 0 46887 6461 4134 23724 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.200.0/21" target="_blank">182.61.200.0/21</a> 144.121.203.141 0 46887 6461 4134 58466 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.216.0/21" target="_blank">182.61.216.0/21</a> 144.121.203.141 0 46887 6461 4134 58466 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.223.0/24" target="_blank">182.61.223.0/24</a> 144.121.203.141 0 46887 6461 4134 58466 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">*> <a href="http://182.61.224.0/19" target="_blank">182.61.224.0/19</a> 144.121.203.141 0 46887 6461 4134 58466 38365 38365 i<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">We are getting the <a href="http://182.61.200.0/21" target="_blank">182.61.200.0/21</a> and <a href="http://182.61.200.0/22" target="_blank">182.61.200.0/22</a> from all of our other peers:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">asr-inet2#sh ip bgp <a href="http://182.61.200.0/21" target="_blank">182.61.200.0/21</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">BGP routing table entry for <a href="http://182.61.200.0/21" target="_blank">182.61.200.0/21</a>, version 15779018<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">Paths: (2 available, best #2, table default)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> Advertised to update-groups:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> 3 <u></u>
<u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> Refresh Epoch 1<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> 54004 6128 1299 4134 58466 38365 38365, (aggregated by 38365 119.75.208.225)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> 148.77.99.201 from 148.77.99.201 (24.157.4.25)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> Origin IGP, localpref 100, valid, external, atomic-aggregate<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> rx pathid: 0, tx pathid: 0<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> Updated on Apr 29 2022 21:02:05 EDT<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> Refresh Epoch 1<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> 46887 6461 4134 58466 38365 38365, (aggregated by 38365 119.75.208.225)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> 129.77.17.254 from 129.77.17.254 (129.77.40.7)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> Origin IGP, metric 0, localpref 100, valid, internal, atomic-aggregate, best<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> rx pathid: 0, tx pathid: 0x0<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""> Updated on May 3 2022 04:02:50 EDT<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New""><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-family:"Courier New"">From:</span></b><span style="font-family:"Courier New""> NANOG <nanog-bounces+mhuff=<a href="mailto:ox.com@nanog.org" target="_blank">ox.com@nanog.org</a>>
<b>On Behalf Of </b>holow29<br>
</span><b>Sent:</b> Thursday, June 23, 2022 5:49 PM<br>
<b>To:</b> <a href="mailto:nanog@nanog.org" target="_blank">nanog@nanog.org</a><br>
<b>Subject:</b> Verizon no BGP route to some of AS38365 (<a href="http://182.61.200.0/24" target="_blank">182.61.200.0/24</a>)<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">I've been trying (to no avail) for over a month now to get Verizon to investigate their lack of BGP routing to
<a href="http://182.61.200.0/24" target="_blank">182.61.200.0/24</a>, which hosts Baidu Wangpan at
<a href="http://pan.baidu.com" target="_blank">pan.baidu.com</a> (Baidu's cloud services/equivalent of Google Drive).<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Easily verified through Verizon's Looking Glass.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">We all know Verizon's BGP routing is a disaster, but does anyone have any ideas?<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</blockquote></div></div></div>
</blockquote></div>
</blockquote></div>