What's new

Odd Loss/Choke

A Stable Carbocation

Staff member
Moderator
So my harddrive is almost dead, but for some reason I'm getting 3%-9% loss and a couple percent choke in the GO server. Both values go up as the server fills, I've had 10% loss before. At 10% it's basically unplayable. Any ideas?

Code:
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     5 ms     4 ms     9 ms  L100.LSANCA-VFTTP-89.verizon-gni.net [98.119.183
.1]
  3     9 ms     9 ms     9 ms  G1-2-0-6.LSANCA-LCR-22.verizon-gni.net [100.41.1
98.126]
  4     9 ms     9 ms    12 ms  ae10-0.LAX01-BB-RTR2.verizon-gni.net [130.81.199
.106]
  5    20 ms    19 ms    59 ms  0.xe-7-1-2.XL4.SJC7.ALTER.NET [152.63.6.49]
  6    25 ms    21 ms    24 ms  TenGigE0-5-0-6.GW6.SJC7.ALTER.NET [152.63.51.198
]
  7    24 ms    24 ms    23 ms  internap-sjc-gw.customer.alter.net [157.130.195.
90]
  8    22 ms    21 ms    21 ms  border1.t3-1-bbnet1.sje003.pnap.net [66.151.144.
27]
  9    22 ms    21 ms    21 ms  c-66-151-138-115.managed-vds.internap-sj.nfoserv
ers.com [66.151.138.115]

Trace complete.
 

IcEWoLF

Staff member
Founder
You are on a wireless router?

Anyways you will need to run a ping test when experiencing packet loss, you will need to run the following command to do so:

Code:
ping -a 66.151.138.115 -n 30
 

A Stable Carbocation

Staff member
Moderator
Not wireless.
Code:
C:\Users\Daniel>ping -a 66.151.138.115 -n 30

Pinging c-66-151-138-115.managed-vds.internap-sj.nfoservers.com [66.151.138.115]
with 32 bytes of data:
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=18ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=23ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=18ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=18ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=18ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118

Ping statistics for 66.151.138.115:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 23ms, Average = 20ms
This it?
 

IcEWoLF

Staff member
Founder
Yes, from the report above it does not show any connection loss. You will have to run that when you are experiencing packet loss. It could also be that your wireless connection just can't handle CS:GO because of the amount of data being transferred.
 

A Stable Carbocation

Staff member
Moderator
it's not wireless. Here is the first one I ran (i did two)


Code:
C:\Users\Daniel>ping -a 66.151.138.115 -n 30

Pinging c-66-151-138-115.managed-vds.internap-sj.nfoservers.c
with 32 bytes of data:
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Request timed out.
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Reply from 66.151.138.115: bytes=32 time=18ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Request timed out.
Reply from 66.151.138.115: bytes=32 time=23ms TTL=118
Reply from 66.151.138.115: bytes=32 time=18ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Reply from 66.151.138.115: bytes=32 time=23ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Request timed out.
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118

Ping statistics for 66.151.138.115:
    Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 23ms, Average = 20ms
 

A Stable Carbocation

Staff member
Moderator
it's different every time I do it. ok one sec.


Code:
C:\Users\Daniel>ping -a 66.151.138.115 -n 30

Pinging c-66-151-138-115.managed-vds.internap-sj.nfoservers.com [66.151.138.115]
with 32 bytes of data:
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=23ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=23ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=23ms TTL=118
Reply from 66.151.138.115: bytes=32 time=18ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=23ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118
Request timed out.
Request timed out.
Reply from 66.151.138.115: bytes=32 time=22ms TTL=118
Reply from 66.151.138.115: bytes=32 time=20ms TTL=118
Reply from 66.151.138.115: bytes=32 time=19ms TTL=118
Reply from 66.151.138.115: bytes=32 time=21ms TTL=118

Ping statistics for 66.151.138.115:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 23ms, Average = 20ms
 

A Stable Carbocation

Staff member
Moderator
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|          Wireless_Broadband_Router.home -    0 |  793 |  793 |    0 |    0 |    1 |    0 |
|    L100.LSANCA-VFTTP-89.verizon-gni.net -    0 |  793 |  793 |    3 |   11 |  290 |    5 |
|  G1-2-0-6.LSANCA-LCR-22.verizon-gni.net -    0 |  793 |  793 |    5 |   10 |   28 |   11 |
|    ae10-0.LAX01-BB-RTR2.verizon-gni.net -    0 |  793 |  793 |    8 |   14 |   83 |   10 |
|           0.xe-7-1-2.XL4.SJC7.ALTER.NET -    0 |  793 |  793 |   20 |   26 |   99 |   21 |
|       TenGigE0-5-0-7.GW6.SJC7.ALTER.NET -    1 |  789 |  788 |   18 |   25 |   35 |   26 |
|      internap-sjc-gw.customer.alter.net -    5 |  672 |  641 |   18 |   21 |   26 |   21 |
|     border1.t3-1-bbnet1.sje003.pnap.net -    5 |  665 |  633 |   20 |   29 |  307 |   23 |
|c-66-151-138-115.managed-vds.internap-sj.nfoservers.com -    6 |  657 |  623 |   18 |   20 |   25 |   20 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 

IcEWoLF

Staff member
Founder
I went ahead and sent the report to NFo, hopefully they can get in touch with Internap to address the issue and reroute you.
 
Top