Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.




1228 posts

Uber Geek
+1 received by user: 55


Topic # 24893 5-Aug-2008 22:01
Send private message

Hey, is anyone willing to help me out by posting a couple of ping/trace routes for me?

I'm trying to determine if a recent increase in latency to a couple of my favourite game servers is due to an issue at my ISP, or because ANC has re-routed traffic to the servers. I've learned it's better to do a bit of research before logging a fault with an ISP.

The servers are:
216.6.226.83, 216.6.224.222, 216.6.232.141, 203.89.181.185 and 63.215.74.158.

Thanks
Smile




rm *
Sick of your ISP? Get a $20 credit when you try Bigpipe via this link. wink


Create new topic
2483 posts

Uber Geek
+1 received by user: 4

Trusted

  Reply # 154490 5-Aug-2008 22:31
Send private message

It's one long reply... Laughing


C:\Documents and Settings\James>ping 216.6.226.83

Pinging 216.6.226.83 with 32 bytes of data:

Reply from 216.6.226.83: bytes=32 time=240ms TTL=53
Reply from 216.6.226.83: bytes=32 time=240ms TTL=53
Reply from 216.6.226.83: bytes=32 time=240ms TTL=53
Reply from 216.6.226.83: bytes=32 time=241ms TTL=53

Ping statistics for 216.6.226.83:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 240ms, Maximum = 241ms, Average = 240ms

C:\Documents and Settings\James>ping 216.6.224.222

Pinging 216.6.224.222 with 32 bytes of data:

Reply from 216.6.224.222: bytes=32 time=252ms TTL=118
Reply from 216.6.224.222: bytes=32 time=251ms TTL=118
Reply from 216.6.224.222: bytes=32 time=250ms TTL=118
Reply from 216.6.224.222: bytes=32 time=253ms TTL=118

Ping statistics for 216.6.224.222:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 250ms, Maximum = 253ms, Average = 251ms

C:\Documents and Settings\James>ping 216.6.232.141

Pinging 216.6.232.141 with 32 bytes of data:

Reply from 216.6.232.141: bytes=32 time=205ms TTL=118
Reply from 216.6.232.141: bytes=32 time=201ms TTL=118
Reply from 216.6.232.141: bytes=32 time=204ms TTL=118
Reply from 216.6.232.141: bytes=32 time=202ms TTL=118

Ping statistics for 216.6.232.141:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 201ms, Maximum = 205ms, Average = 203ms

C:\Documents and Settings\James>ping 203.89.181.185

Pinging 203.89.181.185 with 32 bytes of data:

Reply from 203.89.181.185: bytes=32 time=43ms TTL=57
Reply from 203.89.181.185: bytes=32 time=41ms TTL=57
Reply from 203.89.181.185: bytes=32 time=44ms TTL=57
Reply from 203.89.181.185: bytes=32 time=44ms TTL=57

Ping statistics for 203.89.181.185:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 41ms, Maximum = 44ms, Average = 43ms

C:\Documents and Settings\James>ping 63.215.74.158

Pinging 63.215.74.158 with 32 bytes of data:

Reply from 63.215.74.158: bytes=32 time=206ms TTL=120
Reply from 63.215.74.158: bytes=32 time=211ms TTL=120
Reply from 63.215.74.158: bytes=32 time=204ms TTL=120
Reply from 63.215.74.158: bytes=32 time=200ms TTL=120

Ping statistics for 63.215.74.158:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 200ms, Maximum = 211ms, Average = 205ms



C:\Documents and Settings\James>tracert 216.6.226.83

