Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Slow hop  (Read 5193 times)

dfranke

  • Newbie
  • *
  • Posts: 2
Slow hop
« on: June 22, 2008, 05:11:30 AM »

Code: [Select]
dfranke@feanor:~$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2001:4860:0:2001::68) from 2001:470:1f04:53e::2, 30 hops max, 24 byte packets
 1  dfrankehome.tunnel.tserv3.fmt2.ipv6.he.net (2001:470:1f04:53e::1)  13.794 ms  13.457 ms  13.23 ms
 2  gige-g3-20.core1.fmt2.he.net (2001:470:0:45::1)  11.73 ms  16.719 ms  12.48 ms
 3  10gigabitethernet1-2.core1.pao1.he.net (2001:470:0:30::2)  12.983 ms  12.977 ms  13.229 ms
 4  10gigabitethernet2-4.core1.ash1.he.net (2001:470:0:35::2)  89.435 ms  90.429 ms  88.186 ms
 5  pr61.iad07.net.google.com (2001:504:0:2:0:1:5169:1)  87.933 ms !S  87.933 ms !S  88.434 ms !S

Notice the big difference in ping time between hops 3 and 4.  I'm in San Francisco using the Fremont endpoint pinging Google in Mountain View, so these packets are never leaving the Bay Area.  So why the big delay on HE's own tubes?
Logged

piojan

  • Jr. Member
  • **
  • Posts: 85
Re: Slow hop
« Reply #1 on: June 22, 2008, 05:20:55 AM »

Code: [Select]
dfranke@feanor:~$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2001:4860:0:2001::68) from 2001:470:1f04:53e::2, 30 hops max, 24 byte packets
 1  dfrankehome.tunnel.tserv3.fmt2.ipv6.he.net (2001:470:1f04:53e::1)  13.794 ms  13.457 ms  13.23 ms
 2  gige-g3-20.core1.fmt2.he.net (2001:470:0:45::1)  11.73 ms  16.719 ms  12.48 ms
 3  10gigabitethernet1-2.core1.pao1.he.net (2001:470:0:30::2)  12.983 ms  12.977 ms  13.229 ms
 4  10gigabitethernet2-4.core1.ash1.he.net (2001:470:0:35::2)  89.435 ms  90.429 ms  88.186 ms
 5  pr61.iad07.net.google.com (2001:504:0:2:0:1:5169:1)  87.933 ms !S  87.933 ms !S  88.434 ms !S

Notice the big difference in ping time between hops 3 and 4.  I'm in San Francisco using the Fremont endpoint pinging Google in Mountain View, so these packets are never leaving the Bay Area.  So why the big delay on HE's own tubes?

Form www.peeringdb.com about google
Code: [Select]
We peer IPV6 routes at AMS-IX Amsterdam, Equinix Ashburn & WIDE Toyko
4 hop is Ashburn so that's on the other side of US from Bay Area.

The difference is noticible - like 70 ms. But from Europe to US you would get >110ms.
Logged

dfranke

  • Newbie
  • *
  • Posts: 2
Re: Slow hop
« Reply #2 on: June 22, 2008, 05:28:54 AM »

Ah, ok.  I assumed I was getting routed to the Googleplex but I guess they put their ipv6 server elsewhere.
Logged