• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Extremely Slow for ipv6 website.. particularly all Google site

Started by alanho, February 25, 2011, 11:06:27 PM

Previous topic - Next topic


Recently, I can't get access to all google website (actually it is extremely slow at <1K/s)
gmail google search google code whatever.  I cannot access to he.net via ipv6 as well.
I used to be able to access these site without big performance issue but now it is virtually inaccessible.
My tunnel is using :-
ip tunnel add he-ipv6 mode sit remote ttl 64

Now I have to disable ipv6 on my windows box to get access to this site.


are you sure your tunnel is up?  if your tunnel is down, your computer doesnt know it and still thinks it has ipv6 connectivity.  it will try to resolve google over ipv6 until it times out and falls back to ipv4


I have checked the connection by pinging www.google.com and it was returning positive result (~150ms) with an ipv6 address.
However, right now I lost access to ipv6 totally. I cannot get through the tunnel anymore nor accessing any v6 address.
Since I didn't change anything on my router, I really have no idea on what's going on.


I'm experiencing similar in that over the last couple of days I've seen a definite slowness to my Google sites via IPv6.  My tunnel is working fine, so far as I can tell by pinging Google and other sites.  My average ping time to Google is ~35ms, but I've watched spikes to ~4000ms for a dozen packets or so.  The slowness manifests for me in Google Reader taking a long time, (many seconds to a minute), to refresh a subscription article list or open an article.  It's been poor enough that on several occasions I thought that the tunnel had stopped working.


I have got my ipv6 conection back...
but it is still hell slow from google..

here is my tracert result.

over a maximum of 30 hops:

  1     4 ms    <1 ms    <1 ms  2001:470:d: ... (my local ipv6)
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *      261 ms   234 ms  PR01.LAX03.google.com [2001:504:0:3:0:1:5169:1]

  5   228 ms     *        *     2001:4860::1:0:607
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17   225 ms   218 ms   240 ms  lax04s01-in-x68.1e100.net [2001:4860:8011::68]

Trace complete.

Any ideas? Thanks.