1. #1

    Latency issues outside of WoW

    I am aware of the DDoS attacks, but even out of WoW my latency is high, here is a trace route to google as an example
    Tracing route to google.com [216.58.219.238]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 1615 ms 1649 ms 1638 ms 10.29.43.1
    3 1661 ms 1647 ms 1608 ms G101-0-0-15.SCTNPA-LCR-21.verizon-gni.net [100.41.15.132]
    4 * * * Request timed out.
    5 1621 ms 1656 ms 1653 ms 0.ae13.GW13.NYC1.ALTER.NET [140.222.234.193]
    6 1677 ms 1642 ms 1661 ms google-gw.customer.alter.net [204.148.18.34]
    7 1599 ms 1676 ms 1586 ms 209.85.247.29
    8 * 1664 ms 1676 ms 64.233.174.117
    9 1615 ms 1677 ms 1660 ms lga25s41-in-f238.1e100.net [216.58.219.238]

    Trace complete.

    I've tried releasing and renewing my DHCP but still nothing, should I just wait for the DDoS to blow over?

  2. #2
    Quote Originally Posted by soulkeeperx View Post
    I am aware of the DDoS attacks, but even out of WoW my latency is high, here is a trace route to google as an example
    Tracing route to google.com [216.58.219.238]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 1615 ms 1649 ms 1638 ms 10.29.43.1
    3 1661 ms 1647 ms 1608 ms G101-0-0-15.SCTNPA-LCR-21.verizon-gni.net [100.41.15.132]
    4 * * * Request timed out.
    5 1621 ms 1656 ms 1653 ms 0.ae13.GW13.NYC1.ALTER.NET [140.222.234.193]
    6 1677 ms 1642 ms 1661 ms google-gw.customer.alter.net [204.148.18.34]
    7 1599 ms 1676 ms 1586 ms 209.85.247.29
    8 * 1664 ms 1676 ms 64.233.174.117
    9 1615 ms 1677 ms 1660 ms lga25s41-in-f238.1e100.net [216.58.219.238]

    Trace complete.

    I've tried releasing and renewing my DHCP but still nothing, should I just wait for the DDoS to blow over?
    Open a dos prompt and type the following :netstat -n -r
    Find the IP address of your gateway and ping it with ping -n 100 xxx.xxx.xxx.xxx and see if you have any dropped packets.
    IF you are behind a router then you'll have to get the gateway of your ISP from the router in the web interface and ping it the same.
    If you are not dropping packets to the gateway and the ping is low-ish, depending on your ISP and situation sub 20ms is not unreasonable then the issue is outside your ISP and there is little for you to do.
    If you are dropping packets and/or have high latency INside your isp, aka pinging to the gateway your attached to then the issue is your ISP or you.

    *edit*
    Sorry super tired, I see from your trace route your behind a router.
    and your gateway is on a private network, ugghh..
    Your issue is likely whoever is controlling your local network.
    2 1615 ms 1649 ms 1638 ms 10.29.43.1 is a private IP and can not be used in the public network thus it's part of your local network.
    Contact your network admins to fix it.
    From the rest of the data your path to the internet seems ok, but your local network is hosed.
    Last edited by Muddysmind; 2016-08-03 at 03:51 AM.

  3. #3
    Quote Originally Posted by Muddysmind View Post
    Open a dos prompt and type the following :netstat -n -r
    Find the IP address of your gateway and ping it with ping -n 100 xxx.xxx.xxx.xxx and see if you have any dropped packets.
    IF you are behind a router then you'll have to get the gateway of your ISP from the router in the web interface and ping it the same.
    If you are not dropping packets to the gateway and the ping is low-ish, depending on your ISP and situation sub 20ms is not unreasonable then the issue is outside your ISP and there is little for you to do.
    If you are dropping packets and/or have high latency INside your isp, aka pinging to the gateway your attached to then the issue is your ISP or you.

    *edit*
    Sorry super tired, I see from your trace route your behind a router.
    and your gateway is on a private network, ugghh..
    Your issue is likely whoever is controlling your local network.
    2 1615 ms 1649 ms 1638 ms 10.29.43.1 is a private IP and can not be used in the public network thus it's part of your local network.
    Contact your network admins to fix it.
    From the rest of the data your path to the internet seems ok, but your local network is hosed.
    I see, are there any other solutions, like using a proxy or a vpn? Or will I just have to call Verizon tomorrow?

  4. #4
    Unless you have another path to the internet at large there is no option.
    That first jump outside your router is very broken and if it's Verizon that have some issues to fix.
    Good luck with that as my experience with them on the business side is horrible, not sure how they are on the consumer side.

    I'd search for what is my IP any search engine and take that IP address replace the last octet with a 1 and see if you can ping it normally or is it still in the 1000's of ms.
    Example if your IP is 28.21.1.25 replace the last octet of 25 with 1 and ping that IP, there is no guarantee that your gateway is .1 but normally they are.
    Should give you an idea what point your connection is broken.

  5. #5
    Got off the phone with verizon and everything was fine on their end, we tried everything and nothing. However, when my PC is off my internet/wireless is fine, I hooked up my previous PC and the internet is fine there, too. I even swapped routers with someone else who has the same model as mine, and it was still slow. So my new PC is doing something to slow it down, idk what because I didn't change anything in the firewall

  6. #6
    You either have a bad modem/router, or a bad line between your home and your provider. The 1st hop is from your PC to your router. The 2nd is between your router and your ISP.

  7. #7
    Quote Originally Posted by Gorgodeus View Post
    You either have a bad modem/router, or a bad line between your home and your provider. The 1st hop is from your PC to your router. The 2nd is between your router and your ISP.
    He said the router was fine, it's still pretty new, a little over a year, and it was receiving the right amount of data, here's a trace route on this PC to compare

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

    1 <1 ms 1 ms 1 ms 192.168.1.1
    2 32 ms 30 ms 32 ms 10.29.43.1
    3 36 ms 40 ms 34 ms G0-0-4-5.SCTNPA-LCR-22.verizon-gni.net [100.41.2
    23.224]
    4 * * * Request timed out.
    5 41 ms 41 ms 42 ms 0.ae14.GW13.NYC1.ALTER.NET [140.222.234.197]
    6 42 ms 42 ms 41 ms google-gw.customer.alter.net [204.148.18.34]
    7 43 ms 42 ms 43 ms 216.239.50.141
    8 42 ms 42 ms 42 ms 209.85.240.113
    9 46 ms 45 ms 46 ms lga15s47-in-f14.1e100.net [172.217.4.78]

    Trace complete.

    Seems like Verizon couldn't do anything, unless I needed to speak to someone higher up

  8. #8
    Wait, so your other PC had that last trace route?
    Maybe your PC is part of a botnet and you are not aware of it?

    Personally I'd bypass my hard drive and OS and see if it's a software issue then.
    Go download a Linux live image burn it to a dvd or USB stick and boot up the desktop.
    That will give you a working normal desktop without using yours to do testing with and see if the results are the same
    You can open a terminal (just like a dos window) and run ping/traceroute from there.
    https://linuxmint.com/edition.php?id=217

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •