Just switched to 3BB - very unstable internet - ping 3000ms

[balo]

This is the result when I trace route to thaivisa.com

Tracing route to thaivisa.com [175.41.131.133]

over a maximum of 30 hops:

1 2 ms 8 ms 9 ms 192.168.1.1

2 2029 ms 1512 ms 1649 ms 10.121.20.113

3 3229 ms 2039 ms 1857 ms 10.121.20.114

4 2188 ms 1419 ms 1859 ms mx-ll-110.164.0-211.static.3bb.co.th [110.164.0.

211]

5 1635 ms 1578 ms 2464 ms mx-ll-110.164.0-140.static.3bb.co.th [110.164.0.

140]

6 2236 ms 2809 ms 2649 ms mx-ll-110.164.1-63.static.3bb.co.th [110.164.1.6

3]

7 * 1876 ms 1495 ms mx-ll-110.164.1-11.static.3bb.co.th [110.164.1.1

1]

8 41 ms 29 ms 29 ms 181.84.50.182.crs-bb-ix-jastel.co.th [182.50.84.

181]

9 85 ms 539 ms 959 ms pos-0-1-1-1-bkk.crs.bb2-ix-jastel.co.th [182.50.

84.237]

10 1934 ms 2049 ms 2149 ms 124.158.232.17

11 3025 ms 2829 ms 3037 ms ae-0.myix-gw-1-kul-pip.my.globaltransit.net [61.

11.210.190]

12 2485 ms 2635 ms 2823 ms 218.100.44.155

13 2614 ms 2828 ms 3140 ms 203.83.223.2

14 3064 ms 3359 ms 2939 ms 203.83.223.23

15 3372 ms 3072 ms 2339 ms 203.83.223.231

16 2098 ms 1999 ms 1779 ms ec2-175-41-128-241.ap-southeast-1.compute.amazon

aws.com [175.41.128.241]

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 2859 ms 3342 ms 2372 ms ec2-175-41-131-133.ap-southeast-1.compute.amazon

aws.com [175.41.131.133]

Trace complete.

Speedtest (testmy.net) shows normal speed 1.7 mb to Hong Kong , and just under 1 mb to London which is acceptable for TV streams . I pay for the cheapest subscription .

But the problem is all the lag, suddenly google.com takes several seconds to load.

I use a wifi router but there's no problems when I ping my own network . This is in Chonburi , any suggestions ?

Also when I restart the router the speed seems fine for about 30 minutes , then the same happens again .

.

Edited May 11, 2015 by balo

[balo]

Trace route to google.com

Tracing route to google.com [216.58.217.142]

over a maximum of 30 hops:

1 2 ms 3 ms 9 ms 192.168.1.1

2 715 ms 337 ms 199 ms 10.121.20.113

3 2488 ms 2673 ms 1407 ms 10.121.20.114

4 1929 ms 2306 ms 2819 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.1

4.187]

5 2788 ms 2958 ms 2817 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.1

4.186]

6 2427 ms 2609 ms 2749 ms mx-ll-110.164.1-65.static.3bb.co.th [110.164.1.6

5]

7 3286 ms 2388 ms 639 ms mx-ll-110.164.1-11.static.3bb.co.th [110.164.1.1

1]

8 * * * Request timed out.

9 1684 ms 905 ms 422 ms mx-ll-110.164.14-235.static.3bb.co.th [110.164.1

4.235]

10 410 ms 409 ms 414 ms 72.14.196.114

11 1732 ms 2209 ms 2733 ms 209.85.242.246

12 2497 ms 469 ms 3497 ms 209.85.242.242

13 1907 ms 1893 ms 1979 ms 209.85.255.131

14 1207 ms 216 ms 222 ms 209.85.143.1

15 * * * Request timed out.

16 * * * Request timed out.

17 * 2651 ms 2629 ms 72.14.236.147

18 * * * Request timed out.

19 2260 ms 399 ms 269 ms iad23s43-in-f14.1e100.net [216.58.217.142]

Trace complete.

[balo]

Is this what to expect with 3BB these days?

[KittenKong]

With my 15mbs 3BB package I get 50-70ms through to ec2-175-41-131-133.ap-southeast-1.compute.amazon

aws.com [175.41.131.133], but there's probably some proxy hanky-panky going on there.

The bulk of your delay seems to be happening between you and your local gateway, so presumably there's something wrong.

I just got 8mbs to HongKong using your test service.

[Tywais]

