Nothing Is Working

[niller74]

CAT, TOT and TT&T seems to have come to a complete stop....

Getting throughput of less that 5kb/s on all 3.

I wonder if this has anything to do with implementation of their great logging requirements.

On top of that WE-TV is <deleted> so the signal show for 1 sec then go off for 3-4 sec.

Guess it's time to read a book.

[Guest Reimar]

CAT, TOT and TT&T seems to have come to a complete stop....

Getting throughput of less that 5kb/s on all 3.

I wonder if this has anything to do with implementation of their great logging requirements.

On top of that WE-TV is <deleted> so the signal show for 1 sec then go off for 3-4 sec.

Guess it's time to read a book.

No problems at TRUE in Samut Prakarn. Everythings works just normal. Maybe you off your Router/Modem for a few minutes and om again. And if that didn't works, maybe you can check in your neiboroughhood they have the same problem?!

Cheers.

[Rice_King]

Discounting your vague subject line, I am experiencing no aggravations with True today in Chiang Mai.

[Khun Jack]

Phuket TOT internet was down for about 12 hours.

[XCaSQz]

TOT in Jomtien is very very slow today

usually I have 50ms ping within Thailand but today it comes to 400ms

I can't play any online games but torrents are good as usual (specially those with lots of seeds )

Edited August 24, 2008 by XCaSQz

[dttk0009]

It seems True is routing its traffic through CAT's international lines today, which are bringing much of the international traffic into a huge traffic jam. Here's a tracert to a server in Australia. As you can see, true's gateways are fine until they hit CAT's IP addresses:

NOTE JUMPS 9-12

Tracing route to gw3.mel1.alter.net [210.80.0.223]

over a maximum of 30 hops:

1 18 ms 18 ms 19 ms ppp-124-120-230-1.revip2.asianet.co.th [124.120.230.1]

2 17 ms 19 ms 18 ms ppp-210-86-189-50.revip.asianet.co.th [210.86.189.50]

3 22 ms 24 ms 20 ms 10.169.50.1

4 20 ms 22 ms 21 ms 58-97-25-102.static.asianet.co.th [58.97.25.102]

5 19 ms 22 ms 19 ms 61-90-132-85.static.asianet.co.th [61.90.132.85]

6 19 ms 19 ms 18 ms 61-90-254-89.static.asianet.co.th [61.90.254.89]

7 20 ms 18 ms 19 ms 203-144-144-27.static.asianet.co.th [203.144.144.27]

8 21 ms 19 ms 19 ms 61-91-210-1.static.asianet.co.th [61.91.210.1]

9 239 ms 241 ms 244 ms 202.47.254.25

10 245 ms 243 ms 239 ms 202.47.253.146

11 288 ms 256 ms 249 ms 61.19.9.2

12 327 ms 324 ms 326 ms 203.103.244.245

13 324 ms 324 ms 321 ms 0.so-2-0-0.XT1.HKG2.Alter.Net [210.80.3.209]

14 456 ms * 454 ms 0.so-0-1-0.XT3.SYD2.ALTER.NET [210.80.50.73]

15 463 ms 467 ms 468 ms so-0-1-0.XL1.MEL1.ALTER.NET [210.80.33.106]

16 467 ms 519 ms 464 ms loopback0.gw3.mel1.alter.net [210.80.0.223]

Trace complete.

[joncl]

It seems True is routing its traffic through CAT's international lines today, which are bringing much of the international traffic into a huge traffic jam. Here's a tracert to a server in Australia. As you can see, true's gateways are fine until they hit CAT's IP addresses:

NOTE JUMPS 9-12

Tracing route to gw3.mel1.alter.net [210.80.0.223]

over a maximum of 30 hops:

1 18 ms 18 ms 19 ms ppp-124-120-230-1.revip2.asianet.co.th [124.120.230.1]

2 17 ms 19 ms 18 ms ppp-210-86-189-50.revip.asianet.co.th [210.86.189.50]

3 22 ms 24 ms 20 ms 10.169.50.1

