DNS response history for ns4.naostech.com

ns4.naostech.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-25. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 2240 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 ns4.naostech.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

2240 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.129.31.21

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns4.naostech.com

Showing DNS history for 2026-08-25 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
29 2026-08-25 09:49 639232471861770303
2054 ms 212.129.31.21
28 2026-08-25 09:32 639232461630217327
2050 ms 212.129.31.21
27 2026-08-25 09:15 639232451282965990
4028 ms 212.129.31.21
26 2026-08-25 08:57 639232440814614938
2025 ms 212.129.31.21
25 2026-08-25 08:40 639232430410720425
2028 ms 212.129.31.21
24 2026-08-25 08:23 639232420003096185
2027 ms 212.129.31.21
23 2026-08-25 08:05 639232409467287444
2021 ms 212.129.31.21
22 2026-08-25 07:48 639232399077195997
2030 ms 212.129.31.21
21 2026-08-25 07:30 639232388731528337
2030 ms 212.129.31.21
20 2026-08-25 07:13 639232378288598612
2025 ms 212.129.31.21
19 2026-08-25 06:19 639232346196373643
2026 ms 212.129.31.21
18 2026-08-25 06:02 639232336112370741
2024 ms 212.129.31.21
17 2026-08-25 05:45 639232326146508970
2026 ms 212.129.31.21
16 2026-08-25 05:29 639232316189381720
4027 ms 212.129.31.21
15 2026-08-25 05:12 639232306217998913
2127 ms 212.129.31.21
14 2026-08-25 04:56 639232296255744174
2021 ms 212.129.31.21
13 2026-08-25 04:39 639232286095760789
2048 ms 212.129.31.21
12 2026-08-25 04:22 639232276086186273
2029 ms 212.129.31.21
11 2026-08-25 04:05 639232265900986425
2045 ms 212.129.31.21
10 2026-08-25 03:49 639232255723518075
2022 ms 212.129.31.21
9 2026-08-25 03:31 639232245484452890
4028 ms 212.129.31.21
8 2026-08-25 03:14 639232235157175331
2025 ms 212.129.31.21
7 2026-08-25 02:21 639232203197189095
2051 ms 212.129.31.21
6 2026-08-25 02:04 639232192844564298
2025 ms 212.129.31.21
5 2026-08-25 01:47 639232182496008942
2020 ms 212.129.31.21
4 2026-08-25 01:29 639232172197053132
2026 ms 212.129.31.21
3 2026-08-25 00:36 639232140250307418
2026 ms 212.129.31.21
2 2026-08-25 00:19 639232129927860324
2027 ms 212.129.31.21
1 2026-08-25 00:02 639232119551972438
2019 ms 212.129.31.21