Major Packetloss

Status
Not open for further replies.
Joined
Aug 10, 2015
Messages
568
Likes
136
IG Name
Jason Murray
IG Faction
San Andreas County Sheriff
#1
Getting major packet loss and heavy spikes in my ping uniquely for RCRP and I've no explanation


Code:
Running RC-RP Diagnostics test... 
Retrieving system date and time. 
07/01/2018 
12:32
 
------- Ping/Traceroute to EU.FROSTGAMING.COM -------: 

Pinging eu.frostgaming.com [185.198.188.98] with 32 bytes of data:
Reply from 185.198.188.98: bytes=32 time=10ms TTL=58
Reply from 185.198.188.98: bytes=32 time=26ms TTL=58
Reply from 185.198.188.98: bytes=32 time=11ms TTL=58
Reply from 185.198.188.98: bytes=32 time=10ms TTL=58
Reply from 185.198.188.98: bytes=32 time=9ms TTL=58
Reply from 185.198.188.98: bytes=32 time=36ms TTL=58
Reply from 185.198.188.98: bytes=32 time=9ms TTL=58
Reply from 185.198.188.98: bytes=32 time=10ms TTL=58

Ping statistics for 185.198.188.98:
    Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 36ms, Average = 15ms

Tracing route to eu.frostgaming.com [185.198.188.98]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  SkyRouter.Home [192.168.0.1] 
  2     *        *        *     Request timed out.
  3    11 ms    12 ms    13 ms  be392.pr2.hobir.isp.sky.com [2.120.9.82] 
  4    13 ms    10 ms    10 ms  ae3.cr11-lon1.ip4.gtt.net [77.67.74.93] 
  5    10 ms    10 ms    10 ms  xe-3-3-7.cr0-lon1.ip4.gtt.net [89.149.133.82] 
  6    13 ms    11 ms    10 ms  ip4.gtt.net [46.33.78.242] 
  7    45 ms    46 ms    35 ms  185.198.188.1 
  8    36 ms    11 ms    12 ms  185.198.188.3 
  9    10 ms     9 ms    10 ms  rev.srv3.eu.frostgaming.com [185.198.188.98] 

Trace complete.
 
------- Ping/Traceroute to SERVER.REDCOUNTYRP.COM -------: 

Pinging server.redcountyrp.com [185.198.188.100] with 32 bytes of data:
Reply from 185.198.188.100: bytes=32 time=9ms TTL=58
Reply from 185.198.188.100: bytes=32 time=17ms TTL=58
Reply from 185.198.188.100: bytes=32 time=36ms TTL=58
Reply from 185.198.188.100: bytes=32 time=10ms TTL=58
Reply from 185.198.188.100: bytes=32 time=10ms TTL=58
Reply from 185.198.188.100: bytes=32 time=9ms TTL=58
Reply from 185.198.188.100: bytes=32 time=9ms TTL=58
Reply from 185.198.188.100: bytes=32 time=39ms TTL=58

Ping statistics for 185.198.188.100:
    Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 39ms, Average = 17ms

Tracing route to server.redcountyrp.com [185.198.188.100]
over a maximum of 30 hops:

  1     2 ms     4 ms     2 ms  SkyRouter.Home [192.168.0.1] 
  2     *        *        *     Request timed out.
  3    31 ms    21 ms    35 ms  be392.pr2.hobir.isp.sky.com [2.120.9.82] 
  4    31 ms    12 ms    10 ms  ae3.cr11-lon1.ip4.gtt.net [77.67.74.93] 
  5    33 ms    37 ms    10 ms  xe-9-1-0.cr0-lon1.ip4.gtt.net [89.149.183.182] 
  6    11 ms    10 ms    11 ms  ip4.gtt.net [46.33.78.242] 
  7    29 ms    33 ms   160 ms  185.198.188.1 
  8    11 ms    11 ms    20 ms  185.198.188.3 
  9    13 ms     9 ms     9 ms  rev.srv5.eu.frostgaming.com [185.198.188.100] 

Trace complete.
 
------- Ping/Traceroute to GOOGLE.COM -------: 

Pinging google.com [2a00:1450:4009:80a::200e] with 32 bytes of data:
Reply from 2a00:1450:4009:80a::200e: time=29ms 
Reply from 2a00:1450:4009:80a::200e: time=11ms 
Reply from 2a00:1450:4009:80a::200e: time=10ms 
Reply from 2a00:1450:4009:80a::200e: time=16ms 

Ping statistics for 2a00:1450:4009:80a::200e:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 29ms, Average = 16ms

Tracing route to google.com [2a00:1450:4009:80a::200e]
over a maximum of 30 hops:

  1     2 ms     3 ms     1 ms  2a02:c7d:7650:a600::1 
  2     *        *        *     Request timed out.
  3    11 ms    12 ms    12 ms  2001:4860:1:1::22a 
  4    12 ms    12 ms    11 ms  2001:4860:1:1::22a 
  5   323 ms    25 ms    38 ms  2a00:1450:8000:23d::1:1 
  6    11 ms    10 ms    20 ms  lhr35s02-in-x0e.1e100.net [2a00:1450:4009:80a::200e] 

Trace complete.
 
IPconfig information: 

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DESKTOP-I34N1U1
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : Home

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Intel(R) I211 Gigabit Network Connection
   Physical Address. . . . . . . . . : 40-8D-5C-E3-15-C5
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 3:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
   Physical Address. . . . . . . . . : 16-16-F9-B0-86-2A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter WiFi 2:

   Connection-specific DNS Suffix  . : Home
   Description . . . . . . . . . . . : TP-LINK 300Mbps Wireless N Adapter #2
   Physical Address. . . . . . . . . : 84-16-F9-B0-86-2A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2a02:c7d:7650:a600:9142:7959:de37:b7e2(Preferred) 
   IPv6 Address. . . . . . . . . . . : fd12:be30:3cb9:0:9142:7959:de37:b7e2(Preferred) 
   Temporary IPv6 Address. . . . . . : 2a02:c7d:7650:a600:94c0:315d:a7cc:173a(Preferred) 
   Temporary IPv6 Address. . . . . . : fd12:be30:3cb9:0:94c0:315d:a7cc:173a(Preferred) 
   Link-local IPv6 Address . . . . . : fe80::9142:7959:de37:b7e2%9(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.0.40(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 07 January 2018 12:18:17
   Lease Expires . . . . . . . . . . : 08 January 2018 12:18:17
   Default Gateway . . . . . . . . . : fe80::c23e:fff:fee1:3b0%9
                                       192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 310646521
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-3D-A7-CE-40-8D-5C-E3-15-C5
   DNS Servers . . . . . . . . . . . : fd12:be30:3cb9:0:c23e:fff:fee1:3b0
                                       192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 13:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
 
*****Test Complete*****! 
12:33
07/01/2018
 

fr0st

SysAdmin
System Administrator
Joined
Jan 28, 2011
Messages
439
Likes
221
#2
I see some spikes to Google in the traceroute you posted. Which makes me believe this is not a server problem.

Check your connection. Reboot routers/modems, or call your ISP and ask them to check the line locally. There's nothing we can do if the problem isn't specific to us.
 
Status
Not open for further replies.