Slow internet past couple of weeks?

[jpinx]

It's probably showing switzerland as an attempt to bypass 'slow' connectivity across the Pacific right now. Your ISP may be routing out of vietnam instead of singapore, hard to be certain but yeah. Now you can see that it's not your 'speed' that's a problem, it's your routing. So a speedtest won't accurately show you your issues but here in the tracert (short for trace route) you're seeing where the connectivity problem is. There's probably not much your ISP can do at this moment short of rebuilding their routing tables and... good effin' luck getting them to do that =D.

Not quite sure about that -- given that my traceroute to 8.8.8.8 ended up in California without issues - just a bit slow.

You can do a geoIP search on any of the IP's listed in the traceroute results to see exactly where it's going. As I said before, it may not be the same every time.

[JeffreyO]

Google routes to California but the tracert is not accurate. There is no connection that takes 50ms to cross the ocean. Bottom line.

[jpinx]

Google routes to California but the tracert is not accurate. There is no connection that takes 50ms to cross the ocean. Bottom line.

Not sure where you see 50ms...

16 google-public-dns-a.google.com (8.8.8.8) 338.278 ms 337.888 ms 337.696 ms

[JeffreyO]

Sorry, I was looking at another. That's about expected speed to north america. And yes, a route can use many different lines, time of day, network usage, bottlenecks, etc. They all play a role.

[shariq607]

This looks like normal ping to 8.8.8.8 (google open DNS). You can attempt to a more to a more localized server.

Try... in-n-out.com

tracert in-n-out.com

You should see significantly higher latency as you leave the local ocean.

Ping times of 32ms mean you didn't leave the region.

This is what im getting.

PING in-n-out.com (199.83.131.71): 56 data bytes

64 bytes from 199.83.131.71: seq=0 ttl=52 time=230.224 ms

64 bytes from 199.83.131.71: seq=1 ttl=52 time=229.879 ms

64 bytes from 199.83.131.71: seq=2 ttl=52 time=230.039 ms

64 bytes from 199.83.131.71: seq=3 ttl=52 time=229.907 ms

64 bytes from 199.83.131.71: seq=4 ttl=52 time=230.058 ms

--- in-n-out.com ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max = 229.879/230.021/230.224 ms

[JeffreyO]

This looks like normal ping to 8.8.8.8 (google open DNS). You can attempt to a more to a more localized server.

Try... in-n-out.com

tracert in-n-out.com

You should see significantly higher latency as you leave the local ocean.

Ping times of 32ms mean you didn't leave the region.

This is what im getting.

PING in-n-out.com (199.83.131.71): 56 data bytes

64 bytes from 199.83.131.71: seq=0 ttl=52 time=230.224 ms

64 bytes from 199.83.131.71: seq=1 ttl=52 time=229.879 ms

64 bytes from 199.83.131.71: seq=2 ttl=52 time=230.039 ms

64 bytes from 199.83.131.71: seq=3 ttl=52 time=229.907 ms

64 bytes from 199.83.131.71: seq=4 ttl=52 time=230.058 ms

--- in-n-out.com ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max = 229.879/230.021/230.224 ms

Your connection is stable and that's expected latency for a connection to that location. If you do a ping in-n-out.com -t the ping will happen continuously. You can let it run for a few hours and then CTRL-C, check if you had 'windows' of packet loss. A connection might be good for 5 minutes, bad for 5, off and on.