You can run a trace route by opening up your command prompt and typing in tracert 204.2.229.9

This is my most recent result. I blanked out my own IP, but as you can see the response time jumps up once it hits the ntt.net nodes

1 2 ms 2 ms 1 ms 10.0.0.1
2 12 ms 11 ms 10 ms xxxxxxxxxx
3 11 ms 11 ms 10 ms be160-rur02.elmhurst.il.chicago.comcast.net [96.110.163.5]
4 10 ms 10 ms 9 ms hu-0-18-0-0-sur07.elmhurst.il.chicago.comcast.net [162.151.92.141]
5 113 ms 27 ms 12 ms be-111-ar01.area4.il.chicago.comcast.net [162.151.92.121]
6 12 ms 14 ms 16 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 11 ms 12 ms 34 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 117 ms 113 ms 111 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 75 ms 68 ms 67 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 115 ms 126 ms 135 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 76 ms 68 ms 70 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 80 ms 72 ms 72 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 79 ms 73 ms 79 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 78 ms 74 ms 71 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 71 ms 71 ms * 204.2.229.234
16 76 ms 75 ms 72 ms 204.2.229.9