Recently I noticed a routing anomaly while performing traceroutes to find out why Internet connectivity has become so unstable. The results were quite consistent with 169.254.11.21 appearing as the either the second to last hop before the destination IP, or as the final hop, following the destination IP specified in the traceroute command. Everything was running smoothly before this routing bug occured and the IP 169.254.11.21 never before appeared in traceroutes. I have read the other community posts here relating to this issue, and while in those cases, this IP often appeared as the second hop in the traceroutes, one explanation provided that this is "by design" is inaccurate. I am not using the Omada cloud based controller services, and the router ports are configured per default settings (port 1/WAN) ports 2-5 LAN. I have examined the routing table and everything looks fine there. For myself this issue just started occuring recently, following almost a year of problem free operating. Connecting a laptop directly to the ISP's modem does not reproduce the issue, therefore the problem lies within the ER605. Any insight from the community, and instructions for a possible fix, would be much appreciated. Thanks.