[Bug Report] GamePing: Duplicate Dallas destinations and failing RTT (1000ms)

Technical Support
1

Hi Mudfish Team,

I would like to report a bug in the GamePing application regarding the Dallas destinations.

1. Duplicate Entries: When searching for “Dallas”, the application displays two seemingly redundant destinations: “US Central (Dallas)” and “US Central (Dallas, TX)”.

2. Failing Ping Tests (1000ms):

Neither of these destinations is working correctly for ping measurements:

  • Testing the first option, “US Central (Dallas)”, results in a constant 1000.0 ms RTT due to a “TCP connect timed out” error. The app reports that 30 out of 30 recent measurements failed (100.0%).
  • Testing the second option, “US Central (Dallas, TX)”, also results in a flat 1000.0 ms actual and average RTT for the direct connection.

It appears that the target endpoints configured for these specific GamePing destinations are either offline or blocking the requests, making it impossible to check the real latency to Dallas.

Could you please review, merge, and update the target IPs for these GamePing entries? Screenshots are attached below for reference.

Thank you!

image
image1680×1050 28.8 KB

image
image1680×1050 176 KB

image
image1680×1050 203 KB

2

Thank you for reporting this issue! I have updated the “US Central (Dallas)” section and removed the redundant “US Central (Dallas, TX)” destination. 

Could you please completely close the GamePing program and restart it? Please wait about 1 to 2 minutes after launching for the update to fully apply in the background.

Please try the ping test again after that, and let me know if it works correctly for you!

1 Like
3

Thanks, it’s been corrected!

4

Thank you for confirming! We are glad that the GamePing issue with Dallas has been resolved. Thank you for reporting it and helping us improve the service. If it happens again, please let us know.

1 Like