This is mine from Chiang Mai to Thaivisa.com. 3BB 13Mbps/1Mbps subscription. As mentioned, the problem seems to right away at the 3BB 1st or 2nd router. Had a similar problem when initially installed and ended up being a bad wiring connection at the pole. Worth contacting 3BB showing your information. I've found them to respond quickly.

Tracing route to pagespeed.googlehosted.com [74.125.68.121]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 21 ms 22 ms 21 ms 10.121.50.101
3 23 ms 29 ms 21 ms 10.121.50.254
4 51 ms 35 ms 106 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]
5 33 ms 34 ms 33 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]
6 33 ms 37 ms 33 ms mx-ll-110.164.1-5.static.3bb.co.th [110.164.1.5]
7 37 ms 35 ms 34 ms mx-ll-110.164.1-11.static.3bb.co.th [110.164.1.11]
8 59 ms 58 ms 59 ms mx-ll-110.164.0-129.static.3bb.co.th [110.164.0.129]
9 60 ms 60 ms 60 ms 72.14.194.15
10 61 ms 62 ms 74 ms 209.85.243.156
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 65 ms 64 ms 64 ms 74.125.68.121

[RichCor]

Trace route to google.com

Tracing route to google.com [216.58.217.142]

over a maximum of 30 hops:

1 2 ms 3 ms 9 ms 192.168.1.1

2 715 ms 337 ms 199 ms 10.121.20.113

3 2488 ms 2673 ms 1407 ms 10.121.20.114

The IP Addresses assigned to your consumer router and 3BBs concentrator (10.121.20.113 and .114) are part of the reserved 10.0.0.0 - 10.255.255.255 PRIVATE IP addresses normally used for internal LANS. It can also be used by ISPs deploying Carrier Grade NAT, meaning your connection is effectively 'double NAT' (ISP private address, and your consumer router issuing your devices another private address)

Double NAT works fine for most Internet Browsing, but doesn't play well where direct point-to-point connections are needed (communications, games, iptv, etc).

