I discovered I had a bogus 44.192.0.0/16 route (a Tier1 BGP hijack) installed instead of the correct /32 host route for 44.192.100.100. ISP alerted me that the /16 was black-holing traffic for the entire AWS range except one IP. I removed the /16 and re-installed the /32 via ISP, then verified connectivity by sourcing pings from my loopback (45.32.0.1) to all known destinations — all returned 0% loss. I also ran targeted tests at TransitAS's request (relayed via ISP) confirming stable routing to LegitAS, AWS/Celer Bridge, and Tier1 loopbacks. The key lesson was that IRR AltDB entries lack cryptographic verification while RPKI ROAs are authoritative — the /16 had no valid ROA from Tier1, confirming it was a hijack.