DNS response history for ns2.thailink.org

ns2.thailink.org is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 524 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.thailink.org.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

524 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

139.162.18.142

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.thailink.org

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
34 2026-08-26 11:34 639233403515141099
170 ms 139.162.18.142
33 2026-08-26 10:39 639233370841350248
7 ms 139.162.18.142
32 2026-08-26 10:22 639233360361507238
156 ms 139.162.18.142
31 2026-08-26 10:05 639233350067824371
35 ms 139.162.18.142
30 2026-08-26 09:48 639233339545274518
295 ms 139.162.18.142
29 2026-08-26 09:30 639233329214918079
286 ms 139.162.18.142
28 2026-08-26 09:13 639233318749762337
267 ms 139.162.18.142
27 2026-08-26 08:55 639233308387917838
427 ms 139.162.18.142
26 2026-08-26 08:38 639233297961740122
384 ms 139.162.18.142
25 2026-08-26 08:21 639233287487159094
2184 ms 139.162.18.142
24 2026-08-26 08:03 639233276995531707
498 ms 139.162.18.142
23 2026-08-26 07:45 639233266521568229
403 ms 139.162.18.142
22 2026-08-26 07:28 639233256081047431
497 ms 139.162.18.142
21 2026-08-26 06:34 639233223620132921
279 ms 139.162.18.142
20 2026-08-26 06:17 639233213287814244
4153 ms 139.162.18.142
19 2026-08-26 06:00 639233202925983161
230 ms 139.162.18.142
18 2026-08-26 05:42 639233192644780696
399 ms 139.162.18.142
17 2026-08-26 05:25 639233182401183833
161 ms 139.162.18.142
16 2026-08-26 05:08 639233172074181051
308 ms 139.162.18.142
15 2026-08-26 04:51 639233161808421455
310 ms 139.162.18.142
14 2026-08-26 04:34 639233151357344052
276 ms 139.162.18.142
13 2026-08-26 04:16 639233141034116946
296 ms 139.162.18.142
12 2026-08-26 03:59 639233130828334142
535 ms 139.162.18.142
11 2026-08-26 03:42 639233120373450007
289 ms 139.162.18.142
10 2026-08-26 03:25 639233110066216193
812 ms 139.162.18.142
9 2026-08-26 02:31 639233078065410564
303 ms 139.162.18.142
8 2026-08-26 02:14 639233067787457832
481 ms 139.162.18.142
7 2026-08-26 01:57 639233057501801162
7 ms 139.162.18.142
6 2026-08-26 01:40 639233047089431703
150 ms 139.162.18.142
5 2026-08-26 01:23 639233036754790688
169 ms 139.162.18.142
4 2026-08-26 01:05 639233026412602472
280 ms 139.162.18.142
3 2026-08-26 00:48 639233016064066127
276 ms 139.162.18.142
2 2026-08-26 00:31 639233005922655772
2299 ms 139.162.18.142
1 2026-08-26 00:14 639232995672256907
208 ms 139.162.18.142