Skip to content
View in the app

A better way to browse. Learn more.

Thailand News and Discussion Forum | ASEANNOW

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Could you test your 3BB/AIS/TOT speeds?

Featured Replies

I'll be moving to Bangkok in a couple months from Japan. 3BB seems to have good pricing and recommendations but for the past few days I have been speedtesting each of 3BB/AIS/TOT and 3BB seems to not do well compared to the other. Not only the speeds but it constantly gave me higher ping. (similar results with Chiang Mai area) Not sure if its a 3BB thing or my ISP here. If anyone with fiber connection from any of the ISPs above could run a test to a server in Tokyo and/or try pinging 104.160.154.1 I would appreciate it.

 

3BB

8910513725.png

 

AIS

8910519809.png

 

TOT

8910525503.png

Just done the #BB Speedtest. I pay for 400/400 = Bht 749 a month, but have re-allocated to 600/200.

Ping = 7ms, Down = 510, Up = 208.

Must ask ém where the other 100 is!   LOL

AIS Fiber:

OPEN Project (via 20G SINET): Ping: 112 ms, Jitter: 2 ms, Loss: 0.3%, Down: 376 mbps, Up: 15.9 mbps

Rakuten Mobile, Inc: Ping: 386 ms, Jitter: 9 ms, Loss: 0.0% , Down: 43.04 mbps, Up: 10.74 mbps

 

PING 104.160.154.1 (104.160.154.1): 56 data bytes
64 bytes from 104.160.154.1: icmp_seq=0 ttl=52 time=100.636 ms
64 bytes from 104.160.154.1: icmp_seq=1 ttl=52 time=100.321 ms
64 bytes from 104.160.154.1: icmp_seq=2 ttl=52 time=100.795 ms
64 bytes from 104.160.154.1: icmp_seq=3 ttl=52 time=99.948 ms
64 bytes from 104.160.154.1: icmp_seq=4 ttl=52 time=100.245 ms
64 bytes from 104.160.154.1: icmp_seq=5 ttl=52 time=100.331 ms

AIS Fiber Tokyo

 

hhh.jpg

 

AIS Fiber just outside Bangkok

 

 

 

speed.jpg

Can someone remove crossy's IP address from his post? It reveals his precise location, sure hid didn't intend to do that. 

 

Edit: actually the IP address shows for me is hundreds of km away, I'm sure he safe from internet trolls and weirdos.

  • Author

Thanks everyone. It does seems like 3BB has bad ping to Tokyo for some reason. I'll probably have to remove 3BB from my choices.

1 hour ago, kzyswd said:

Thanks everyone. It does seems like 3BB has bad ping to Tokyo for some reason. I'll probably have to remove 3BB from my choices.

its just your server. I get 100-160ms on 3bb on gaming servers in tokyo.

53 minutes ago, bearpolar said:

its just your server. I get 100-160ms on 3bb on gaming servers in tokyo.

That's still a bit too high for decent gaming. 160ms is borderline unplayable for most games.

7 hours ago, kzyswd said:

try pinging 104.160.154.1

Ouch!

I did a tracert (routing) for 3BB to this server.

Seemingly going through US carriers!

One IP is 50.242.150.145. Geolocation shows Comcast Chicago!

 

Quote

Tracing route to 104.160.154.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     5 ms     4 ms     7 ms  100.103.0.1
  3     4 ms     4 ms     4 ms  10.121.40.206
  4    10 ms    10 ms    10 ms  10.33.44.15
  5     *        9 ms     9 ms  10.33.44.24
  6     9 ms     9 ms     8 ms  10.33.45.65
  7     *        *        *     Request timed out.
  8     9 ms     9 ms     9 ms  mx-ll-110.164.1-142.static.3bb.co.th [110.164.1.142]
  9     9 ms     9 ms    10 ms  mx-ll-110.164.1-19.static.3bb.co.th [110.164.1.19]
 10    11 ms    11 ms    10 ms  mx-ll-110.164.1-21.static.3bb.co.th [110.164.1.21]
 11    54 ms    54 ms    54 ms  mx-ll-110.164.0-223.static.3bb.co.th [110.164.0.223]
 12   202 ms   202 ms   202 ms  mx-ll-110.164.0-23.static.3bb.co.th [110.164.0.23]
 13   211 ms   212 ms   211 ms  te-0-9-0-0-1-pe01.9greatoaks.ca.ibone.comcast.net [50.242.150.145]
 14   232 ms   231 ms   231 ms  be-12544-cr01.9greatoaks.ca.ibone.comcast.net [68.86.87.149]
 15   206 ms   206 ms   206 ms  be-12578-pe04.9greatoaks.ca.ibone.comcast.net [68.86.88.18]
 16   204 ms   204 ms   204 ms  ae-13.a02.snjsca04.us.bb.gin.ntt.net [129.250.66.33]
 17   213 ms   213 ms   213 ms  ae-9.r01.snjsca04.us.bb.gin.ntt.net [129.250.2.2]
 18   205 ms   205 ms   205 ms  ae-10.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.174]
 19   241 ms   208 ms   208 ms  ae-21.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.5.77]
 20   209 ms   209 ms   209 ms  ae-2.r00.tokyjp08.jp.bb.gin.ntt.net [129.250.6.127]
 21   209 ms   208 ms   208 ms  ae-1.a00.tokyjp03.jp.bb.gin.ntt.net [129.250.5.51]
 22   210 ms   210 ms   210 ms  xe-0-0-17-1.a00.tokyjp03.jp.ce.gin.ntt.net [61.120.146.66]

 23   210 ms   209 ms   209 ms  104.160.154.1

 

Other Japan addresses show ping's of about 120 ms though.

 

About this 104.160.154.1:

Two geolocation services show it as located in the US (Riot Games Inc).

One shows it located in Japan.

?

  • Author
2 hours ago, KhunBENQ said:

Ouch!

I did a tracert (routing) for 3BB to this server.

Seemingly going through US carriers!

One IP is 50.242.150.145. Geolocation shows Comcast Chicago!

 

 

This is interesting.

It does look like its going through US. 250ms makes sense if that was the case.

  • Author
2 hours ago, KhunBENQ said:

Other Japan addresses show ping's of about 120 ms though.

 

About this 104.160.154.1:

Two geolocation services show it as located in the US (Riot Games Inc).

One shows it located in Japan.

?

The IP is Riot's (US company) so I can see why some geolocation shows it as US. Im sure the server is in Japan since my ping is 3ms.

13 hours ago, SteveK said:

Can someone remove crossy's IP address from his post? It reveals his precise location, sure hid didn't intend to do that. 

 

No worries, the best I can geolocate to is Nonthaburi which is on the other side of the river ????

 

I do sometimes wonder just how accurately the, ahem "professional", locators can get from just an IP address, but I'm not exactly worried about it. 

 

"I don't want to know why you can't. I want to know how you can!"

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.