[outages] Internet Health Report

[Ujjval Karihaloo]

at this point my traceroutes are fins from denver as well - however our
upstream has informed of issues being investigated with TWTelecom who shows
up in our traceroutes
......
 6  50.58.53.181 (50.58.53.181)  0.653 ms  0.671 ms  0.645 ms
 7  den1-pr2-xe-1-0-0-0.us.twtelecom.net (66.192.242.126)  0.687 ms  0.702
ms  0.684 ms
 8  66.192.242.11 (66.192.242.11)  1.181 ms  1.164 ms  1.159 ms
 9  72.14.234.57 (72.14.234.57)  1.139 ms  1.143 ms  1.138 ms
10  216.239.46.150 (216.239.46.150)  1.369 ms 216.239.46.144
(216.239.46.144)  1.464 ms  1.422 ms
11  216.239.46.53 (216.239.46.53)  11.348 ms 72.14.239.50 (72.14.239.50)
11.321 ms 216.239.46.55 (216.239.46.55)  11.360 ms
12  216.239.46.191 (216.239.46.191)  11.344 ms  11.340 ms  11.335 ms
13  google-public-dns-a.google.com (8.8.8.8)  11.339 ms  11.445 ms  11.352
ms



Ujjval Karihaloo

CTO

IP Phone/Text Msg: +13032428610

E-Fax: +17202391690

Like SimpleSignal on *Facebook* <http://www.facebook.com/SimpleSignal>* !*

SimpleSignal Inc.

3600 S. Yosemite Street

Suite 150

Denver, CO  80237


On Thu, Nov 7, 2013 at 5:56 PM, Grant Ridder <shortdudey123 at gmail.com>wrote:

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