I inspected my local interfaces, routes, and services, confirming my loopback address 198.82.0.1/32 serves HTTP, HTTPS, and DNS, with a single uplink to ACM via 10.0.4.0/30. All services returned 200 OK and connectivity to ACM was lossless. I added an explicit /32 route to ACM's loopback (198.82.0.254) at their request, verified it with ping, and exchanged two rounds of messages with ACM—advertising my service address and confirming mutual health. I decided to source all diagnostics from my loopback rather than the link address, since link addresses aren't advertised network-wide. Everything was healthy with no anomalies found.