DNS response history for ns2.thaiload.com

ns2.thaiload.com 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 37 DNS check records, 37 successful responses, 0 failed responses, and 394 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.thaiload.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

394 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.151.233.8

Most recently resolved hosting IP on selected date

Successful Responses

37

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.thaiload.com

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
37 2026-08-26 12:18 639233434974187439
45 ms 203.151.233.8
36 2026-08-26 12:00 639233424567558554
60 ms 203.151.233.8
35 2026-08-26 11:43 639233414056832719
118 ms 203.151.233.8
34 2026-08-26 11:25 639233403515141099
146 ms 203.151.233.8
33 2026-08-26 10:31 639233370841350248
40 ms 203.151.233.8
32 2026-08-26 10:13 639233360361507238
2062 ms 203.151.233.8
31 2026-08-26 09:56 639233350067824371
12 ms 203.151.233.8
30 2026-08-26 09:39 639233339545274518
58 ms 203.151.233.8
29 2026-08-26 09:22 639233329214918079
88 ms 203.151.233.8
28 2026-08-26 09:04 639233318749762337
50 ms 203.151.233.8
27 2026-08-26 08:47 639233308387917838
175 ms 203.151.233.8
26 2026-08-26 08:29 639233297961740122
2065 ms 203.151.233.8
25 2026-08-26 08:12 639233287487159094
119 ms 203.151.233.8
24 2026-08-26 07:55 639233276995531707
54 ms 203.151.233.8
23 2026-08-26 07:37 639233266521568229
18 ms 203.151.233.8
22 2026-08-26 07:20 639233256081047431
153 ms 203.151.233.8
21 2026-08-26 06:26 639233223620132921
44 ms 203.151.233.8
20 2026-08-26 06:08 639233213287814244
2048 ms 203.151.233.8
19 2026-08-26 05:51 639233202925983161
109 ms 203.151.233.8
18 2026-08-26 05:34 639233192644780696
2044 ms 203.151.233.8
17 2026-08-26 05:17 639233182401183833
193 ms 203.151.233.8
16 2026-08-26 05:00 639233172074181051
27 ms 203.151.233.8
15 2026-08-26 04:43 639233161808421455
70 ms 203.151.233.8
14 2026-08-26 04:25 639233151357344052
64 ms 203.151.233.8
13 2026-08-26 04:08 639233141034116946
10 ms 203.151.233.8
12 2026-08-26 03:51 639233130828334142
9 ms 203.151.233.8
11 2026-08-26 03:34 639233120373450007
2018 ms 203.151.233.8
10 2026-08-26 03:16 639233110066216193
125 ms 203.151.233.8
9 2026-08-26 02:23 639233078065410564
45 ms 203.151.233.8
8 2026-08-26 02:06 639233067787457832
2056 ms 203.151.233.8
7 2026-08-26 01:49 639233057501801162
62 ms 203.151.233.8
6 2026-08-26 01:31 639233047089431703
19 ms 203.151.233.8
5 2026-08-26 01:14 639233036754790688
36 ms 203.151.233.8
4 2026-08-26 00:57 639233026412602472
80 ms 203.151.233.8
3 2026-08-26 00:40 639233016064066127
56 ms 203.151.233.8
2 2026-08-26 00:23 639233005922655772
148 ms 203.151.233.8
1 2026-08-26 00:06 639232995672256907
34 ms 203.151.233.8