DNS response history for ns2.thaihealth.net

ns2.thaihealth.net 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 453 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.thaihealth.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

453 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.151.232.67

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.thaihealth.net

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:14 639233424567558554
404 ms 203.151.232.67
36 2026-08-26 11:56 639233414056832719
234 ms 203.151.232.67
35 2026-08-26 11:39 639233403515141099
250 ms 203.151.232.67
34 2026-08-26 10:44 639233370841350248
360 ms 203.151.232.67
33 2026-08-26 10:27 639233360361507238
380 ms 203.151.232.67
32 2026-08-26 10:09 639233350067824371
358 ms 203.151.232.67
31 2026-08-26 09:52 639233339545274518
2336 ms 203.151.232.67
30 2026-08-26 09:35 639233329214918079
381 ms 203.151.232.67
29 2026-08-26 09:17 639233318749762337
394 ms 203.151.232.67
28 2026-08-26 09:00 639233308387917838
1154 ms 203.151.232.67
27 2026-08-26 08:43 639233297961740122
407 ms 203.151.232.67
26 2026-08-26 08:25 639233287487159094
260 ms 203.151.232.67
25 2026-08-26 08:08 639233276995531707
282 ms 203.151.232.67
24 2026-08-26 07:50 639233266521568229
330 ms 203.151.232.67
23 2026-08-26 07:33 639233256081047431
389 ms 203.151.232.67
22 2026-08-26 06:39 639233223620132921
416 ms 203.151.232.67
21 2026-08-26 06:22 639233213287814244
375 ms 203.151.232.67
20 2026-08-26 06:04 639233202925983161
368 ms 203.151.232.67
19 2026-08-26 05:47 639233192644780696
413 ms 203.151.232.67
18 2026-08-26 05:30 639233182401183833
32 ms 203.151.232.67
17 2026-08-26 05:13 639233172074181051
409 ms 203.151.232.67
16 2026-08-26 04:56 639233161808421455
250 ms 203.151.232.67
15 2026-08-26 04:39 639233151357344052
420 ms 203.151.232.67
14 2026-08-26 04:21 639233141034116946
422 ms 203.151.232.67
13 2026-08-26 04:04 639233130828334142
430 ms 203.151.232.67
12 2026-08-26 03:47 639233120373450007
235 ms 203.151.232.67
11 2026-08-26 03:29 639233110066216193
253 ms 203.151.232.67
10 2026-08-26 02:36 639233078065410564
198 ms 203.151.232.67
9 2026-08-26 02:19 639233067787457832
376 ms 203.151.232.67
8 2026-08-26 02:02 639233057501801162
2008 ms 203.151.232.67
7 2026-08-26 01:45 639233047089431703
407 ms 203.151.232.67
6 2026-08-26 01:27 639233036754790688
362 ms 203.151.232.67
5 2026-08-26 01:10 639233026412602472
242 ms 203.151.232.67
4 2026-08-26 00:53 639233016064066127
365 ms 203.151.232.67
3 2026-08-26 00:36 639233005922655772
272 ms 203.151.232.67
2 2026-08-26 00:19 639232995672256907
365 ms 203.151.232.67
1 2026-08-26 00:02 639232985300872416
226 ms 203.151.232.67