API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jan 17th, 2014
66
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.76 KB | None | 0 0
raw download clone embed print report
  1.  
  2. C:\Windows\system32>ping 208.100.4.54
  3.  
  4. Pinging 208.100.4.54 with 32 bytes of data:
  5. Reply from 208.100.4.54: bytes=32 time=26ms TTL=56
  6. Reply from 208.100.4.54: bytes=32 time=26ms TTL=56
  7. Reply from 208.100.4.54: bytes=32 time=32ms TTL=56
  8. Reply from 208.100.4.54: bytes=32 time=28ms TTL=56
  9.  
  10. Ping statistics for 208.100.4.54:
  11. Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  12. Approximate round trip times in milli-seconds:
  13. Minimum = 26ms, Maximum = 32ms, Average = 28ms
  14.  
  15. C:\Windows\system32>tracert 208.100.4.54
  16.  
  17. Tracing route to lookingglass.chi.steadfast.net [208.100.4.54]
  18. over a maximum of 30 hops:
  19.  
  20. 1 2 ms 2 ms 2 ms vlan1.phub.net.cable.rogers.com [192.168.0.1]
  21. 2 10 ms 10 ms 10 ms 7.11.164.21
  22. 3 9 ms 9 ms 14 ms 66.185.89.113
  23. 4 16 ms 19 ms 16 ms 24.156.157.69
  24. 5 25 ms 16 ms 18 ms 24.156.144.134
  25. 6 27 ms 27 ms 28 ms 24.156.144.178
  26. 7 31 ms 28 ms 31 ms eqix1.chi01.steadfast.NET [206.223.119.34]
  27. 8 27 ms 30 ms 26 ms ip35.208-100-32.static.steadfastdns.net [208.100
  28. .32.35]
  29. 9 26 ms 27 ms 33 ms lookingglass.chi.steadfast.net [208.100.4.54]
  30.  
  31. Trace complete.
  32.  
  33. C:\Windows\system32>ping 68.232.169.106
  34.  
  35. Pinging 68.232.169.106 with 32 bytes of data:
  36. Reply from 68.232.169.106: bytes=32 time=24ms TTL=55
  37. Reply from 68.232.169.106: bytes=32 time=23ms TTL=55
  38. Reply from 68.232.169.106: bytes=32 time=25ms TTL=55
  39. Reply from 68.232.169.106: bytes=32 time=24ms TTL=55
  40.  
  41. Ping statistics for 68.232.169.106:
  42. Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  43. Approximate round trip times in milli-seconds:
  44. Minimum = 23ms, Maximum = 25ms, Average = 24ms
  45.  
  46. C:\Windows\system32>tracert 68.232.169.106
  47.  
  48. Tracing route to 68.232.169.106.choopa.net [68.232.169.106]
  49. over a maximum of 30 hops:
  50.  
  51. 1 2 ms 1 ms 1 ms vlan1.phub.net.cable.rogers.com [192.168.0.1]
  52. 2 8 ms 23 ms 16 ms 7.11.164.21
  53. 3 9 ms 9 ms 9 ms 67.231.221.137
  54. 4 14 ms 16 ms 14 ms 24.156.157.73
  55. 5 13 ms 14 ms 12 ms 24.153.4.150
  56. 6 16 ms 13 ms 16 ms torix.tge2-3.ar1.tor1.ca.nlayer.net [206.108.34.
  57. 53]
  58. 7 25 ms 24 ms 55 ms xe-0-1-1.cr2.ord1.us.nlayer.net [69.22.142.77]
  59. 8 28 ms * 29 ms ae2-30g.ar1.ord1.us.nlayer.net [69.31.111.138]
  60. 9 25 ms 25 ms 25 ms tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]
  61. 10 25 ms 25 ms 24 ms 68.232.169.106.choopa.net [68.232.169.106]
  62.  
  63. Trace complete.
  64.  
  65. C:\Windows\system32>ping 184.170.250.82
  66.  
  67. Pinging 184.170.250.82 with 32 bytes of data:
  68. Reply from 184.170.250.82: bytes=32 time=54ms TTL=56
  69. Reply from 184.170.250.82: bytes=32 time=53ms TTL=56
  70. Reply from 184.170.250.82: bytes=32 time=54ms TTL=56
  71. Reply from 184.170.250.82: bytes=32 time=53ms TTL=56
  72.  
  73. Ping statistics for 184.170.250.82:
  74. Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  75. Approximate round trip times in milli-seconds:
  76. Minimum = 53ms, Maximum = 54ms, Average = 53ms
  77.  
  78. C:\Windows\system32>tracert 184.170.250.82
  79.  
  80. Tracing route to speed.chi.coloat.com [184.170.250.82]
  81. over a maximum of 30 hops:
  82.  
  83. 1 2 ms 2 ms 2 ms vlan1.phub.net.cable.rogers.com [192.168.0.1]
  84. 2 10 ms 9 ms 11 ms 7.11.164.21
  85. 3 17 ms 10 ms 10 ms 69.63.254.133
  86. 4 14 ms 14 ms 19 ms pos-1-0.gw01.orvl.phub.net.cable.rogers.com [66.
  87. 185.81.158]
  88. 5 17 ms 18 ms 15 ms 24.156.144.121
  89. 6 * * * Request timed out.
  90. 7 * * * Request timed out.
  91. 8 30 ms 30 ms 41 ms xe-9-0-0.cr1.lga5.us.above.net [64.125.21.78]
  92. 9 53 ms 52 ms 74 ms ae6.cr1.ord2.us.above.net [64.125.24.34]
  93. 10 54 ms 67 ms 54 ms ae5.cr2.ord2.us.above.net [64.125.28.234]
  94. 11 53 ms 51 ms 52 ms xe-0-1-0.er2.ord2.us.above.net [64.125.25.110]
  95. 12 54 ms 66 ms 56 ms 208.185.22.158.ipyx-063453-zyo.above.net [208.18
  96. 5.22.158]
  97. 13 52 ms 53 ms 53 ms speed.chi.coloat.com [184.170.250.82]
  98.  
  99. Trace complete.
  100.  
  101. C:\Windows\system32>ping 216.52.148.4
  102.  
  103. Pinging 216.52.148.4 with 32 bytes of data:
  104. Reply from 216.52.148.4: bytes=32 time=36ms TTL=55
  105. Reply from 216.52.148.4: bytes=32 time=39ms TTL=55
  106. Reply from 216.52.148.4: bytes=32 time=37ms TTL=55
  107. Reply from 216.52.148.4: bytes=32 time=36ms TTL=55
  108.  
  109. Ping statistics for 216.52.148.4:
  110. Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  111. Approximate round trip times in milli-seconds:
  112. Minimum = 36ms, Maximum = 39ms, Average = 37ms
  113.  
  114. C:\Windows\system32>tracert 216.52.148.4
  115.  
  116. Tracing route to chicago-ventrilo.nfoservers.com [216.52.148.4]
  117. over a maximum of 30 hops:
  118.  
  119. 1 2 ms 2 ms 2 ms vlan1.phub.net.cable.rogers.com [192.168.0.1]
  120. 2 8 ms 9 ms 9 ms 7.11.164.21
  121. 3 11 ms 11 ms 16 ms 67.231.221.137
  122. 4 20 ms 18 ms 19 ms pos-1-0.gw01.clwd.phub.net.cable.rogers.com [66.
  123. 185.81.217]
  124. 5 30 ms 30 ms 31 ms 64.71.240.66
  125. 6 * * * Request timed out.
  126. 7 30 ms 31 ms 33 ms be2063.mpd22.jfk02.atlas.cogentco.com [154.54.47
  127. .57]
  128. 8 37 ms 37 ms 38 ms be2115.ccr22.ord01.atlas.cogentco.com [154.54.6.
  129. 190]
  130. 9 38 ms 38 ms 37 ms be2004.ccr21.ord03.atlas.cogentco.com [154.54.5.
  131. 10]
  132. 10 37 ms 54 ms 38 ms 38.122.180.138
  133. 11 37 ms 58 ms 60 ms border5.po1-bbnet1.chg.pnap.net [64.94.32.10]
  134. 12 37 ms 38 ms 37 ms chicago-ventrilo.nfoservers.com [216.52.148.4]
  135.  
  136. Trace complete.
  137.  
  138. C:\Windows\system32>ping 174.34.172.51
  139.  
  140. Pinging 174.34.172.51 with 32 bytes of data:
  141. Reply from 174.34.172.51: bytes=32 time=26ms TTL=55
  142. Reply from 174.34.172.51: bytes=32 time=24ms TTL=55
  143. Reply from 174.34.172.51: bytes=32 time=26ms TTL=55
  144. Reply from 174.34.172.51: bytes=32 time=25ms TTL=55
  145.  
  146. Ping statistics for 174.34.172.51:
  147. Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  148. Approximate round trip times in milli-seconds:
  149. Minimum = 24ms, Maximum = 26ms, Average = 25ms
  150.  
  151. C:\Windows\system32>tracert 174.34.172.51
  152.  
  153. Tracing route to 174.34.172.51.rdns.ubiquityservers.com [174.34.172.51]
  154. over a maximum of 30 hops:
  155.  
  156. 1 2 ms 1 ms 1 ms vlan1.phub.net.cable.rogers.com [192.168.0.1]
  157. 2 10 ms 8 ms 9 ms 7.11.164.21
  158. 3 19 ms 9 ms 9 ms 69.63.254.133
  159. 4 14 ms 11 ms 23 ms 24.156.157.73
  160. 5 12 ms 11 ms 12 ms 24.153.4.150
  161. 6 15 ms 15 ms 17 ms torix.tge2-3.ar1.tor1.ca.nlayer.net [206.108.34.
  162. 53]
  163. 7 * 26 ms 25 ms xe-0-1-1.cr2.ord1.us.nlayer.net [69.22.142.77]
  164. 8 26 ms 26 ms * ae2-30g.ar1.ord1.us.nlayer.net [69.31.111.138]
  165. 9 26 ms 25 ms 26 ms edge1.chi2.ubiquityservers.com [69.31.111.66]
  166. 10 26 ms 26 ms 25 ms 174.34.172.51.rdns.ubiquityservers.com [174.34.1
  167. 72.51]
  168.  
  169. Trace complete.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!