[nuttle]

I suspect the tracert delay for 10.0.0.1 is simply trying to reverse lookup 10.0.0.1 (and other addresses along the way) to a DNS text name -- the servers to do this are on the other side of the outage and so the requests/retries to do this are timing out. The actual ping times being reported are much lower, sub-second.

Something like "tracert -d 198.101.239.6" (chiefdelphi.com) would be more interesting, since this would show the hop that it going out; when you run it when things are not out and when they are, you'll have some interesting data I think.

The whole IP address thing is at what is called "layer 3" in a stack of protocols. Bridging is "layer 2" but an outage in a layer 2 link will take out a (non-redundant) layer 3 link, so the first step is to work out where you lose layer 3 connectivity, then possibly there's a next step of diving into anything more complicated than a point-to-point link at layer 2.