tserv1.jnb1.he.net - Which does *local* (<50ms) connectivity?

[Meester]

Good day,

So Vumatel is rolling out in my region, and I've been checking this situation with https://atlas.ripe.net/measurements/14787598/#!probes after I've had fall outs with VoX that doesn't want to route locally to tserv1.jnb1.he.net (only via London... it's a management decision... been there for >1month ADSL side)

So it appears that the following FTTH ISPs will be scrapped from my list to cater for my IPv6 connectivity:

* Vox - already confirmed
* Cool Ideas - seems to route locally to he.net, but then the return path is via London??
* Seacom routed - Any ISP that uses Seaom predominantly (Which I guess includes Macrolan ?? ;( ) as could be seen from the RIPE probes

Any advice (and traceroute "proofs") which Vumatel FTTH ISP does local routing for the IPv6 tunnel endpoint on he.net?

Any advice which Vumatel FTTH does provide a local IPv6 tunnel end point?

 

[websquadza]

Are you going to be on Vumatel trenched or Aerial? Trenched is a L3 network, so no native IPv6 support from them yet. Best bet is to tunnel via HE (Who we peer with, so <3ms to them if you're based in Joburg). If you're on Aerial, we support IPv6 natively via PPPoE.

 

[Meester]

Well... they trench *and* do aerial in our area, but then I'll be in a complex with trenched connection, so you tell me which I'll get
Im "happy" to do the he.net tunnel, as I currently do it via ADSL, just painfull with Vox that doesn't route locally, so I have multiple ISPs on ADSL for that, and the reason I'm asking, so lets see what Vumatel will deploy for us.

 

[websquadza]

Thanks for the quick reply. Drop our activations team an email (or me a PM) and they'll check for you.

The HE tunnel works well over trenched, here it is running on a Vuma Trenched line in JHB:

V4 to HE:

traceroute to tserv1.jnb1.he.net (216.66.87.134), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  2.401 ms  1.219 ms  1.110 ms
 2  as-vuma.jb-is-bry-01.za.ws.net.za (160.119.239.129)  3.467 ms  3.191 ms  4.067 ms
 3  core.vuma-l3.jb1.za.ws.net.za (160.119.224.97)  3.920 ms  5.706 ms  4.129 ms
 4  core.as-02.jb1.za.ws.net.za (160.119.224.89)  2.886 ms  18.073 ms  2.829 ms
 5  core.cr-01.jb1.za.ws.net.za (160.119.224.29)  2.974 ms  2.908 ms  2.785 ms
 6  ixp-xe-4000.pe-ix01.jb1.za.ws.net.za (160.119.224.19)  2.878 ms  3.501 ms  3.120 ms
 7  he.ixp.joburg (196.60.8.42)  3.038 ms  3.102 ms  3.104 ms
 8  tserv1.jnb1.he.net (216.66.87.134)  2.876 ms  3.031 ms  2.941 ms

V6 Trace:

traceroute6 to 2600:: (2600::) from 2001:470:1f23:192:dd5:2190:b83:fd09, 64 hops max, 12 byte packets
 1  2001:470:1f23:192::1  14.612 ms  1.288 ms  1.335 ms
 2  tunnel518146.tunnel.tserv1.jnb1.ipv6.he.net  3.114 ms  3.367 ms  2.965 ms
 3  10ge11-15.core1.jnb1.he.net  2.824 ms  2.814 ms  2.790 ms
 4  10ge3-11.core1.lon2.he.net  159.346 ms  179.424 ms  159.749 ms
 5  100ge13-2.core1.nyc4.he.net  228.705 ms  226.381 ms  226.304 ms
 6  100ge11-1.core1.nyc5.he.net  226.294 ms  334.606 ms  226.936 ms
 7  sprint.tienyc.telxgroup.net  228.614 ms  229.311 ms  227.702 ms
 8  sl-crs1-rly-be11.v6.sprintlink.net  259.493 ms  232.289 ms  234.134 ms
 9  sl-crs1-dc-be2.v6.sprintlink.net  241.196 ms  306.909 ms  307.093 ms
10  sl-crs1-ffx-be8.v6.sprintlink.net  306.527 ms  250.206 ms  247.741 ms
11  sl-crs1-orl-be12.v6.sprintlink.net  251.599 ms  255.035 ms  251.200 ms
12  2600:3:2000:2::69  253.045 ms  354.233 ms  253.273 ms
13  www.sprint.net  254.605 ms  253.952 ms  396.853 ms

Thanks