Tracing route to 216.6.226.83 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  10.1.1.1
  2    44 ms    49 ms    54 ms  lo1.akl-grafton-bras1.ihug.net [203.109.128.90]
  3    40 ms    40 ms    39 ms  gi2-31.akl-grafton-bdr2.ihug.net [203.109.129.102]
  4    41 ms    43 ms    41 ms  et4-110.akl-grafton-edge1.ihug.net [203.109.130.141]
  5    40 ms    40 ms    41 ms  ip-static-202-147-45-73.asianetcom.net [202.147.45.73]
  6    40 ms    42 ms    43 ms  ip-static-202-147-45-73.asianetcom.net [202.147.45.73]
  7   220 ms   223 ms   221 ms  po0-0.gw1.sjc1.asianetcom.net [202.147.50.129]
  8   200 ms   193 ms   211 ms  eqix-peer.sjc01.mzima.net [206.223.116.62]
  9   208 ms   196 ms   195 ms  xe0-0.cr02.sjc02.mzima.net [216.193.255.221]
 10   273 ms   268 ms   273 ms  eos0-23.cr01.dfw01.mzima.net [216.193.255.158]
 11   269 ms   275 ms   271 ms  ge0-ubiquity.cust.dfw01.mzima.net [72.37.178.34]
 12   273 ms   268 ms   270 ms  69.147.241.2
 13   240 ms   244 ms   240 ms  216.6.226.83

Trace complete.

C:\Documents and Settings\James>tracert 216.6.224.222

Tracing route to 216.6.224.222 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.1.1.1
  2    55 ms    43 ms    51 ms  lo1.akl-grafton-bras1.ihug.net [203.109.128.90]
  3    41 ms    39 ms    45 ms  gi2-32.akl-grafton-bdr2.ihug.net [203.109.129.234]
  4    40 ms    43 ms    41 ms  et4-110.akl-grafton-edge1.ihug.net [203.109.130.141]
  5    40 ms    40 ms    40 ms  ip-static-202-147-45-73.asianetcom.net [202.147.45.73]
  6    40 ms    40 ms    41 ms  ip-static-202-147-45-73.asianetcom.net [202.147.45.73]
  7   194 ms   192 ms   193 ms  po8-3.gw1.sjc1.asianetcom.net [202.147.55.206]
  8   169 ms   175 ms   164 ms  eqix-peer.sjc01.mzima.net [206.223.116.62]
  9   167 ms   177 ms   165 ms  xe0-0.cr02.sjc02.mzima.net [216.193.255.221]
 10   247 ms   251 ms   272 ms  eos0-19.cr01.ord01.mzima.net [216.193.255.153]
 11   243 ms   243 ms   242 ms  ge1-ubiquity.cust.ord01.mzima.net [72.37.148.166]
 12   251 ms   257 ms   250 ms  216.6.224.222

Trace complete.

C:\Documents and Settings\James>tracert 216.6.232.141

Tracing route to 216.6.232.141 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.1.1.1
  2    52 ms    46 ms    50 ms  lo1.akl-grafton-bras1.ihug.net [203.109.128.90]
  3    47 ms    39 ms    41 ms  gi2-31.akl-grafton-bdr2.ihug.net [203.109.129.102]
  4    41 ms    41 ms    40 ms  et4-110.akl-grafton-edge1.ihug.net [203.109.130.141]
  5    49 ms    41 ms    40 ms  ip-static-202-147-45-73.asianetcom.net [202.147.45.73]
  6    41 ms    39 ms    43 ms  ip-static-202-147-45-73.asianetcom.net [202.147.45.73]
  7   191 ms   192 ms   197 ms  po8-3.gw1.sjc1.asianetcom.net [202.147.55.206]
  8   171 ms   172 ms   177 ms  eqix-peer.sjc01.mzima.net [206.223.116.62]
  9   179 ms   177 ms   166 ms  xe0-0.cr02.sjc02.mzima.net [216.193.255.221]
 10   201 ms   214 ms   214 ms  eos2-22.cr01.lax02.mzima.net [216.193.255.162]
 11   205 ms   206 ms   202 ms  ge0-2.cr01.lax04.mzima.net [216.193.255.230]
 12   211 ms   204 ms   201 ms  ge0-ubiquity.cust.lax04.mzima.net [72.37.172.166]
 13   205 ms   201 ms   202 ms  216.6.232.141

Trace complete.

C:\Documents and Settings\James>tracert 203.89.181.185

