Kita ora ana gandhengane karo pamaréntah Thailand. Kanggo formulir TDAC resmi, bukak tdac.immigration.go.th.
Operasional
tdac.immigration.go.th
Kedadeyan pungkasan sing kacathet: up · Nov 25, 2025 19:00
Dianyari 1 menit kepungkurChecked every minute
Wektu Wangsulan Rata-rata
510 ms
Priksa Kacathet
16,445
Sela Priksa
Checked every minute
Dipantau Wiwit
May 7, 2025
Rasio Uptime Mlaku
24 Jam Pungkasan
100.000%
excellent
7 Dina Pungkasan
100.000%
excellent
30 Dina Pungkasan
99.815%
good
90 Dina Pungkasan
99.899%
good
Wektu Wangsulan Paling Anyar
Latency329 ms
Butuh kiriman TDAC sing dijamin?
AGENTS CO., LTD. ngirim sajroning 5 mènit, nyimpen draf, lan ngabari panjenengan nalika situs pamaréntah wis mari pulih.
Log Kedadeyan Anyar
Nov 25, 2025
13 dina kepungkurTotal Downtime · 42 mènit
UP
19:00 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
18:52 GMT+07:00CloudFlare TimeoutCloudFlare service can not connect to the website.
UP
18:23 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
18:03 GMT+07:00Service UnavailableThe service is temporarily overloaded.
UP
18:01 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
17:46 GMT+07:00Service UnavailableThe service is temporarily overloaded.
Nov 18, 2025
20 dina kepungkurTotal Downtime · 38 mènit
UP
19:59 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
19:58 GMT+07:00Internal Server ErrorThe server encountered an unexpected condition that prevented it from fulfilling the request.
UP
19:47 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
19:38 GMT+07:00Internal Server ErrorThe server encountered an unexpected condition that prevented it from fulfilling the request.
UP
19:28 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
19:24 GMT+07:00Internal Server ErrorThe server encountered an unexpected condition that prevented it from fulfilling the request.
UP
19:15 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
19:08 GMT+07:00Internal Server ErrorThe server encountered an unexpected condition that prevented it from fulfilling the request.
UP
18:52 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
18:35 GMT+07:00Internal Server ErrorThe server encountered an unexpected condition that prevented it from fulfilling the request.
Oct 23, 2025
46 dina kepungkurTotal Downtime · 1 mènit
UP
02:04 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
02:03 GMT+07:00Cloudflare TimeoutCloudflare service can not connect to the website.
Oct 16, 2025
53 dina kepungkurTotal Downtime · 9 mènit
UP
14:28 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
14:19 GMT+07:00Connection TimeoutThe response took so long that the connection timed out.
Oct 5, 2025
64 dina kepungkurTotal Downtime · 27 mènit
UP
13:05 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
12:38 GMT+07:00Connection TimeoutThe response took so long that the connection timed out.
Sep 26, 2025
73 dina kepungkurTotal Downtime · 14 mènit
UP
10:51 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
10:37 GMT+07:00Connection TimeoutThe response took so long that the connection timed out.
Aug 27, 2025
103 dina kepungkurTotal Downtime · 6 mènit
UP
21:45 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
21:43 GMT+07:00CloudFlare TimeoutCloudFlare service can not connect to the website.
UP
20:05 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
20:03 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
UP
18:43 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
18:42 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
UP
17:28 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
17:26 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
May 28, 2025
194 dina kepungkurTotal Downtime · 1 mènit
UP
15:38 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
15:37 GMT+07:00Connection TimeoutThe response took so long that the connection timed out.
May 14, 2025
208 dina kepungkurTotal Downtime · 4 mènit
UP
14:24 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
14:22 GMT+07:00CloudFlare TimeoutCloudFlare service can not connect to the website.
UP
13:31 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
13:30 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
UP
13:12 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
13:11 GMT+07:00Connection TimeoutThe response took so long that the connection timed out.
May 8, 2025
214 dina kepungkurTotal Downtime · 1h 58m
UP
16:32 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
16:31 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
UP
06:24 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
06:23 GMT+07:00CloudFlare TimeoutCloudFlare service can not connect to the website.
UP
05:30 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
05:28 GMT+07:00OKStandard response for successful HTTP requests.
UP
02:25 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
00:31 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
UP
00:29 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
00:28 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
May 7, 2025
215 dina kepungkurTotal Downtime · 2h 32m
UP
23:13 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
23:09 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
UP
22:36 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
22:35 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
UP
22:29 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
22:22 GMT+07:00Service UnavailableThe service is temporarily overloaded.
UP
21:58 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
21:57 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
UP
21:46 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
21:43 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
UP
20:51 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
20:46 GMT+07:00Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
UP
20:43 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
20:42 GMT+07:00Connection TimeoutThe response took so long that the connection timed out.
UP
20:02 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
18:38 GMT+07:00ForbiddenThe server understood the request, but cannot fulfill it.
UP
18:35 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
18:34 GMT+07:00Service UnavailableThe service is temporarily overloaded.
UP
16:37 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
16:28 GMT+07:00ForbiddenThe server understood the request, but cannot fulfill it.
UP
14:56 GMT+07:00OKStandard response for successful HTTP requests.
DOWN
14:20 GMT+07:00ForbiddenThe server understood the request, but cannot fulfill it.
STARTED
14:10 GMT+07:00Unknown errorThere was some other error.
Apa sing kudu ditindakake nalika TDAC mati
Sumber Resmi
Kita dudu sumber resmi; kita nggunakake pengawas mandiri saindenging donya sing mriksa tdac.immigration.go.th saben menit saka njero lan njaba Thailand.
Napa Iki Penting
Nalika portal resmi ora bisa diakses, para lelungan kudu nundha pangajuan utawa nggunakake layanan sing dipercaya. Kita langsung nampilake kedadeyan kasebut.
Penanganan Darurat TDAC
Yèn panjenengan teka sajroning 72 jam lan situs pamaréntah offline, AGENTS ngirim panyuwunan panjenengan tanpa biaya, nyimpen kanthi aman, lan langsung ngluncuraké pas layanan bali normal.
Carane Nanggapi
Yèn wektu mati kedadeyan, entèna nganti ana log UP utawa wènèhna AGENTS ngantriaké pangajuan panjenengan supaya otomatis dikirim nalika sistem imigrasi wis pulih.
Titik Kontak
Laporkna gangguan dawa menyang 1178 (Biro Imigrasi) utawa hubungi meja dhukungan kita ing [email protected].
Kita dudu situs web utawa sumber daya pemerintah. Kita berusaha kanggo nyedhiyakake informasi sing akurat lan nawakake bantuan kanggo para pelancong.