DNS response history for ns2.chaengsom.com

ns2.chaengsom.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-24. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 276 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.chaengsom.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

276 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

141.98.19.29

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

Showing DNS history for 2026-08-24 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-24 15:37 639231818080917481
366 ms 141.98.19.29
36 2026-08-24 15:20 639231807961539652
386 ms 141.98.19.29
35 2026-08-24 15:03 639231797631669865
365 ms 141.98.19.29
34 2026-08-24 14:10 639231765923559455
369 ms 141.98.19.29
33 2026-08-24 13:53 639231755868832964
370 ms 141.98.19.29
32 2026-08-24 13:36 639231745628278877
365 ms 141.98.19.29
31 2026-08-24 13:19 639231735407682062
321 ms 141.98.19.29
30 2026-08-24 12:26 639231703815441688
3 ms 141.98.19.29
29 2026-08-24 12:10 639231693747052549
376 ms 141.98.19.29
28 2026-08-24 11:53 639231683712487276
387 ms 141.98.19.29
27 2026-08-24 11:36 639231673513573868
387 ms 141.98.19.29
26 2026-08-24 10:43 639231641791249939
4 ms 141.98.19.29
25 2026-08-24 10:27 639231631866211033
378 ms 141.98.19.29
24 2026-08-24 10:10 639231621644955316
248 ms 141.98.19.29
23 2026-08-24 09:53 639231611478799259
376 ms 141.98.19.29
22 2026-08-24 09:00 639231579923718211
3 ms 141.98.19.29
21 2026-08-24 08:43 639231569810702936
382 ms 141.98.19.29
20 2026-08-24 08:26 639231559762411619
378 ms 141.98.19.29
19 2026-08-24 08:10 639231549663595407
374 ms 141.98.19.29
18 2026-08-24 07:17 639231518076817246
3 ms 141.98.19.29
17 2026-08-24 07:00 639231508078650885
2 ms 141.98.19.29
16 2026-08-24 06:44 639231498210697093
374 ms 141.98.19.29
15 2026-08-24 06:27 639231488109699360
376 ms 141.98.19.29
14 2026-08-24 05:35 639231456772510692
375 ms 141.98.19.29
13 2026-08-24 05:18 639231447084631185
380 ms 141.98.19.29
12 2026-08-24 05:02 639231437208519473
2 ms 141.98.19.29
11 2026-08-24 04:45 639231427209627490
374 ms 141.98.19.29
10 2026-08-24 03:53 639231395791246644
7 ms 141.98.19.29
9 2026-08-24 03:37 639231386075551458
375 ms 141.98.19.29
8 2026-08-24 03:20 639231376208713791
2 ms 141.98.19.29
7 2026-08-24 03:04 639231366170589276
380 ms 141.98.19.29
6 2026-08-24 02:11 639231334732159368
353 ms 141.98.19.29
5 2026-08-24 01:55 639231325035670078
374 ms 141.98.19.29
4 2026-08-24 01:39 639231315132253837
373 ms 141.98.19.29
3 2026-08-24 01:22 639231305014280808
3 ms 141.98.19.29
2 2026-08-24 00:29 639231273779380675
372 ms 141.98.19.29
1 2026-08-24 00:14 639231264180839154
252 ms 141.98.19.29