4 20 ms 22 ms 21 ms 58-97-25-102.static.asianet.co.th [58.97.25.102]

5 19 ms 22 ms 19 ms 61-90-132-85.static.asianet.co.th [61.90.132.85]

6 19 ms 19 ms 18 ms 61-90-254-89.static.asianet.co.th [61.90.254.89]

7 20 ms 18 ms 19 ms 203-144-144-27.static.asianet.co.th [203.144.144.27]

8 21 ms 19 ms 19 ms 61-91-210-1.static.asianet.co.th [61.91.210.1]

9 239 ms 241 ms 244 ms 202.47.254.25

10 245 ms 243 ms 239 ms 202.47.253.146

11 288 ms 256 ms 249 ms 61.19.9.2

12 327 ms 324 ms 326 ms 203.103.244.245

13 324 ms 324 ms 321 ms 0.so-2-0-0.XT1.HKG2.Alter.Net [210.80.3.209]

14 456 ms * 454 ms 0.so-0-1-0.XT3.SYD2.ALTER.NET [210.80.50.73]

15 463 ms 467 ms 468 ms so-0-1-0.XL1.MEL1.ALTER.NET [210.80.33.106]

16 467 ms 519 ms 464 ms loopback0.gw3.mel1.alter.net [210.80.0.223]

Trace complete.

True in BKK ;

ping 210.80.0.223

PING 210.80.0.223 (210.80.0.223) 56(84) bytes of data.

64 bytes from 210.80.0.223: icmp_seq=1 ttl=48 time=244 ms

64 bytes from 210.80.0.223: icmp_seq=2 ttl=48 time=233 ms

[RKASA]

same address

traceroute 210.80.0.223

traceroute to 210.80.0.223 (210.80.0.223), 30 hops max, 38 byte packets

 1 192.168.5.100 (192.168.5.100) 0.738 ms 0.461 ms 0.375 ms

 2 192.168.1.57 (192.168.1.57) 892.328 ms 918.528 ms 813.716 ms

 3 192.168.100.49 (192.168.100.49) 974.053 ms 899.690 ms 834.735 ms

 4 192.168.100.18 (192.168.100.18) 943.136 ms 806.595 ms 895.763 ms

 5 10.159.1.209 (10.159.1.209) 975.002 ms 892.005 ms 830.154 ms

 6 203.113.24.1 (203.113.24.1) 979.256 ms 839.490 ms 939.439 ms

5 to 30 second delay unrecorded

 7 203.113.13.145 (203.113.13.145) 1014.267 ms 1076.480 ms 802.045 ms

another 5 to 30 delay unrecorded

 8 203.113.13.126 (203.113.13.126) 922.174 ms 1036.278 ms 851.930 ms

another 5 to 30 delay not record

 9 203.113.24.237 (203.113.24.237) 946.065 ms 933.647 ms 821.969 ms

another, these between 8 and 9 are new before like the last 3 months its been only

between 6 and 7

10 61.19.10.13 (61.19.10.13) 841.800 ms 1115.485 ms 955.842 ms

11 202.47.253.146 (202.47.253.146) 937.907 ms 1034.913 ms 1052.140 ms

12 61.19.9.6 (61.19.9.6) 1094.922 ms 1000.502 ms 1007.736 ms

13 203.103.244.245 (203.103.244.245) 1034.640 ms 1051.074 ms 1364.591 ms

14 210.80.3.33 (210.80.3.33) 1118.891 ms 1205.449 ms 1133.865 ms

15 0.so-0-1-0.XT4.SYD4.ALTER.NET (210.80.50.77) 1108.494 ms 1323.723 ms 1248.112 ms

16 so-0-1-0.XL2.MEL1.ALTER.NET (210.80.33.10) 1164.768 ms 1136.643 ms 1152.362 ms

17 * * *

18 * * *

19 * * *

20 * * *

21 * * *

22 * * *

23 * * *

ToT seems to be unable to understand or fix it for three months.