DNS response history for ns4.anazana.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

474 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.108.134.118

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 ns4.anazana.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
37 2026-08-25 12:49 639232587225721862
27 ms 65.108.134.118
36 2026-08-25 12:32 639232576780683689
16 ms 65.108.134.118
35 2026-08-25 12:14 639232566381512620
38 ms 65.108.134.118
34 2026-08-25 11:57 639232556111768563
31 ms 65.108.134.118
33 2026-08-25 11:40 639232545839529039
41 ms 65.108.134.118
32 2026-08-25 11:23 639232535349285207
47 ms 65.108.134.118
31 2026-08-25 11:05 639232524938080723
13 ms 65.108.134.118
30 2026-08-25 10:11 639232492740373468
27 ms 65.108.134.118
29 2026-08-25 09:54 639232482235303141
63 ms 65.108.134.118
28 2026-08-25 09:37 639232471861770303
2024 ms 65.108.134.118
27 2026-08-25 09:20 639232461630217327
22 ms 65.108.134.118
26 2026-08-25 09:02 639232451282965990
107 ms 65.108.134.118
25 2026-08-25 08:45 639232440814614938
34 ms 65.108.134.118
24 2026-08-25 08:28 639232430410720425
47 ms 65.108.134.118
23 2026-08-25 08:10 639232420003096185
39 ms 65.108.134.118
22 2026-08-25 07:53 639232409467287444
41 ms 65.108.134.118
21 2026-08-25 07:35 639232399077195997
4032 ms 65.108.134.118
20 2026-08-25 07:18 639232388731528337
65 ms 65.108.134.118
19 2026-08-25 07:01 639232378288598612
2041 ms 65.108.134.118
18 2026-08-25 06:07 639232346196373643
27 ms 65.108.134.118
17 2026-08-25 05:50 639232336112370741
113 ms 65.108.134.118
16 2026-08-25 05:34 639232326146508970
60 ms 65.108.134.118
15 2026-08-25 05:17 639232316189381720
21 ms 65.108.134.118
14 2026-08-25 05:01 639232306217998913
41 ms 65.108.134.118
13 2026-08-25 04:44 639232296255744174
30 ms 65.108.134.118
12 2026-08-25 04:27 639232286095760789
26 ms 65.108.134.118
11 2026-08-25 04:10 639232276086186273
7 ms 65.108.134.118
10 2026-08-25 03:53 639232265900986425
71 ms 65.108.134.118
9 2026-08-25 03:36 639232255723518075
2037 ms 65.108.134.118
8 2026-08-25 03:19 639232245484452890
28 ms 65.108.134.118
7 2026-08-25 03:02 639232235157175331
71 ms 65.108.134.118
6 2026-08-25 02:09 639232203197189095
27 ms 65.108.134.118
5 2026-08-25 01:52 639232192844564298
16 ms 65.108.134.118
4 2026-08-25 01:34 639232182496008942
14 ms 65.108.134.118
3 2026-08-25 01:17 639232172197053132
49 ms 65.108.134.118
2 2026-08-25 00:24 639232140250307418
4097 ms 65.108.134.118
1 2026-08-25 00:07 639232129927860324
2033 ms 65.108.134.118