<h4 style="margin:0px 0px 14px;font-weight:400;padding-top:2px;line-height:22px;max-width:600px"><font size="2"><span style="background-color:rgba(255,255,255,0)">Google congestion management</span></font></h4><p style="margin:0px 0px 19px;box-sizing:border-box;max-width:600px"><font size="2"><span style="background-color:rgba(255,255,255,0)">Google can generally run peering ports at 100% capacity, with low (<1-2%) packet loss for most services. Peers should abide by the capacity augments guideline above.</span></font></p><p style="margin:0px 0px 19px;box-sizing:border-box;max-width:600px"><a href="https://peering.google.com/#/options/peering">https://peering.google.com/#/options/peering</a><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></p><p style="margin:0px 0px 19px;box-sizing:border-box;max-width:600px"><br></p><p style="margin:0px 0px 19px;box-sizing:border-box;max-width:600px">--</p><p style="margin:0px 0px 19px;box-sizing:border-box;max-width:600px">Eduardo Schoedler</p><p style="margin:0px 0px 19px;box-sizing:border-box;max-width:600px"><font size="2"><span style="background-color:rgba(255,255,255,0)"><br></span></font></p><br>Em segunda-feira, 29 de agosto de 2016, Dan White via Outages <<a href="mailto:outages@outages.org">outages@outages.org</a>> escreveu:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We are seeing packet loss to google hosts, hosted in Dallas. Any anyone seeing this?<br>
<br>
MTR output:<br>
<br>
Host Loss% Snt Last Avg Best Wrst StDev<br>
1. 10.0.2.1 0.0% 51 2.4 1.9 0.5 5.2 0.7<br>
2. <a href="http://olp-67-217-152-5.olp.net" target="_blank">olp-67-217-152-5.olp.net</a> 0.0% 51 0.4 3.7 0.3 27.8 4.9<br>
3. <a href="http://olp-67-217-158-29.olp.net" target="_blank">olp-67-217-158-29.olp.net</a> 0.0% 50 0.3 4.5 0.3 22.0 5.3<br>
4. <a href="http://olp-67-217-151-125.olp.net" target="_blank">olp-67-217-151-125.olp.net</a> 0.0% 50 0.6 4.9 0.6 33.3 6.8<br>
5. <a href="http://olp-67-217-158-30.olp.net" target="_blank">olp-67-217-158-30.olp.net</a> 0.0% 50 0.6 6.4 0.5 64.0 10.5<br>
6. <a href="http://olp-67-217-158-21.olp.net" target="_blank">olp-67-217-158-21.olp.net</a> 0.0% 50 11.4 4.4 1.1 13.6 4.1<br>
7. <a href="http://xe-8-3-0.bar2.tulsa2.level3.net" target="_blank">xe-8-3-0.bar2.tulsa2.level3.ne<wbr>t</a> 0.0% 50 1.2 2.7 1.2 27.5 5.5<br>
8. <a href="http://ae-0-11.bar1.tulsa2.level3.net" target="_blank">ae-0-11.bar1.tulsa2.level3.net</a><wbr> 0.0% 50 2.0 4.1 1.9 44.5 7.8<br>
9. <a href="http://ae-3-3.ebr4.dallas1.level3.net" target="_blank">ae-3-3.ebr4.dallas1.level3.net</a> 91.8% 50 20.5 20.5 20.5 20.5 0.0<br>
10. <a href="http://ae-8-0.ear3.dallas1.level3.net" target="_blank">ae-8-0.ear3.dallas1.level3.net</a> 93.9% 50 20.6 20.6 20.6 20.7 0.0<br>
11. google-level3-100g.dallas1.lev<wbr>e28.0% 50 20.5 20.7 20.4 29.6 1.5<br>
12. 108.170.240.193 22.0% 50 20.8 20.7 20.7 20.9 0.0<br>
13. 64.233.175.9 26.0% 50 20.7 20.7 20.7 20.8 0.0<br>
14. <a href="http://google-public-dns-a.google.com" target="_blank">google-public-dns-a.google.com</a> 24.0% 50 20.5 20.6 20.5 25.9 0.9<br>
<br>
The problematic hop appears to be either 10 or 11 (level3-100g). Compare to:<br>
<br>
Host Loss% Snt Last Avg Best Wrst StDev<br>
1. 10.0.2.1 0.0% 124 0.8 1.6 0.5 4.6 0.5<br>
2. <a href="http://olp-67-217-152-5.olp.net" target="_blank">olp-67-217-152-5.olp.net</a> 0.0% 124 3.8 4.3 0.3 29.9 5.6<br>
3. <a href="http://olp-67-217-158-29.olp.net" target="_blank">olp-67-217-158-29.olp.net</a> 0.0% 124 0.3 3.5 0.3 26.1 4.9<br>
4. <a href="http://olp-67-217-151-125.olp.net" target="_blank">olp-67-217-151-125.olp.net</a> 0.0% 124 6.6 3.3 0.6 20.0 3.7<br>
5. <a href="http://olp-67-217-158-30.olp.net" target="_blank">olp-67-217-158-30.olp.net</a> 0.0% 124 0.6 7.1 0.6 44.1 9.8<br>
6. <a href="http://olp-67-217-158-21.olp.net" target="_blank">olp-67-217-158-21.olp.net</a> 0.8% 124 11.9 4.8 1.1 14.9 4.3<br>
7. <a href="http://xe-8-3-0.bar2.tulsa2.level3.net" target="_blank">xe-8-3-0.bar2.tulsa2.level3.ne<wbr>t</a> 0.0% 123 1.3 4.0 1.1 68.3 11.3<br>
8. <a href="http://ae-0-11.bar1.tulsa2.level3.net" target="_blank">ae-0-11.bar1.tulsa2.level3.net</a><wbr> 0.8% 123 2.1 3.9 1.9 62.3 8.1<br>
9. <a href="http://ae-3-3.ebr4.dallas1.level3.net" target="_blank">ae-3-3.ebr4.dallas1.level3.net</a> 94.3% 123 20.5 20.6 20.5 20.6 0.0<br>
10. ae-2-3512.edge2.dallas1.level3<wbr>. 0.0% 123 20.4 22.1 20.3 68.0 7.1<br>
11. <a href="http://b.resolvers.level3.net" target="_blank">b.resolvers.level3.net</a> 0.0% 123 20.2 20.3 20.2 22.8 0.3<br>
<br>
-- <br>
Dan White<br>
BTC Broadband<br>
Network Admin Lead<br>
Ph 918.366.0248 (direct) main: (918)366-8000<br>
Fax 918.366.6610 email: <a>dwhite@olp.net</a><br>
<a href="http://www.btcbroadband.com" target="_blank">http://www.btcbroadband.com</a><br>
______________________________<wbr>_________________<br>
Outages mailing list<br>
<a>Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" target="_blank">https://puck.nether.net/mailma<wbr>n/listinfo/outages</a><br>
</blockquote><br><br>-- <br>Eduardo Schoedler<br>