#Double the latency i should have

1 messages · Page 1 of 1 (latest)

minor hull
#

I have been a payer for shadow for over two years now and for the first time in a long time i was able to use my flight sticks again, now, Friday December 12 a full week after i have gotten new fiber optic internet installed was my latency low enough to use my joysticks, a full week now and i can no longer use said joysticks again, latency is now a CONSTANT 40-41ms when just last week i was at a stable 25-30, whats with the latency increase, nothing has changed for me hardware wise, same system, same programs, but now my latency skyrocketed. VM still says USWDC01 so i know that hasnt been changed

#

This was a week ago latency says it should be around 29 according to the top, but the graph shows 33.7 still below 35ms so I should've been able to use my sticks, popup said unrecognized device and would let me use them, now it shows latency is +40ms to shadow server but graph showing 34-33, still below 35 on the graph, still no ability to use my sticks, I have tried resetting shadow multiple times, still nothing

agile locust
#

and more unstable

red mica
#

I think it's better to start investigate and do some traceroutes. I usually use PingPlotter.

Traceroute is a network diagnostic tool used to track the path that data packets take from one computer to another across a network (like the internet). It helps in determining the route and measuring the transit delays of packets over the internet. It's especially useful for identifying network issues such as slow response times, network congestion, or routing problems.

  • Via PingPlotter web site
    Download PingPlotter on both sides, Shadow and local, get the public v4 addresses, and swap them. Local traces to Shadow's IP, Shadow traces to your local IP. Then you get a pretty graph and all of the per hop latency stats. Can narrow it down from there to a local ISP issue, datacenter issue, whatever.

On PingPlotter, you can see with the graphs to understand (since you can do both tests) if it is really a Shadow problem or not.
You can post the results here, so someone can able to see, what's going on and Shadow support could ask you to do it too.

agile locust
minor hull
#

black is home to shadow, white is shadow to home

#

i dont know how to read these but.... something tells me its shadows end not mine, because it was working perfectly fine last week

red mica
#

@steel heron

red mica
red mica
# minor hull

I think, you made a mistake in setting something in the settings, since looking at other users who had done it, the graph should have marked all the routers with your local pings at the bottom (in the case from local to Shadow).

#

Due to the hour ( it's 1:20 am CET ) I can't able to help, but that mod or Pip, or the other Alex, are more technical than me.

#

For example it should look like this