 | Here they are, (from behind a DSL connection)
www.broadvoice.com Pinging www.broadvoice.com [147.135.0.5] with 32 bytes of data:
Reply from 147.135.0.5: bytes=32 time=51ms TTL=114 Reply from 147.135.0.5: bytes=32 time=60ms TTL=114
Tracing route to www.broadvoice.com [147.135.0.5] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 172.21.0.1 2 23 ms 23 ms 23 ms dsl-30-1.cofs.net [68.142.30.1] 3 23 ms 23 ms 23 ms 69.25.48.97 4 24 ms 23 ms 23 ms border5.fe6-9.compofficesol-2.mia003.pnap.net [69.25.48.129] 5 24 ms 23 ms 24 ms core1.pc1.bbnet1.mia003.pnap.net [69.25.0.1] 6 23 ms 23 ms 24 ms ge-4-2.a00.miamfl02.us.ra.verio.net [130.94.195.117] 7 23 ms 23 ms 24 ms ge-1-1-0-4.r01.miamfl02.us.bb.verio.net [129.250.30.30] 8 49 ms 48 ms 138 ms p4-2-0-0.r02.asbnva01.us.bb.verio.net [129.250.5.24] 9 49 ms 49 ms 48 ms ge-1-1.a00.asbnva01.us.ra.verio.net [129.250.26.97] 10 51 ms 49 ms 49 ms ge-3-3.a00.asbnva01.us.ce.verio.net [168.143.105.98] 11 50 ms 51 ms 50 ms border1.ge3-1-bbnet1.wdc002.pnap.net [216.52.127.18] 12 50 ms 50 ms 50 ms broadvoice-1.border1.wdc002.pnap.net [216.52.127.234] 13 53 ms 50 ms 51 ms 147.135.0.5
www.rhapsody.com Pinging www.rhapsody.com [64.157.228.10] with 32 bytes of data:
Reply from 64.157.228.10: bytes=32 time=97ms TTL=237 Reply from 64.157.228.10: bytes=32 time=96ms TTL=237
Tracing route to www.rhapsody.com [64.157.228.10] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 172.21.0.1 2 23 ms 26 ms 25 ms dsl-30-1.cofs.net [68.142.30.1] 3 23 ms 24 ms 23 ms 69.25.48.97 4 29 ms 24 ms 25 ms border6.fe6-9.compofficesol-2.mia003.pnap.net [69.25.48.133] 5 25 ms 25 ms 23 ms core4.ge1-0.bbnet2.mia003.pnap.net [69.25.0.68] 6 26 ms 25 ms 25 ms so-8-3.hsa1.Miami1.Level3.net [64.156.216.9] 7 26 ms 26 ms 118 ms ge-6-0-0.mp2.Miami1.Level3.net [64.159.0.17] 8 100 ms 99 ms 100 ms as-2-0.bbr2.SanJose1.Level3.net [4.68.128.157] 9 100 ms 101 ms 99 ms ge-11-1.ipcolo2.SanJose1.Level3.net [4.68.123.106] 10 98 ms 96 ms 97 ms unknown.Level3.net [63.209.16.154] 11 97 ms 97 ms 98 ms 64.157.228.10
www.dslreports.com Pinging dslreports.com [209.123.109.175] with 32 bytes of data:
Reply from 209.123.109.175: bytes=32 time=60ms TTL=50 Reply from 209.123.109.175: bytes=32 time=59ms TTL=50
Tracing route to dslreports.com [209.123.109.175]over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 172.21.0.1 2 22 ms 23 ms 23 ms dsl-30-1.cofs.net [68.142.30.1] 3 24 ms 23 ms 24 ms 69.25.48.97 4 24 ms 23 ms 23 ms border5.fe6-9.compofficesol-2.mia003.pnap.net [69.25.48.129] 5 23 ms 23 ms 23 ms core1.pc2.bbnet2.mia003.pnap.net [69.25.0.65] 6 23 ms 23 ms 24 ms ge-0-1-0.403.ar2.MIA1.gblx.net [67.17.161.213] 7 37 ms 74 ms 47 ms so1-0-0-9953M.ar4.ATL1.gblx.net [67.17.68.234] 8 42 ms 38 ms 39 ms 57.ATM2-0.BR2.ATL5.ALTER.NET [204.255.168.137] 9 40 ms 43 ms 39 ms 0.so-2-3-0.XL1.ATL5.ALTER.NET [152.63.82.198] 10 57 ms 56 ms 57 ms 0.so-5-0-0.XL1.NYC9.ALTER.NET [152.63.0.174] 11 57 ms 57 ms 56 ms POS6-0.GW1.NYC9.ALTER.NET [152.63.99.177] 12 61 ms 63 ms 59 ms nac-nj-oc12-gw.customer.alter.net [157.130.60.182] 13 60 ms 63 ms 61 ms 0.ge-0-0-0.gbr1.oct.nac.net [209.123.11.49] 14 61 ms * 61 ms www.dslreports.com [209.123.109.175] |