Tracing route to ns-newzealand.internet.bs [203.89.181.185]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.1.1
  2    48 ms    47 ms    50 ms  lo1.akl-grafton-bras1.ihug.net [203.109.128.90]
  3    41 ms    39 ms    39 ms  gi2-32.akl-grafton-bdr2.ihug.net [203.109.129.234]
  4    40 ms    39 ms    39 ms  gi1-15.akl-grafton-bdr1.ihug.net [203.109.130.76]
  5    40 ms    42 ms    41 ms  et4-130.akl-grafton-edge2.ihug.net [203.109.130.250]
  6    41 ms    41 ms    40 ms  maxnet1.ape.net.nz [192.203.154.86]
  7    41 ms    41 ms    41 ms  maxnet1.ape.net.nz [192.203.154.86]
  8    40 ms    40 ms    40 ms  gi5-1.hsa1.alb.maxnet.net.nz [123.100.64.131]
  9    50 ms    42 ms    44 ms  bo0-966.akmn1-br1.webhost.co.nz [202.89.49.117]
 10    41 ms    50 ms    44 ms  ln-32-2.openhost.net.nz [119.47.118.14]
 11    47 ms    40 ms    42 ms  ns-newzealand.internet.bs [203.89.181.185]

Trace complete.

C:\Documents and Settings\James>tracert 63.215.74.158

Tracing route to 63.215.74.158 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.1.1.1
  2    51 ms    45 ms    47 ms  lo1.akl-grafton-bras1.ihug.net [203.109.128.90]
  3    39 ms    41 ms    39 ms  gi2-31.akl-grafton-bdr2.ihug.net [203.109.129.102]
  4    40 ms    44 ms    40 ms  et4-110.akl-grafton-edge1.ihug.net [203.109.130.141]
  5    41 ms    41 ms    46 ms  ip-static-202-147-45-73.asianetcom.net [202.147.45.73]
  6    40 ms    41 ms    45 ms  ip-static-202-147-45-73.asianetcom.net [202.147.45.73]
  7   200 ms   195 ms   191 ms  po8-3.gw1.sjc1.asianetcom.net [202.147.55.206]
  8   164 ms   171 ms   164 ms  po1-0.gw2.sjc1.asianetcom.net [202.147.50.166]
  9   196 ms   195 ms   200 ms  unknown.Level3.net [64.152.102.57]
 10   203 ms   214 ms   219 ms  vlan99.csw4.SanJose1.Level3.net [4.68.18.254]
 11   198 ms   198 ms   207 ms  ae-93-93.ebr3.SanJose1.Level3.net [4.69.134.237]
 12   210 ms   201 ms   212 ms  ae-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]
 13   205 ms   213 ms   202 ms  ae-83-83.csw3.LosAngeles1.Level3.net [4.69.137.42]
 14   205 ms   200 ms   202 ms  ae-31-89.car1.LosAngeles1.Level3.net [4.68.20.131]
 15   201 ms   202 ms   201 ms  63.215.74.158

Trace complete.




Find me on Twitter!

I posted 1, 2 x 10^3 times!

44 posts

Geek


  Reply # 154498 5-Aug-2008 22:49
Send private message

Here's some. My connection (Orcon ADSL) is pretty well used and it shows in this.

I screenshotted them, then closed my cmd window and *then* found that I can't upload a PDF into a reply so this is what I've recreated and I'll redo it for you tomorrow.

Cheers


C:\Users\Dael>ping 216.6.224.222

Pinging 216.6.224.222 with 32 bytes of data:

Reply from 216.6.224.222: bytes=32 time=221ms TTL=114
Request timed out.
Reply from 216.6.224.222: bytes=32 time=223ms TTL=114
Request timed out.

Ping statistics for 216.6.224.222:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 221ms, Maximum = 223ms, Average = 222ms

C:\Users\Dael>tracert -d 216.6.232.141

Tracing route to 216.6.232.141 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  172.16.10.254
  2    67 ms    53 ms   107 ms  60.234.8.18
  3   104 ms     *        *     121.98.9.21
  4    63 ms    54 ms    52 ms  121.98.9.13
  5    85 ms    62 ms   135 ms  60.234.9.1
  6     *        *        *     Request timed out.
  7   218 ms   254 ms    75 ms  202.147.55.209
  8   483 ms     *        *     202.147.55.206
  9     *        *        *     Request timed out.
 10   204 ms   200 ms   267 ms  216.193.255.221
 11   236 ms   213 ms   216 ms  216.193.255.162
 12     *      191 ms   192 ms  216.193.255.230
 13     *      210 ms   184 ms  72.37.172.166
 14     *      193 ms   192 ms  216.6.232.141

Trace complete.

C:\Users\Dael>ping 216.6.232.141

