What's new

Packet Loss Within RCRP Servers

Status
Not open for further replies.

Giga

Donator
Joined
Dec 4, 2010
Messages
18,981
Location
MNL
Hello,

For the past two weeks, I have been experiencing severe packet loss throughout RCRP services. This started with having timeouts almost everytime I perform operations within web services (particularly when submitting a post, editing boards on the ACP, removing someone from the UCP Faction Center), having Error 408 to be specific.

The issue then started to spread across the rest of RCRP services (TeamSpeak and SAMP Servers) where I would get severe packet loss at specific times, bearing the server unplayable for me. The ping is relatively low (for me), but the packet loss is terrible.

Code:
Running RC-RP Diagnostics test... 
Retrieving system date and time. 
Sat 07/29/2017 
08:22 PM
 
------- Ping/Traceroute to EU.FROSTGAMING.COM -------: 

Pinging eu.frostgaming.com [164.132.200.17] with 32 bytes of data:
Reply from 164.132.200.17: bytes=32 time=293ms TTL=50
Request timed out.
Reply from 164.132.200.17: bytes=32 time=298ms TTL=50
Reply from 164.132.200.17: bytes=32 time=286ms TTL=50
Reply from 164.132.200.17: bytes=32 time=296ms TTL=50
Reply from 164.132.200.17: bytes=32 time=286ms TTL=50
Reply from 164.132.200.17: bytes=32 time=301ms TTL=50
Reply from 164.132.200.17: bytes=32 time=303ms TTL=50

Ping statistics for 164.132.200.17:
    Packets: Sent = 8, Received = 7, Lost = 1 (12% loss),
Approximate round trip times in milli-seconds:
    Minimum = 286ms, Maximum = 303ms, Average = 294ms

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

  1    12 ms     7 ms     9 ms  192.168.0.1 
  2     *        *        *     Request timed out.
  3    23 ms    19 ms    23 ms  114.108.194.161 
  4    20 ms    41 ms    21 ms  130.105.0.80 
  5    22 ms    21 ms    34 ms  114.108.193.158 
  6    26 ms    23 ms    33 ms  114.108.193.157 
  7    31 ms    26 ms    20 ms  130.105.0.18 
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10   234 ms   240 ms   243 ms  chi-1-a9.il.us [198.27.73.66] 
 11     *        *        *     Request timed out.
 12   265 ms   267 ms   274 ms  be100-1319.nwk-1-a9.nj.us [198.27.73.205] 
 13   284 ms   279 ms   283 ms  be100-1295.ldn-1-a9.uk.eu [192.99.146.126] 
 14     *      281 ms     *     be10-151.rbx-g1-a9.fr.eu [91.121.215.178] 
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   288 ms   285 ms   285 ms  ns3038202.ip-164-132-200.eu [164.132.200.17] 

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

Pinging server.redcountyrp.com [178.32.108.245] with 32 bytes of data:
Reply from 178.32.108.245: bytes=32 time=287ms TTL=48
Reply from 178.32.108.245: bytes=32 time=277ms TTL=48
Request timed out.
Reply from 178.32.108.245: bytes=32 time=276ms TTL=48
Reply from 178.32.108.245: bytes=32 time=313ms TTL=48
Reply from 178.32.108.245: bytes=32 time=287ms TTL=48
Reply from 178.32.108.245: bytes=32 time=301ms TTL=48
Reply from 178.32.108.245: bytes=32 time=284ms TTL=48

Ping statistics for 178.32.108.245:
    Packets: Sent = 8, Received = 7, Lost = 1 (12% loss),
