Author Topic: How to Determine whether your ISP is at fault and submitting ping reports  (Read 10563 times)

Offline Reuben

  • Chief Doraemon
  • Administrator
  • Admiral
  • *****
  • Posts: 6878
Getting WinMTR

Download this program

http://winmtr.sourceforge.net/winmtr_bin.zip

It is an open source software that helps you trace your route, show its ping times and any loss. Furthermore, it puts it in an easily readable format!

You should try pinging any of our servers' ip:

For e.g.

92.48.100.10

77.92.68.131

Just enter the IP into the 'host' section like so and run it for around 5 minutes:



Generally you want a ping of 200-500 ms to our server. Anything in the 800-1000+ ms range will definitely experience problems with our VPN. If you get poor pings, it's most likely an ISP routing problem. The program also helps you to show where the problem is. Loss rates of around 0-10% is about normal as there are many variables along the route although if you notice very high losses, there might be a problem.

Ping Reports

When giving us ping reports for us to troubleshoot, just click on 'Copy Text to Clipboard' and paste into your forum post. This will end up looking something like this and we should be able to make some findings on your report.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          219.93.218.177 -    0 |   54 |   54 |    0 |   14 |   32 |   31 |
|                          219.93.218.109 -    0 |   54 |   54 |    0 |   13 |   47 |   15 |
|               stm-odsy01-g0-1.tm.net.my -    0 |   54 |   54 |    0 |   11 |   47 |   16 |
|                            219.94.12.21 -    0 |   54 |   54 |   15 |   29 |  140 |   31 |
|                         203.106.253.229 -    0 |   54 |   54 |   31 |   39 |  234 |   31 |
|                         202.188.126.132 -    2 |   54 |   53 |   31 |   41 |  219 |  218 |
|                            58.27.124.34 -    0 |   54 |   54 |   31 |   58 |  375 |   31 |
|                           219.93.173.37 -    0 |   54 |   54 |   31 |   34 |   94 |   32 |
|                          219.93.153.150 -    2 |   54 |   53 |  218 |  236 |  406 |  235 |
|          gi-2-1.bbr01.sjc01.us.xeex.net -    6 |   53 |   50 |  234 |  247 |  313 |  250 |
|               unknown.ord01.us.xeex.net -    0 |   53 |   53 |  281 |  290 |  453 |  281 |
|                                       . -    0 |   53 |   53 |  265 |  271 |  390 |  265 |
|                           66.90.127.134 -    0 |   53 |   53 |  265 |  276 |  437 |  281 |
|                                       . -    0 |   53 |   53 |  265 |  272 |  468 |  265 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir  ( stanimir@cr.nivis.com )

If you are getting a poor ping, try getting a new IP range. An IP range in Streamyx's case are the first two digits in an IP.

124.82.x.x
60.54.x.x
60.53.x.x
118.100.x.x

are just examples of some of the IP ranges Streamyx gives.
There is NO WAY of finding out which is the best IP range without trial and error and testing on your part. This is a fault of Streamyx unfortunately.

« Last Edit: September 01, 2009, 12:20:41 PM by Reuben »
*If you like my service/support, please consider posting a positive feedback here*<3



Co-Founder/Administrator