Playstation Vue over IPv6 from Frontier Tampa Bay, FL

Fri Mar 9 05:15:11 UTC 2018

Playstation Vue is basically unusable when viewing over IPv6 from Tampa Bay
Frontier network. A little background first...

Almost all traffic from my metro area (Tampa Bay, FL) routes to Miami
first, and then continues on to the IPv4 Internet. Frontier does not have
residential IPv6 yet, so I am tunneling to the Hurricane Electric Miami POP
to get IPv6 connectivity. Point being, the tunneling does not really have
an adverse affect on latency.

That said, IPv4 streaming is great because I head down to Miami and jump
right over to Akamai for the content.

  1     4 ms     5 ms     5 ms  192.168.4.1
  2     *       18 ms     6 ms  192.168.100.1
  3     8 ms     6 ms     6 ms  47.199.160.1
  4     8 ms     9 ms     7 ms  172.99.45.80
  5    12 ms    13 ms    13 ms  ae8---0.scr02.mias.fl.frontiernet.net
[74.40.3.73]
  6    13 ms    13 ms    13 ms  ae1---0.cbr01.mias.fl.frontiernet.net
[74.40.1.126]
  7    12 ms    12 ms    12 ms  lag-101.ear3.Miami2.Level3.net [4.15.156.29]
  8    13 ms    13 ms    13 ms  NTT-level3-80G.Miami.Level3.net
[4.68.127.54]
  9    14 ms    13 ms    13 ms  ae-4.r05.miamfl02.us.bb.gin.ntt.net
[129.250.3.40]
 10    14 ms    14 ms    14 ms  a204-2-178-194.deploy.akamaitechnologies.com
[204.2.178.194]

IPv6 on the other hand, goes down to Miami, up to Ashburn, and back to
Miami.

1   clay584-1.tunnel.tserv12.mia1.ipv6.he.net
        (2001:470:4:4e5::1)        17.460   ms  17.231  ms  16.867   ms
2   10ge13-20.core1.mia1.he.net
        (2001:470:0:8c::1)         13.187   ms  13.446  ms  13.143   ms
3   100ge11-1.core1.atl1.he.net
        (2001:470:0:18d::1)        27.223   ms  31.532  ms  27.294   ms
4   100ge8-1.core1.ash1.he.net
       (2001:470:0:114::2)        45.364   ms  39.037  ms  38.893   ms
5   xe-0.equinix.asbnva01.us.bb.gin.ntt.net
        (2001:504:0:2::2914:1)     39.565   ms  39.485  ms  39.870   ms
6   ae-2.r23.asbnva02.us.bb.gin.ntt.net
        (2001:418:0:2000::115)     39.356   ms  39.249  ms  42.904   ms
7   ae-1.r20.miamfl02.us.bb.gin.ntt.net
        (2001:418:0:2000::f2)      64.380   ms  65.897  ms  64.124   ms
8   ae-1.r05.miamfl02.us.bb.gin.ntt.net
        (2001:418:0:2000::26a)     65.341   ms  65.324  ms  65.114   ms
9   ae-8.a00.miamfl02.us.bb.gin.ntt.net
        (2001:418:0:2000::166)     68.843   ms  68.839  ms  69.295   ms
10  2001:418:0:5000::929
       (2001:418:0:5000::929)     135.368  ms  84.350  ms  219.402  ms
11
g2600-1403-0015-0000-0000-0000-48f7-f02b.deploy.static.akamaitechnologies.com
(2600:1403:15::48f7:f02b)  68.629   ms  65.356  ms  65.352   ms

>From what I can see it looks that Hurricane Electric only sees this prefix
from Equinix and thus routes it up to Ashburn and back. I suppose there
could be utilization issues along the path, but the path itself seems like
it could be better and may improve streaming with PS Vue. Going halfway up
the east coast just to come back to the same city (possibly the same
facility) is not ideal.

Is there anyone on list that can see if this can be improved?

Thanks in advance,

Clay