I found that AWS's advertised 44.192.0.0/16 was overstated — probing across the range confirmed only 44.192.100.100 was actually reachable. TransitAS had independently flagged this, and my own testing validated their claim. I removed the /16 and installed a /32 for the single reachable host, since advertising a /16 with only one live host would constitute a route hijack, and the RPKI ROA permits up to /24. I also validated all three TransitAS customer prefixes against IRR/RPKI records (two RIPE-verified, one AltDB but consistent with cascaded customer status) and confirmed end-to-end reachability to all TransitAS destinations. I followed Gao-Rexford policy by not re-advertising routes between peers. Final state: one corrected /32 customer route and four validated peer routes, all with confirmed connectivity.