<div dir="ltr"><div>Looks fine from comcast in Mountain View, ca<br><br> 4 <a href="http://te-1-1-0-8-ar01.oakland.ca.sfba.comcast.net">te-1-1-0-8-ar01.oakland.ca.sfba.comcast.net</a> (68.85.155.150) 13.957 ms<br> <a href="http://te-1-1-0-7-ar01.oakland.ca.sfba.comcast.net">te-1-1-0-7-ar01.oakland.ca.sfba.comcast.net</a> (69.139.198.186) 12.183 ms<br>
<a href="http://te-1-1-0-6-ar01.oakland.ca.sfba.comcast.net">te-1-1-0-6-ar01.oakland.ca.sfba.comcast.net</a> (69.139.198.182) 24.722 ms<br> 5 <a href="http://be-100-ar01.sfsutro.ca.sfba.comcast.net">be-100-ar01.sfsutro.ca.sfba.comcast.net</a> (68.85.155.18) 12.269 ms 12.842 ms 12.166 ms<br>
6 <a href="http://he-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net">he-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net</a> (68.86.90.157) 14.999 ms 12.572 ms 15.726 ms<br> 7 <a href="http://pos-0-5-0-0-pe01.529bryant.ca.ibone.comcast.net">pos-0-5-0-0-pe01.529bryant.ca.ibone.comcast.net</a> (68.86.88.2) 16.369 ms 16.130 ms 16.226 ms<br>
8 * 66.208.228.226 (66.208.228.226) 68.816 ms *<br> 9 72.14.232.138 (72.14.232.138) 17.861 ms<br> 72.14.232.136 (72.14.232.136) 13.317 ms<br> 72.14.232.138 (72.14.232.138) 13.574 ms<br>10 209.85.250.63 (209.85.250.63) 15.775 ms 13.641 ms<br>
209.85.250.64 (209.85.250.64) 13.041 ms<br>11 216.239.49.198 (216.239.49.198) 30.271 ms 37.266 ms<br> 72.14.232.63 (72.14.232.63) 30.471 ms<br>12 72.14.233.138 (72.14.233.138) 34.050 ms<br> 72.14.233.200 (72.14.233.200) 33.475 ms 33.172 ms<br>
13 216.239.48.167 (216.239.48.167) 34.034 ms<br> 216.239.48.165 (216.239.48.165) 33.935 ms 39.507 ms<br>14 * * *<br>15 <a href="http://google-public-dns-a.google.com">google-public-dns-a.google.com</a> (8.8.8.8) 37.080 ms 34.764 ms 35.213 ms<br>
<br>~~~<br>Server: 8.8.8.8<br>Address: 8.8.8.8#53<br><br>Non-authoritative answer:<br>Name: <a href="http://google.com">google.com</a><br>Address: 74.125.239.101<br>Name: <a href="http://google.com">google.com</a><br>
Address: 74.125.239.98<br>Name: <a href="http://google.com">google.com</a><br>Address: 74.125.239.105<br>Name: <a href="http://google.com">google.com</a><br>Address: 74.125.239.100<br>Name: <a href="http://google.com">google.com</a><br>
Address: 74.125.239.102<br>Name: <a href="http://google.com">google.com</a><br>Address: 74.125.239.103<br>Name: <a href="http://google.com">google.com</a><br>Address: 74.125.239.104<br>Name: <a href="http://google.com">google.com</a><br>
Address: 74.125.239.96<br>Name: <a href="http://google.com">google.com</a><br>Address: 74.125.239.97<br>Name: <a href="http://google.com">google.com</a><br>Address: 74.125.239.110<br>Name: <a href="http://google.com">google.com</a><br>
Address: 74.125.239.99<br><br><br><br></div>-Grant<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 7, 2013 at 4:50 PM, Ujjval Karihaloo <span dir="ltr"><<a href="mailto:ujjval@simplesignal.com" target="_blank">ujjval@simplesignal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Is anyone seeing any issues as a result of identified latency in internet health report (lot of REDs and yellows in there)<br>
<br><a href="http://www.internetpulse.net/Main.aspx?xAxis=Destination&yAxis=Origin&zAxis=Metric&nAxis=Period" target="_blank">http://www.internetpulse.net/Main.aspx?xAxis=Destination&yAxis=Origin&zAxis=Metric&nAxis=Period</a><br>
<br></div>We are seeing timeouts to Google DNS servers 8.8.8.8 around 3 pm MT as well.<br><br></div>We are digging more into this to collect more data as well.<br><div><br clear="all"><div><div><div><div>Ujjval K<span><span style="color:rgb(31,73,125)"></span></span><span><span></span></span></div>
</div></div></div></div></div>
<br>_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
<br></blockquote></div><br></div>