Pinging 216.6.232.141 with 32 bytes of data:

Reply from 216.6.232.141: bytes=32 time=193ms TTL=112
Reply from 216.6.232.141: bytes=32 time=262ms TTL=112
Request timed out.
Request timed out.

Ping statistics for 216.6.232.141:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 193ms, Maximum = 262ms, Average = 227ms

C:\Users\Dael>tracert -d 203.89.181.185

Tracing route to 203.89.181.185 over a maximum of 30 hops

  1     2 ms     1 ms     1 ms  172.16.10.254
  2   105 ms    54 ms    53 ms  60.234.8.18
  3    50 ms    52 ms    61 ms  121.98.9.21
  4    50 ms    51 ms    52 ms  121.98.9.13
  5     *        *        *     Request timed out.
  6    81 ms    59 ms    53 ms  192.203.154.86
  7   178 ms   255 ms   243 ms  123.100.64.131
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10    56 ms    57 ms    74 ms  203.89.181.185

Trace complete.

C:\Users\Dael>ping 203.89.181.185

Pinging 203.89.181.185 with 32 bytes of data:

Request timed out.
Reply from 203.89.181.185: bytes=32 time=65ms TTL=56
Reply from 203.89.181.185: bytes=32 time=66ms TTL=56
Request timed out.

Ping statistics for 203.89.181.185:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 65ms, Maximum = 66ms, Average = 65ms

C:\Users\Dael>tracert -d 63.215.74.158

Tracing route to 63.215.74.158 over a maximum of 30 hops

  1     *        9 ms     1 ms  172.16.10.254
  2   130 ms    60 ms    58 ms  60.234.8.18
  3     *        *        *     Request timed out.
  4     *        *       53 ms  121.98.9.13
  5     *        *       52 ms  60.234.9.1
  6     *        *        *     Request timed out.
  7    77 ms     *       80 ms  202.147.55.209
  8   248 ms   247 ms   281 ms  202.147.55.206
  9   278 ms   262 ms     *     202.147.50.166
 10     *      314 ms   274 ms  64.152.102.129
 11     *      222 ms   198 ms  4.68.18.126
 12     *      206 ms     *     4.69.134.229
 13   208 ms     *        *     4.69.132.10
 14   213 ms   198 ms   197 ms  4.69.137.38
 15   186 ms   187 ms   234 ms  4.68.20.67
 16   208 ms   197 ms   195 ms  63.215.74.158

Trace complete.

C:\Users\Dael>ping 63.215.74.158

Pinging 63.215.74.158 with 32 bytes of data:

Request timed out.
Reply from 63.215.74.158: bytes=32 time=192ms TTL=116
Request timed out.
Reply from 63.215.74.158: bytes=32 time=375ms TTL=116

Ping statistics for 63.215.74.158:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 192ms, Maximum = 375ms, Average = 283ms

Create new topic



Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:





News »

UAV Traffic Management Trial launching today in New Zealand
Posted 12-Dec-2017 16:06


UFB connections pass 460,000
Posted 11-Dec-2017 11:26


The Warehouse Group to adopt IBM Cloud to support digital transformation
Posted 11-Dec-2017 11:22


Dimension Data peeks into digital business 2018
Posted 11-Dec-2017 10:55


2018 Cyber Security Predictions
Posted 7-Dec-2017 14:55


Global Govtech Accelerator to drive public sector innovation in Wellington
Posted 7-Dec-2017 11:21


Stuff Pix media strategy a new direction
Posted 7-Dec-2017 09:37


Digital transformation is dead
Posted 7-Dec-2017 09:31


Fake news and cyber security
Posted 7-Dec-2017 09:27


Dimension Data New Zealand strengthens cybersecurity practice
Posted 5-Dec-2017 20:27


Epson NZ launches new Expression Premium Photo range
Posted 5-Dec-2017 20:26


Eventbrite and Twickets launch integration partnership in Australia and New Zealand
Posted 5-Dec-2017 20:23


New Fujifilm macro lens lands in New Zealand
Posted 5-Dec-2017 20:16


Cyber security not being taken seriously enough
Posted 5-Dec-2017 20:13


Sony commences Android 8.0 Oreo rollout in New Zealand
Posted 5-Dec-2017 20:08



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.