I tried two vendors without issue (firefox 5 + IE 9). The only nuance I
saw is the "enter" key didn't work in IE9 for when I entered in the domain
to initiate the traceroute. Clicking "run test" instead works fine.
On Tue, Sep 20, 2011 at 2:41 PM, Scott Weeks wrote:
>
>
> --- paul4...@gmail.
--- paul4...@gmail.com wrote:
From: PC
You can traceroute from all their POPS here if you'd like:
https://kai02.centurylink.com/PtapRpts/Public/BackboneReport.aspx
-
Hmmm, it seems to work with only one vendor's browser. Anyone else notice that?
On 20 September 2011 14:24, PC wrote:
> Having said that, that IP has similar horrible latency from my non-qwest
> connection. Additionally, google does not resolve to that IP for me, which
> is expected. It does look like poor routing on google's network. There's
I mentioned qwest because wh
You can traceroute from all their POPS here if you'd like:
https://kai02.centurylink.com/PtapRpts/Public/BackboneReport.aspx
Having said that, that IP has similar horrible latency from my non-qwest
connection. Additionally, google does not resolve to that IP for me, which
is expected. It does l
On Tue, Sep 20, 2011 at 02:06:18PM -0500, Chris Brookes wrote:
> Anyone else seeing a lot of latency to google via qwest?
>
> ..
>
> 11 2 ms 2 ms 2 ms min-edge-12.inet.qwest.net [207.225.128.1]
> 1215 ms13 ms12 ms chx-edge-03.inet.qwest.net [67.14.38.5]
> 1312 ms
On 09/20/2011 03:06 PM, Chris Brookes wrote:
Anyone else seeing a lot of latency to google via qwest?
..
11 2 ms 2 ms 2 ms min-edge-12.inet.qwest.net [207.225.128.1]
1215 ms13 ms12 ms chx-edge-03.inet.qwest.net [67.14.38.5]
1312 ms21 ms13 ms 72.14.214.78
1
Anyone else seeing a lot of latency to google via qwest?
..
11 2 ms 2 ms 2 ms min-edge-12.inet.qwest.net [207.225.128.1]
1215 ms13 ms12 ms chx-edge-03.inet.qwest.net [67.14.38.5]
1312 ms21 ms13 ms 72.14.214.78
1413 ms13 ms13 ms 72.14.236.178
15
7 matches
Mail list logo
