It is not uncommon for a CMTS to show up as a local address. If you'd like another view of this, these results are FROM a service provider, TO my house:
02/12/2019 04:13:22 UTC
--------------------
MTR:
Start: Mon Dec 2 04:13:26 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 24.105.18.3 0.0% 10 0.7 5.4 0.5 47.9 14.9
3.|-- 137.221.105.16 0.0% 10 0.7 1.0 0.6 1.2 0.0
4.|-- 137.221.66.18 0.0% 10 1.3 9.0 1.0 60.6 18.8
5.|-- 137.221.83.66 0.0% 10 5.7 5.9 5.7 6.2 0.0
6.|-- 137.221.65.68 0.0% 10 5.8 14.2 5.7 53.1 17.7
7.|-- 137.221.68.32 0.0% 10 5.8 9.5 5.8 35.3 9.1
8.|-- langbbrj02-ae1.301.r2.la.cox.net 0.0% 10 5.4 7.9 5.4 29.7 7.6
9.|-- 68.1.1.170 0.0% 10 7.5 10.1 7.5 31.1 7.3
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ip70-181-109-239.oc.oc.cox.net 0.0% 10 122.2 78.3 16.7 297.4 85.6
Looking at the last result, you can clearly see there is a great deal of variance, indicating an overloaded (or misconfigured) node in the route. I had a post with a lot of other examples showing similar results.
Modem has been restarted. I'm trying to get another traceroute that shows the issue. It's intermittent and inconsistent and I'm not always home at peak hours. I'll update this again when I have some relevant results to share.
This is still an issue.