That aside, you should have <35ms delays for each of those devices to the next router hop ( mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

Something definitely wrong there.

Is this an ADSL or Fiber connection?

Try power cycling the Modem/Router (unplug power, count to 10, plug back in) and when it's back up, retest.

[balo]

No change I'm afraid . I will have to contact support tomorrow. Thanks for the input.

[NeverSure]

I'm with Tywais. It's probably in the installation or wiring. There's nothing definitive in the tracert. If it was hanging only on DNS or something you could try another by logging in to the router, but it's consistent.

The only other thing I can think of is that the ISP has too many users on this line. You might try it in the middle of the night just for giggles.

Good luck.

[balo]

Every time I restart the router and do a trace , I get 30ms everywhere and it looks really fast .

No more than 2 minutes later , its the same shitty speed again around 3000 ms.

So it must be something strange going on here, need a technician to check this out.

[RichCor]

If this is an ADSL line, what connection statistics is your modem/router reporting at (192.168.1.1), if you have the name/pass to login?

[NeverSure]

OP, this is kind of a pain but you can probably test the wiring/wireless inside and outside the house if you have a laptop. It's by process of elimination by actually testing to see if it's faster directly from the street.

(BTW you wouldn't happen to have a cable that's ever been kinked or some serious electromagnetic interference with wireless? Anything electrical running close to the router or computer? Could it be an aircon coming on or something?)

If you have an interface box on or in the house where the outside line attaches from the street, you can open it and see the incoming line, and the line to the house. If you unplug the line to the house and instead plug in your modem and router, you can let them boot right there. Extension cords might be needed. Once first the modem, and then next the router, and then next the laptop boot, you will be able to test only the incoming part, bypassing the house.

[T_Dog]

Balo... We had a similar experience with comparable pings when we moved into a moo bann recently. For ten days, the internet was essentially unusable and ours was a new cable to the local box. The technician came and replaced all the hardware in the local gateway and ever since then things have been great. Hope you can get your problems sorted, but keep the pressure up on 3BB support. They initially told us the same "reset your ADSL box" but in the end, it was the local hardware they had to replace.

[balo]

OK guys , this is a bit embarrassing but I never suspected my smart DNS service from Overplay to be the cause of all this troubles. A week ago I received a mail from them that they changed their DNS servers to something called Turbo DNS

"TurboDNS is an upgrade to our SmartDNS service, which will allow users to experience increased speeds when connecting to their favorite channels and entertainment through the OverPlay service. In order to access the new, improved TurboDNS service, users must update their device’s DNS settings."

So I never had any issues with my old DNS settings so I never suspected their new DNS servers to cause the delays.

Anyway been testing now for hours after I removed the DNS settings and this is the results I get.

Pinging thaivisa.com [175.41.131.133] with 32 bytes of data:

Reply from 175.41.131.133: bytes=32 time=54ms TTL=43

Reply from 175.41.131.133: bytes=32 time=53ms TTL=43

Reply from 175.41.131.133: bytes=32 time=53ms TTL=43

Reply from 175.41.131.133: bytes=32 time=54ms TTL=43

Ping statistics for 175.41.131.133:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 53ms, Maximum = 54ms, Average = 53ms

Pinging google.com [110.164.16.103] with 32 bytes of data:

Reply from 110.164.16.103: bytes=32 time=37ms TTL=58

Reply from 110.164.16.103: bytes=32 time=36ms TTL=58

Reply from 110.164.16.103: bytes=32 time=24ms TTL=58

Reply from 110.164.16.103: bytes=32 time=23ms TTL=58

Ping statistics for 110.164.16.103:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 23ms, Maximum = 37ms, Average = 30ms

Tracing route to thaivisa.com [175.41.131.133]

over a maximum of 30 hops:

1 2 ms 4 ms 9 ms 192.168.1.1

2 28 ms 37 ms 57 ms 10.121.20.125

3 25 ms 264 ms 24 ms 10.121.20.122

4 25 ms 65 ms 39 ms mx-ll-110.164.0-137.static.3bb.co.th [110.164.0.

137]

5 26 ms 33 ms 45 ms mx-ll-110.164.0-200.static.3bb.co.th [110.164.0.

200]

6 25 ms 30 ms 35 ms mx-ll-110.164.1-139.static.3bb.co.th [110.164.1.

139]

7 30 ms 30 ms 29 ms mx-ll-110.164.1-117.static.3bb.co.th [110.164.1.

117]

8 27 ms 36 ms 29 ms 253.84.50.182.crs-bb-ix-jastel.co.th [182.50.84.

253]

9 48 ms 48 ms 49 ms pos-0-1-1-1-bkk.crs.bb2-ix-jastel.co.th [182.50.

84.237]

10 * * * Request timed out.

11 51 ms 52 ms 49 ms ae-1.myix-gw-1-kul-pip.my.globaltransit.net [61.

11.211.190]

12 70 ms 54 ms 59 ms 218.100.44.155

13 58 ms 57 ms 59 ms 203.83.223.2

14 55 ms 60 ms 59 ms 203.83.223.23

15 54 ms 57 ms 66 ms 203.83.223.231

16 57 ms 55 ms 59 ms ec2-175-41-128-241.ap-southeast-1.compute.amazon

aws.com [175.41.128.241]

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 171 ms 170 ms 167 ms ec2-175-41-131-133.ap-southeast-1.compute.amazon

aws.com [175.41.131.133]

Trace complete.

[balo]

So instead of increased speed as they promised they gave me the worst speed ever.

I think I'll just stick to my VPN provider to avoid any more of these issues in the future.

Edited May 12, 2015 by balo

[KhunBENQ]

If I understand the discussion right, its not a problem with your 3BB ADSL but with some DNS service that you have installed?

tracert to thaivisa.com (ToT fibre):

1 1 ms 1 ms 2 ms ADSL [192.168.1.1]
2 3 ms 2 ms 2 ms node-801.pool-118-172.dynamic.totbb.net [118.172.xxx.xxx]

...

22 42 ms 42 ms 42 ms ec2-175-41-131-133.ap-southeast-1.compute.amazonaws.com [175.41.131.133]

[balo]

I removed the DNS service now , it's still there , but not slowing down anything,

22 42 ms 42 ms 42 ms ec2-175-41-131-133.ap-southeast-1.compute.amazonaws.com [175.41.131.133]

Edit: this is only when tracing thaivisa.com

Edited May 12, 2015 by balo

[balo]

When I trace google :

Tracing route to google.com [110.164.6.246]

over a maximum of 30 hops:

1 2 ms 8 ms 9 ms 192.168.1.1

2 29 ms 36 ms 29 ms 10.121.20.125

3 29 ms 47 ms 29 ms 10.121.20.114

4 67 ms 29 ms 29 ms mx-ll-110.164.14-193.static.3bb.co.th [110.164.1

4.193]

5 29 ms 29 ms 29 ms mx-ll-110.164.14-192.static.3bb.co.th [110.164.1

4.192]

6 25 ms 36 ms 26 ms mx-ll-110.164.6-246.static.3bb.co.th [110.164.6.

246]

Trace complete.

[Tywais]

Those are perfect results now.

Here is a nice program that will evaluate and find the best DNS server for your location, though it looks like you can't beat what you have now. https://code.google.com/p/namebench/