Something else you may want to look for in the future is an email report
from the puck.nether.net outages list.
On May 2, 2016 8:54 AM, "Matt Hoppes"
wrote:
> Yes yes yes, Josh :) Jeff got me the info I was looking for.
>
> On 5/2/16 9:47 AM, Josh Reynolds
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
Traffic looks normal to me from Troy OH.
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Mon, May 2, 2016 at 7:47 AM, Matt Hoppes <
mattli...@rivervalleyinternet.net> wrote:
> Is anyone else seeing major routing issues across the Frontier IP
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
>
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.
5 matches
Mail list logo