High Ping, Slow Internet

[haxorzllama]

Hey guys, so it has been a week since this happened and I cannot cope with it any more. All devices connected to it are affected. I'm no expert in internet networking and need help immediately as it is affecting my assignments.

Router/Modem - DLink 750b

Ping to www.google.com

Pinging www.google.com [74.125.237.177] with 32 bytes of data:
Reply from 74.125.237.177: bytes=32 time=2078ms TTL=53
Reply from 74.125.237.177: bytes=32 time=2359ms TTL=53
Reply from 74.125.237.177: bytes=32 time=2683ms TTL=53
Reply from 74.125.237.177: bytes=32 time=2474ms TTL=53

Ping statistics for 74.125.237.177:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2078ms, Maximum = 2683ms, Average = 2398ms

 

[Someone Somewhere]

Can you run a traceroute? Does it happen all the time, or only at some times of the day?

Are you connected via WiFi or Ethernet?

 

[haxorzllama]

Can you run a traceroute? Does it happen all the time, or only at some times of the day?

Are you connected via WiFi or Ethernet?

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert www.google.com

Tracing route to www.google.com [216.58.220.100]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms D-Link.Home [192.168.1.1]
2 48 ms 47 ms 47 ms lac.m2core.net.au [202.154.95.70]
3 47 ms 47 ms 46 ms 185.75.154.202.sta.commander.net.au [202.154.75.
185]
4 61 ms 48 ms 47 ms 197.160-26-211.corp.syd.iprimus.net.au [211.26.1
60.197]
5 48 ms 48 ms 47 ms xe-0-2-0.csr02.sydnmtc.nsw.m2core.net.au [203.13
4.72.41]
6 49 ms 48 ms 49 ms xe-1-2-0.csr02.masceqx.nsw.m2core.net.au [203.13
4.2.130]
7 51 ms 48 ms 53 ms ae3.bsr01.masceqx.nsw.m2core.net.au [203.134.2.2
54]
8 50 ms 48 ms 67 ms google-gw.masceqx.nsw.m2core.net.au [203.134.2.9
8]
9 48 ms 80 ms 48 ms 66.249.95.234
10 51 ms 49 ms 51 ms 209.85.142.11
11 58 ms 49 ms 49 ms www.google.com [216.58.220.100]

Trace complete.

1. It happened before but only for like a day so I assumed it was the ISP because it never happened again until last week. It happens every time of the day, even tried power cycling.

2. I used both ethernet and wifi and the problem was still there.

Hmmm, the internet seems to be working now but I have feeling it's not gonna be for long. I'll get back to ya when the problem comes back, I have a feeling it has to do with QoS and WMM.

 

[Someone Somewhere]

Can you do a new traceroute once it starts playing up again?

If it's on ethernet too, it's not WMM. Doubt it's QoS.

The intermittent bit makes me think that it's backhaul congestion from the DSLAM - are you on a rural connection?

 

[haxorzllama]

Can you do a new traceroute once it starts playing up again?

If it's on ethernet too, it's not WMM. Doubt it's QoS.

The intermittent bit makes me think that it's backhaul congestion from the DSLAM - are you on a rural connection?

Yup, it's playing up again.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert www.google.com

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

1 1 ms 1 ms <1 ms D-Link.Home [192.168.1.1]
2 2522 ms 2629 ms 2439 ms 202.154.95.70
3 2330 ms 2527 ms 2835 ms 185.75.154.202.sta.commander.net.au [202.154.75.
185]
4 3170 ms 2700 ms 2634 ms 197.160-26-211.corp.syd.iprimus.net.au [211.26.1
60.197]
5 1906 ms 1934 ms 2058 ms xe-0-2-0.csr02.sydnmtc.nsw.m2core.net.au [203.13
4.72.41]
6 2458 ms 2974 ms * xe-1-2-0.csr02.masceqx.nsw.m2core.net.au [203.13
4.2.130]
7 837 ms 291 ms 82 ms ae3.bsr01.masceqx.nsw.m2core.net.au [203.134.2.2
54]
8 453 ms 485 ms 513 ms google-gw.masceqx.nsw.m2core.net.au [203.134.2.9
8]
9 524 ms 549 ms * 209.85.142.94
10 2939 ms 3386 ms 2761 ms 72.14.232.31
11 3154 ms 2507 ms 2556 ms www.google.com [74.125.237.176]

Trace complete.

Yes, I use regional ADSL2+ and live about 3km away from the exchange.

Somehow I kinda feel it's the router's fault, not too sure if that's the case.

 

[Someone Somewhere]

Unfortunately, it's quite likely that it's a backhaul problem between the exchange and your ISP. Rural exchanges tend to have very poor backhaul, and once that gets saturated the queues start to pile up.

Calling up your ISP is probably the best bet - they can get a network upgrade underway if it's at capacity, or fix it if it's a config issue.

How long has it been doing this for?

 

[haxorzllama]

Unfortunately, it's quite likely that it's a backhaul problem between the exchange and your ISP. Rural exchanges tend to have very poor backhaul, and once that gets saturated the queues start to pile up.

Calling up your ISP is probably the best bet - they can get a network upgrade underway if it's at capacity, or fix it if it's a config issue.

How long has it been doing this for?

About a week, and yeah you're probably right.

When I run diagnostics it usually say the following (when it is working):

TEST THE CONNECTION TO YOUR LOCAL NETWORK
-Test your eth1 Connection: FAIL (Nothing Connected)
-Test your eth2 Connection: FAIL (Nothing Connected)
-Test your eth3 Connection: FAIL (Nothing Connected)
-Test your eth4 Connection: FAIL (Nothing Connected)
-Test your Wireless Connection: PASS

TEST THE CONNECTION TO YOUR DSL SERVICE PROVIDER
-Test ADSL Synchronization: PASS
-Test ATM OAM F5 segment ping: FAIL
-Test ATM OAM F5 end-to-end ping: PASS

TEST THE CONNECTION TO YOUR INTERNET SERVICE PROVIDER
- Ping default gateway: PASS
- Ping primary Domain Name Server: PASS

When it is not working or slow:

TEST THE CONNECTION TO YOUR LOCAL NETWORK
-Test your eth1 Connection: FAIL (Nothing Connected)
-Test your eth2 Connection: FAIL (Nothing Connected)
-Test your eth3 Connection: FAIL (Nothing Connected)
-Test your eth4 Connection: FAIL (Nothing Connected)
-Test your Wireless Connection: PASS

TEST THE CONNECTION TO YOUR DSL SERVICE PROVIDER
-Test ADSL Synchronization: PASS
-Test ATM OAM F5 segment ping: FAIL
-Test ATM OAM F5 end-to-end ping: FAIL

TEST THE CONNECTION TO YOUR INTERNET SERVICE PROVIDER
- Ping default gateway: FAIL
- Ping primary Domain Name Server: FAIL

 

[Someone Somewhere]

Yup, that's almost certainly backhaul congestion.

Talk to your ISP, and they should at least put your area on the upgrade list.

 

[haxorzllama]

Yup, that's almost certainly backhaul congestion.

Talk to your ISP, and they should at least put your area on the upgrade list.

Just wondering, by any chance could this be the modem router's fault?

 

[Someone Somewhere]

Possibly. Highly doubt it, but it's possible.

Got a friend you can borrow one off?