Approximate round trip times in milli-seconds:
    Minimum = 276ms, Maximum = 313ms, Average = 289ms

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

  1     9 ms    10 ms    10 ms  192.168.0.1 
  2     *        *        *     Request timed out.
  3    33 ms    28 ms    20 ms  114.108.194.161 
  4    16 ms    24 ms    45 ms  130.105.0.80 
  5    19 ms    31 ms    20 ms  114.108.193.158 
  6    27 ms    23 ms    29 ms  114.108.193.157 
  7    32 ms    22 ms    22 ms  130.105.0.18 
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10   254 ms   246 ms   245 ms  chi-1-a9.il.us [198.27.73.66] 
 11     *        *        *     Request timed out.
 12   272 ms   278 ms   284 ms  be100-1319.nwk-1-a9.nj.us [198.27.73.205] 
 13   290 ms   298 ms   281 ms  be100-1295.ldn-1-a9.uk.eu [192.99.146.126] 
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   288 ms   303 ms   285 ms  ip245.ip-178-32-108.eu [178.32.108.245] 

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

Pinging google.com [74.125.200.138] with 32 bytes of data:
Reply from 74.125.200.138: bytes=32 time=52ms TTL=45
Reply from 74.125.200.138: bytes=32 time=71ms TTL=45
Reply from 74.125.200.138: bytes=32 time=54ms TTL=45
Reply from 74.125.200.138: bytes=32 time=52ms TTL=45

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

Tracing route to google.com [74.125.200.138]
over a maximum of 30 hops:

  1    12 ms     9 ms     9 ms  192.168.0.1 
  2     *        *        *     Request timed out.
  3    23 ms    22 ms    18 ms  114.108.194.161 
  4    34 ms    31 ms    31 ms  130.105.0.80 
  5    20 ms    17 ms    54 ms  114.108.193.158 
  6    19 ms    44 ms    25 ms  114.108.193.157 
  7    26 ms    31 ms    19 ms  130.105.0.18 
  8    54 ms    54 ms    50 ms  209.85.172.97 
  9    63 ms    50 ms    53 ms  108.170.242.66 
 10    67 ms    62 ms    53 ms  72.14.238.21 
 11    63 ms    66 ms    54 ms  64.233.174.109 
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22    96 ms    59 ms   131 ms  sa-in-f138.1e100.net [74.125.200.138] 

Trace complete.
 
IPconfig information: 

