3BB service in the city (Chiang Mai)

[someonelovesyou]

Hi,

I'm wondering if anyone else out there is having the same problems as me.

I have service with 3BB in the city, next to kad suan kaew.. Had the 800 baht month ADSL plan.

At random times (usually within expected peak hours) it will go very slow for 1-4 hours, then recover again. By slow I mean very slow.

From 3BB's own speed test page, I test the speed with the local Thailand server.

http://speedtest.adslthailand.com/

Here's a typical "good result" when its slow, usually the ping is closer to 1000. One time strangely it consistently gave results in the 20,000-30,000 range.

Last Result:
Download Speed: 1387 kbps (173.4 KB/sec transfer rate)
Upload Speed: 475 kbps (59.4 KB/sec transfer rate)
Latency: 583 ms
1/26/2015, 9:50:23 PM

Complained. At first they told me to upgrade, so I changed to the 1200/month package. Its 30/5 or something. Still same problem.

The speed is fine for the other 20+ hours of the day. It just does this for a few hours and seems to recover. Oddly, one time it was faulty for 4 hours, I called support one time, they asked me if it was fixed. And mysteriously 3 minutes later it went fast again.

Tried to switch to True but apparently they cant offer their fast service to me. I can try another provider (forget the name) but all I read was bad things on here and that 3BB is better. (oh no!)

Are other people getting same thing, and do I just need to stop complaining and put up with it? Its happening almost every day and is quite annoying.

[someonelovesyou]

I might add I've heard a lot of people complain about international speeds, but this problem seems to affect national Thailand traffic too. So I'm wondering if anyone is having problems with this.

[Diplomatico]

I have used 3BB for several months now and have not noticed this problem.

[CMNightRider]

I have been experiencing the same problem, and have complained to 3BB with negative results. As far as I know, 3BB is currently the best internet service available in Chiang Mai.

[LivinLOS]

As I am sure you know your internet is shared with other local users (contention ratio) so if your other local users do bandwidth hogging activities for periods of time (torrenting etc) it effects everyone whose sharing..

My net is nice and speedy.. As everyone finishes work around 5 - 8pm and also but less so over weekends.. Its noticeably slower.

[someonelovesyou]

As I am sure you know your internet is shared with other local users (contention ratio) so if your other local users do bandwidth hogging activities for periods of time (torrenting etc) it effects everyone whose sharing..

My net is nice and speedy.. As everyone finishes work around 5 - 8pm and also but less so over weekends.. Its noticeably slower.

If this were the case I would have thought the speeds would have a greater spread.

My ping is either 30-40ms or 600-1000+ms - nothing in between. I would expect to get perhaps 50-100ms sometimes too if this were the case. But its 30ms one second, then 600+ for 2 hours, then suddenly instantly down to 30-40ms in an instant. Unless its one person that's hogging all the bandwidth and when he logs off its fixed, this doesn't seem quite right.

[CMSteve]

Latency for 583? Its normal for the net to slow when work/school is finished for a few hours, but it seems there is more to it.

Are you using wifi to connect? you might be getting the slow times because of a nearby router using the same channel.

[Diplomatico]

Latency for 583? Its normal for the net to slow when work/school is finished for a few hours, but it seems there is more to it.

Are you using wifi to connect? you might be getting the slow times because of a nearby router using the same channel.

You may be on to something with the router channel, CMSteve. When I first got my internet connection, my router was set to whatever default channel 3BB had on their router (ch 13). I began having problems where my laptop would "find" about 40 other wifi networks but could never seem to find mine, even though it was closest. When it would connect, it would sometimes drop and then again, I'd have problems "finding" my own network.

I logged in to my 3BB account online and changed my router channel to another channel. Problem solved and now my laptop only "sees" about a dozen other networks, as well as my own network, and my connection never drops.

I don't pretend to know much of anything about internet wifi connections but it makes empirical sense that if many other networks are sharing the same channel that speed may suffer. If that's wrong, I'm sure someone else will be along to tell me so.

[circusman]

I had 3b for a year and it was fine. I moved and now have True. My speed is not that great and I will go back to 3b.

[someonelovesyou]

Latency for 583? Its normal for the net to slow when work/school is finished for a few hours, but it seems there is more to it.

Are you using wifi to connect? you might be getting the slow times because of a nearby router using the same channel.

Yes usually the latency is 800-1000 and this is local Thailand server traffic, not international. As I said, 583 was a "good result" for when it has the problem.

I've also tried:

a) changed the service from ADSL (800 month) to their 1200/month service.

b ) got a new computer, tested from 2 different computers with all the other devices shut down.

c) replaced the router

d) plugged Ethernet cable directly into the router and disabled wireless.

problem still occurs.

Edited January 27, 2015 by someonelovesyou

