We are seeing high latency to destinations within Frontier, but not to other locations outside Frontier: traceroute 71.102.212.201 traceroute to 71.102.212.201 (71.102.212.201), 64 hops max, 52 byte packets 1 98.112.74.1 (98.112.74.1) 4.349 ms 4.264 ms 4.855 ms 2 172.102.105.108 (172.102.105.108) 9.970 ms 12.494 ms 10.134 ms 3 ae8---0.scr02.lsan.ca.frontiernet.net (74.40.3.49) 9.833 ms 9.653 ms 10.081 ms 4 be10---0.lcr22.snlo.ca.frontiernet.net (74.40.3.54) 22.614 ms 24.705 ms 25.338 ms 5 172.102.96.195 (172.102.96.195) 24.824 ms 24.521 ms 25.280 ms 6 71.102.212.201 (71.102.212.201) 114.610 ms 134.279 ms 140.006 ms ping -s 1400 71.102.212.201 PING 71.102.212.201 (71.102.212.201): 1400 data bytes Request timeout for icmp_seq 0 1408 bytes from 71.102.212.201: icmp_seq=0 ttl=59 time=1313.874 ms 1408 bytes from 71.102.212.201: icmp_seq=1 ttl=59 time=749.040 ms 1408 bytes from 71.102.212.201: icmp_seq=2 ttl=59 time=200.203 ms 1408 bytes from 71.102.212.201: icmp_seq=3 ttl=59 time=209.519 ms 1408 bytes from 71.102.212.201: icmp_seq=4 ttl=59 time=286.727 ms 1408 bytes from 71.102.212.201: icmp_seq=5 ttl=59 time=338.709 ms 1408 bytes from 71.102.212.201: icmp_seq=6 ttl=59 time=1588.306 ms 1408 bytes from 71.102.212.201: icmp_seq=7 ttl=59 time=1627.653 ms 1408 bytes from 71.102.212.201: icmp_seq=8 ttl=59 time=1380.360 ms 1408 bytes from 71.102.212.201: icmp_seq=9 ttl=59 time=424.260 ms 1408 bytes from 71.102.212.201: icmp_seq=10 ttl=59 time=361.577 ms 1408 bytes from 71.102.212.201: icmp_seq=11 ttl=59 time=283.573 ms 1408 bytes from 71.102.212.201: icmp_seq=12 ttl=59 time=921.086 ms 1408 bytes from 71.102.212.201: icmp_seq=13 ttl=59 time=1037.984 ms 1408 bytes from 71.102.212.201: icmp_seq=14 ttl=59 time=902.649 ms traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets 1 98.112.74.1 (98.112.74.1) 6.391 ms 4.006 ms 5.330 ms 2 172.102.103.6 (172.102.103.6) 9.884 ms 6.952 ms 7.421 ms 3 ae8---0.scr01.lsan.ca.frontiernet.net (74.40.3.37) 7.531 ms 7.040 ms 10.007 ms 4 ae0---0.cbr01.lsan.ca.frontiernet.net (74.40.3.198) 7.441 ms 17.652 ms 7.147 ms 5 74.40.26.254 (74.40.26.254) 7.475 ms 6.983 ms 7.490 ms 6 216.239.59.205 (216.239.59.205) 7.468 ms 209.85.245.99 (209.85.245.99) 9.587 ms 64.233.174.37 (64.233.174.37) 7.364 ms 7 216.58.215.237 (216.58.215.237) 6.996 ms 209.85.249.221 (209.85.249.221) 7.648 ms 216.239.62.103 (216.239.62.103) 7.194 ms 8 google-public-dns-a.google.com (8.8.8.8) 7.275 ms 7.730 ms 7.039 ms ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=57 time=6.596 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=5.773 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=5.534 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=7.839 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=7.851 ms -mel beckman

On May 2, 2016, at 6:50 AM, Jeff Richmond <jeff.richmond@gmail.com> wrote:

Matt, I will ping you direct, but for the public audience, we had a hardware issue this morning that was triggered during a config change on the peering routers. Should be resolved here very shortly.

Thanks, -Jeff

...

On May 2, 2016, at 4:47 AM, Matt Hoppes <mattlists@rivervalleyinternet.net> wrote:

Is anyone else seeing major routing issues across the Frontier IP network this morning?

I have been unable to get ahold of anyone at Frontier as of yet.