DNS response history for ns.saer-thailand.com

ns.saer-thailand.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 34 DNS check records, 34 successful responses, 0 failed responses, and 417 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 ns.saer-thailand.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

417 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

150.107.31.49

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 ns.saer-thailand.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
34 2026-08-26 10:44 639233370841350248
387 ms 150.107.31.49
33 2026-08-26 10:27 639233360361507238
1047 ms 150.107.31.49
32 2026-08-26 10:09 639233350067824371
374 ms 150.107.31.49
31 2026-08-26 09:52 639233339545274518
388 ms 150.107.31.49
30 2026-08-26 09:35 639233329214918079
9 ms 150.107.31.49
29 2026-08-26 09:17 639233318749762337
212 ms 150.107.31.49
28 2026-08-26 09:00 639233308387917838
383 ms 150.107.31.49
27 2026-08-26 08:43 639233297961740122
392 ms 150.107.31.49
26 2026-08-26 08:25 639233287487159094
375 ms 150.107.31.49
25 2026-08-26 08:08 639233276995531707
615 ms 150.107.31.49
24 2026-08-26 07:50 639233266521568229
378 ms 150.107.31.49
23 2026-08-26 07:33 639233256081047431
380 ms 150.107.31.49
22 2026-08-26 06:39 639233223620132921
384 ms 150.107.31.49
21 2026-08-26 06:22 639233213287814244
2191 ms 150.107.31.49
20 2026-08-26 06:04 639233202925983161
335 ms 150.107.31.49
19 2026-08-26 05:47 639233192644780696
32 ms 150.107.31.49
18 2026-08-26 05:30 639233182401183833
372 ms 150.107.31.49
17 2026-08-26 05:13 639233172074181051
379 ms 150.107.31.49
16 2026-08-26 04:56 639233161808421455
189 ms 150.107.31.49
15 2026-08-26 04:38 639233151357344052
375 ms 150.107.31.49
14 2026-08-26 04:21 639233141034116946
34 ms 150.107.31.49
13 2026-08-26 04:04 639233130828334142
371 ms 150.107.31.49
12 2026-08-26 03:47 639233120373450007
401 ms 150.107.31.49
11 2026-08-26 03:29 639233110066216193
365 ms 150.107.31.49
10 2026-08-26 02:36 639233078065410564
374 ms 150.107.31.49
9 2026-08-26 02:19 639233067787457832
384 ms 150.107.31.49
8 2026-08-26 02:02 639233057501801162
392 ms 150.107.31.49
7 2026-08-26 01:45 639233047089431703
372 ms 150.107.31.49
6 2026-08-26 01:27 639233036754790688
390 ms 150.107.31.49
5 2026-08-26 01:10 639233026412602472
385 ms 150.107.31.49
4 2026-08-26 00:53 639233016064066127
376 ms 150.107.31.49
3 2026-08-26 00:36 639233005922655772
381 ms 150.107.31.49
2 2026-08-26 00:19 639232995672256907
370 ms 150.107.31.49
1 2026-08-26 00:02 639232985300872416
375 ms 150.107.31.49