[Awk]

Latency for 583? Its normal for the net to slow when work/school is finished for a few hours, but it seems there is more to it.

Are you using wifi to connect? you might be getting the slow times because of a nearby router using the same channel.

Yes usually the latency is 800-1000 and this is local Thailand server traffic, not international. As I said, 583 was a "good result" for when it has the problem.

I've also tried:

a) changed the service from ADSL (800 month) to their 1200/month service.

b ) got a new computer, tested from 2 different computers with all the other devices shut down.

c) replaced the router

d) plugged Ethernet cable directly into the router and disabled wireless.

problem still occurs.

You might want to lookup how to use the traceroute program, called tracert on windows I think. It might provide a good indication of where in the network path the latency increase occurs. Do some traceroutes while the latency is low/good, and then the same when it is bad, and compare.

[someonelovesyou]

Have the problem right now. Did a traceroute. Basically all it tells me is the problem starts on their 3BB internal network (the 10.121 addresses) before it even gets to 3BB's internet routing devices (the 110.164 devices) and especially before it gets to the next hop out onto the internet (the 203.170 devices).

January 29, 2015. 4pm-4:30pm

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 4 ms 1 ms 1 ms 192.168.0.1

2 37 ms 52 ms 58 ms 10.121.50.105

3 1234 ms 1050 ms 1403 ms 10.121.50.106

4 2393 ms 296 ms 45 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 1086 ms 172 ms 52 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 1763 ms 941 ms 2607 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 1613 ms 1192 ms 456 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 97 ms 110 ms 131 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 1022 ms 1156 ms 1267 ms 27.254.128.129

11 905 ms 778 ms 1191 ms 27.254.129.134

12 * * * Request timed out.

13 1956 ms 1461 ms 2210 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 2 ms 1 ms <1 ms 192.168.0.1

2 27 ms 28 ms 146 ms 10.121.50.105

3 28 ms 29 ms 30 ms 10.121.50.106

4 75 ms 153 ms 73 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 53 ms 55 ms 41 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 134 ms 69 ms 49 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 54 ms 57 ms 57 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 102 ms 343 ms 359 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 86 ms 112 ms 111 ms 27.254.128.129

11 1777 ms 1178 ms 176 ms 27.254.129.134

12 * * * Request timed out.

13 1659 ms 510 ms 280 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 9 ms 11 ms 14 ms 192.168.0.1

2 44 ms 607 ms 58 ms 10.121.50.253

3 1326 ms 2044 ms 1976 ms 10.121.50.106

4 983 ms 2304 ms 1596 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 998 ms 907 ms 1669 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 1006 ms 2059 ms 2029 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 1799 ms 759 ms 421 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 1449 ms 1130 ms 2123 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 2049 ms 2237 ms 1982 ms 27.254.128.129

11 * 172 ms 528 ms 27.254.129.134

12 * * * Request timed out.

13 59 ms 54 ms 56 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 16 ms 6 ms 5 ms 192.168.0.1

2 332 ms 101 ms 42 ms 10.121.50.101

3 1275 ms 47 ms 30 ms 10.121.50.106

4 101 ms 773 ms 1713 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 708 ms 40 ms 43 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 1507 ms 1074 ms 175 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 1907 ms 224 ms 60 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 1443 ms 1444 ms 2180 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 1757 ms 988 ms 91 ms 27.254.128.129

11 1967 ms * 2201 ms 27.254.129.134

12 * * * Request timed out.

13 1970 ms * * serve62-15.sheeplink.com [115.178.62.15]

14 3191 ms 1419 ms 1411 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 14 ms 11 ms 12 ms 192.168.0.1

2 348 ms 36 ms 41 ms 10.121.50.253

3 1867 ms 459 ms 94 ms 10.121.50.106

4 1419 ms 882 ms 1029 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 1107 ms 996 ms 370 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 329 ms 1483 ms 537 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 130 ms 1585 ms 2300 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 1135 ms 888 ms 907 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 322 ms 138 ms 116 ms 27.254.128.129

11 969 ms 46 ms 41 ms 27.254.129.134

12 * * * Request timed out.

13 939 ms 2654 ms 1807 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1

2 29 ms 28 ms 43 ms 10.121.50.101

3 28 ms 29 ms 28 ms 10.121.50.106

4 41 ms 40 ms 40 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 40 ms 40 ms 39 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 39 ms 39 ms 40 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 41 ms 41 ms 41 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 40 ms 40 ms 40 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 40 ms 40 ms 40 ms 27.254.128.129

11 42 ms 41 ms 41 ms 27.254.129.134

12 * * * Request timed out.

13 278 ms 261 ms 248 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1

2 153 ms 48 ms 32 ms 10.121.50.101

