Quote Originally Posted by Raikki View Post
You're missing the part where 204.2.229.234 is already pingable on that route:

Code:
ae-1.r00.scrmca02.us.bb.gin.ntt.net (129.250.7.31) 
xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net (129.250.195.46) 
204.2.229.234 (204.2.229.234)
Same netblock:

Code:
network:IP-Network-Block:204.2.229.0 - 204.2.229.255
And again, the final hop cant be resolved. So for all we know thats where it thinks it may have been. DNS routing tables still havent fully resolved as the final host is not live.