Windows IP Configuration

   Host Name . . . . . . . . . . . . : GIGABITZPC
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Mixed
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Connection:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Realtek RTL8188CU Wireless LAN 802.11n USB 2.0 Network Adapter
   Physical Address. . . . . . . . . : 02-56-BF-6D-2E-05
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.35(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, July 29, 2017 08:18:59 PM
   Lease Expires . . . . . . . . . . : Saturday, August 05, 2017 08:18:59 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 114.108.195.1
                                       114.108.193.201
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 3:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:3cc8:10dc:7d96:2894(Preferred) 
   Link-local IPv6 Address . . . . . : fe80::3cc8:10dc:7d96:2894%4(Preferred) 
   Default Gateway . . . . . . . . . : ::
   DHCPv6 IAID . . . . . . . . . . . : 134217728
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-B4-B9-EF-00-1B-FC-FA-4A-7A
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{3E25959B-CC2F-467D-B2AD-7563EB1BC861}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
 
*****Test Complete*****! 
08:29 PM
Sat 07/29/2017

Hello,

For the last week, I have been experiencing frequent timeouts on the forums when performing operations, such as posting on threads and sending private messages. Upon pressing submit, it just loads for like a minute until the page times out. I am also experiencing the same on the SASP forums (especially when editing boards on the ACP), except that it shows the exact error code - Error 408. Whenever I experience this issue, I have to "spam click" Submit until it loads, but it is rather a hassle.

62LWfEL.png


I made a basic research of the error, and one of them is saying that it could be related to my internet connection, but I highly doubt this is the case as I am able to load other websites just fine. My connection to the SAMP and Teamspeak servers are also just fine.
 

Novi

Retired Admin
Joined
May 8, 2015
Messages
6,207
Location
Belgium
Re: Error 408 on the forums

Basic HTTP knowledge taught me:
Error 400 - > You fucked up
Error 500 -> The server fucked up

What this error means in human language is that either your request did not reach the server or the server's response did not reach you.

So if my memory is good and I am right this should be a client-side issue. Try restarting your router, reinstalling browser, using a different browser, try using a different IP, use a different machine and last but not least try ipconfig /release -> ipconfig /renew in CMD.

Giga said:
tagging that Philly guy
 

Giga

Donator
Joined
Dec 4, 2010
Messages
18,981
Location
MNL
Re: Error 408 on the forums

Hello,

This isolated issue remains unresolved, unfortunately. I have tried all steps given by Novi to no avail.
 

Manu

Retired Admin
Joined
Apr 7, 2013
Messages
5,142
Location
Flanders, Belgium
Re: Error 408 on the forums

Giga said:
Hello,

This isolated issue remains unresolved, unfortunately. I have tried all steps given by Novi to no avail.
do a "tracert sasp.redcountyrp.com" in your command prompt, see if there's any timeouts there? Could be your ISP fucking up routing or something
 

Giga

Donator
Joined
Dec 4, 2010
Messages
18,981
Location
MNL
Re: Error 408 on the forums

Manu said:
Giga said:
Hello,

This isolated issue remains unresolved, unfortunately. I have tried all steps given by Novi to no avail.
do a "tracert sasp.redcountyrp.com" in your command prompt, see if there's any timeouts there? Could be your ISP fucking up routing or something
I actually felt that suspicion before revisiting this query, which is why I ran the diagnostic tool when you posted that. It could be the same cause as to why I am having severe packet loss around RCRP servers.

Thread has been edited.

Code:
Running RC-RP Diagnostics test... 
Retrieving system date and time. 
Sat 07/29/2017 
08:22 PM
 
------- Ping/Traceroute to EU.FROSTGAMING.COM -------: 

Pinging eu.frostgaming.com [164.132.200.17] with 32 bytes of data:
Reply from 164.132.200.17: bytes=32 time=293ms TTL=50
Request timed out.
Reply from 164.132.200.17: bytes=32 time=298ms TTL=50
Reply from 164.132.200.17: bytes=32 time=286ms TTL=50
Reply from 164.132.200.17: bytes=32 time=296ms TTL=50
Reply from 164.132.200.17: bytes=32 time=286ms TTL=50
Reply from 164.132.200.17: bytes=32 time=301ms TTL=50
Reply from 164.132.200.17: bytes=32 time=303ms TTL=50

Ping statistics for 164.132.200.17:
    Packets: Sent = 8, Received = 7, Lost = 1 (12% loss),
Approximate round trip times in milli-seconds:
    Minimum = 286ms, Maximum = 303ms, Average = 294ms

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

  1    12 ms     7 ms     9 ms  192.168.0.1 
  2     *        *        *     Request timed out.
  3    23 ms    19 ms    23 ms  114.108.194.161 
  4    20 ms    41 ms    21 ms  130.105.0.80 
  5    22 ms    21 ms    34 ms  114.108.193.158 
  6    26 ms    23 ms    33 ms  114.108.193.157 
  7    31 ms    26 ms    20 ms  130.105.0.18 
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10   234 ms   240 ms   243 ms  chi-1-a9.il.us [198.27.73.66] 
 11     *        *        *     Request timed out.
 12   265 ms   267 ms   274 ms  be100-1319.nwk-1-a9.nj.us [198.27.73.205] 
 13   284 ms   279 ms   283 ms  be100-1295.ldn-1-a9.uk.eu [192.99.146.126] 
 14     *      281 ms     *     be10-151.rbx-g1-a9.fr.eu [91.121.215.178] 
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   288 ms   285 ms   285 ms  ns3038202.ip-164-132-200.eu [164.132.200.17] 

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

Pinging server.redcountyrp.com [178.32.108.245] with 32 bytes of data:
Reply from 178.32.108.245: bytes=32 time=287ms TTL=48
Reply from 178.32.108.245: bytes=32 time=277ms TTL=48
Request timed out.
Reply from 178.32.108.245: bytes=32 time=276ms TTL=48
Reply from 178.32.108.245: bytes=32 time=313ms TTL=48
Reply from 178.32.108.245: bytes=32 time=287ms TTL=48
Reply from 178.32.108.245: bytes=32 time=301ms TTL=48
Reply from 178.32.108.245: bytes=32 time=284ms TTL=48

Ping statistics for 178.32.108.245:
    Packets: Sent = 8, Received = 7, Lost = 1 (12% loss),
Approximate round trip times in milli-seconds:
    Minimum = 276ms, Maximum = 313ms, Average = 289ms

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

  1     9 ms    10 ms    10 ms  192.168.0.1 
  2     *        *        *     Request timed out.
  3    33 ms    28 ms    20 ms  114.108.194.161 
  4    16 ms    24 ms    45 ms  130.105.0.80 
  5    19 ms    31 ms    20 ms  114.108.193.158 
  6    27 ms    23 ms    29 ms  114.108.193.157 
  7    32 ms    22 ms    22 ms  130.105.0.18 
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10   254 ms   246 ms   245 ms  chi-1-a9.il.us [198.27.73.66] 
 11     *        *        *     Request timed out.
 12   272 ms   278 ms   284 ms  be100-1319.nwk-1-a9.nj.us [198.27.73.205] 
 13   290 ms   298 ms   281 ms  be100-1295.ldn-1-a9.uk.eu [192.99.146.126] 
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   288 ms   303 ms   285 ms  ip245.ip-178-32-108.eu [178.32.108.245] 

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

Pinging google.com [74.125.200.138] with 32 bytes of data:
Reply from 74.125.200.138: bytes=32 time=52ms TTL=45
Reply from 74.125.200.138: bytes=32 time=71ms TTL=45
Reply from 74.125.200.138: bytes=32 time=54ms TTL=45
Reply from 74.125.200.138: bytes=32 time=52ms TTL=45

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

Tracing route to google.com [74.125.200.138]
over a maximum of 30 hops:

  1    12 ms     9 ms     9 ms  192.168.0.1 
  2     *        *        *     Request timed out.
  3    23 ms    22 ms    18 ms  114.108.194.161 
  4    34 ms    31 ms    31 ms  130.105.0.80 
  5    20 ms    17 ms    54 ms  114.108.193.158 
  6    19 ms    44 ms    25 ms  114.108.193.157 
  7    26 ms    31 ms    19 ms  130.105.0.18 
  8    54 ms    54 ms    50 ms  209.85.172.97 
  9    63 ms    50 ms    53 ms  108.170.242.66 
 10    67 ms    62 ms    53 ms  72.14.238.21 
 11    63 ms    66 ms    54 ms  64.233.174.109 
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22    96 ms    59 ms   131 ms  sa-in-f138.1e100.net [74.125.200.138] 

Trace complete.
 
IPconfig information: 

Windows IP Configuration

   Host Name . . . . . . . . . . . . : GIGABITZPC
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Mixed
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Connection:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Realtek RTL8188CU Wireless LAN 802.11n USB 2.0 Network Adapter
   Physical Address. . . . . . . . . : 02-56-BF-6D-2E-05
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.35(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, July 29, 2017 08:18:59 PM
   Lease Expires . . . . . . . . . . : Saturday, August 05, 2017 08:18:59 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 114.108.195.1
                                       114.108.193.201
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 3:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:3cc8:10dc:7d96:2894(Preferred) 
   Link-local IPv6 Address . . . . . : fe80::3cc8:10dc:7d96:2894%4(Preferred) 
   Default Gateway . . . . . . . . . : ::
   DHCPv6 IAID . . . . . . . . . . . : 134217728
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-B4-B9-EF-00-1B-FC-FA-4A-7A
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{3E25959B-CC2F-467D-B2AD-7563EB1BC861}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
 
*****Test Complete*****! 
08:29 PM
Sat 07/29/2017
 
Status
Not open for further replies.
Top