3 45 ms 41 ms 35 ms 10.121.50.106

4 70 ms 88 ms 47 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 40 ms 40 ms 53 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 203 ms 243 ms 163 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 256 ms 236 ms 117 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 288 ms 277 ms 256 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 127 ms 107 ms 63 ms 27.254.128.129

11 50 ms 48 ms 49 ms 27.254.129.134

12 * * * Request timed out.

13 201 ms 334 ms 433 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 15 ms 203 ms 13 ms 192.168.0.1

2 48 ms 49 ms 40 ms 10.121.50.105

3 28 ms 37 ms 29 ms 10.121.50.106

4 43 ms 43 ms 40 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 39 ms 39 ms 39 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 40 ms 39 ms 39 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 41 ms 41 ms 41 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 40 ms 40 ms 40 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 40 ms 40 ms 40 ms 27.254.128.129

11 41 ms 41 ms 41 ms 27.254.129.134

12 * * * Request timed out.

13 40 ms 41 ms 40 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 2 ms 1 ms 6 ms 192.168.0.1

2 158 ms 423 ms 102 ms 10.121.50.253

3 51 ms 29 ms 28 ms 10.121.50.106

4 41 ms 40 ms 42 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 52 ms 48 ms 39 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 41 ms 39 ms 39 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 41 ms 41 ms 43 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 51 ms 41 ms 40 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 43 ms 41 ms 42 ms 27.254.128.129

11 52 ms 56 ms 66 ms 27.254.129.134

12 * * * Request timed out.

13 242 ms 139 ms 107 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 9 ms 13 ms 11 ms 192.168.0.1

2 222 ms 50 ms 33 ms 10.121.50.101

3 148 ms 31 ms 323 ms 10.121.50.106

4 40 ms 43 ms 42 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 86 ms 39 ms 309 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 40 ms 41 ms 39 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 41 ms 41 ms 42 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 40 ms 40 ms 44 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 40 ms 40 ms 40 ms 27.254.128.129

11 42 ms 43 ms 41 ms 27.254.129.134

12 * * * Request timed out.

13 41 ms 40 ms 40 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 16 ms 13 ms 9 ms 192.168.0.1

2 34 ms 40 ms 34 ms 10.121.50.253

3 1587 ms 778 ms 704 ms 10.121.50.106

4 531 ms 684 ms 719 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 744 ms 122 ms 1009 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 1041 ms 683 ms 388 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 233 ms 536 ms 1334 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 * 60 ms 55 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 55 ms 51 ms 86 ms 27.254.128.129

11 111 ms 308 ms 199 ms 27.254.129.134

12 * * * Request timed out.

13 766 ms 1339 ms 106 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 6 ms 11 ms 10 ms 192.168.0.1

2 49 ms 38 ms 35 ms 10.121.50.105

3 2310 ms 2125 ms 1831 ms 10.121.50.106

4 431 ms 1603 ms 1510 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 121 ms 50 ms 42 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 2605 ms 1537 ms 1224 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 1497 ms 2009 ms 1375 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 782 ms 994 ms 146 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 40 ms 40 ms 44 ms 27.254.128.129

11 41 ms 41 ms 42 ms 27.254.129.134

12 * * * Request timed out.

13 76 ms 79 ms 91 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

C:\Users\User>tracert 115.178.62.15

Tracing route to serve62-15.sheeplink.com [115.178.62.15]

over a maximum of 30 hops:

1 9 ms 11 ms 12 ms 192.168.0.1

2 41 ms 30 ms 45 ms 10.121.50.105

3 2044 ms 1634 ms 945 ms 10.121.50.106

4 1100 ms 1457 ms 720 ms mx-ll-110.164.14-187.static.3bb.co.th [110.164.14.187]

5 1874 ms 600 ms 525 ms mx-ll-110.164.14-186.static.3bb.co.th [110.164.14.186]

6 * * * Request timed out.

7 1765 ms 1905 ms 2095 ms dial-373.ras-18.bkk.c.cscoms.com [203.170.173.57]

8 516 ms 815 ms 1895 ms dial-410.ras-18.bkk.c.cscoms.com [203.170.173.94]

9 432 ms 48 ms 50 ms dial-402.ras-18.bkk.c.cscoms.com [203.170.173.86]

10 40 ms 40 ms 42 ms 27.254.128.129

11 43 ms 64 ms 42 ms 27.254.129.134

12 * * * Request timed out.

13 49 ms 43 ms 44 ms serve62-15.sheeplink.com [115.178.62.15]

Trace complete.

[someonelovesyou]

Called them, apparently all the technicians finish at 5pm so one is calling me tomorrow. We'll see if showing them these results can help them fix this problem...

I'll keep this thread updated with the results in case anyone has similar problems.