DNS response history for ns2.aranzee.com

ns2.aranzee.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 35 DNS check records, 35 successful responses, 0 failed responses, and 314 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.aranzee.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

314 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

166.1.136.4

Most recently resolved hosting IP on selected date

Successful Responses

35

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.aranzee.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
35 2026-08-25 12:16 639232566381512620
70 ms 166.1.136.4
34 2026-08-25 11:58 639232556111768563
47 ms 166.1.136.4
33 2026-08-25 11:41 639232545839529039
91 ms 166.1.136.4
32 2026-08-25 11:24 639232535349285207
58 ms 166.1.136.4
31 2026-08-25 11:06 639232524938080723
78 ms 166.1.136.4
30 2026-08-25 10:13 639232492740373468
113 ms 166.1.136.4
29 2026-08-25 09:55 639232482235303141
90 ms 166.1.136.4
28 2026-08-25 09:38 639232471861770303
118 ms 166.1.136.4
27 2026-08-25 09:21 639232461630217327
74 ms 166.1.136.4
26 2026-08-25 09:04 639232451282965990
64 ms 166.1.136.4
25 2026-08-25 08:46 639232440814614938
2056 ms 166.1.136.4
24 2026-08-25 08:29 639232430410720425
117 ms 166.1.136.4
23 2026-08-25 08:12 639232420003096185
84 ms 166.1.136.4
22 2026-08-25 07:54 639232409467287444
2058 ms 166.1.136.4
21 2026-08-25 07:37 639232399077195997
111 ms 166.1.136.4
20 2026-08-25 07:19 639232388731528337
2062 ms 166.1.136.4
19 2026-08-25 07:02 639232378288598612
87 ms 166.1.136.4
18 2026-08-25 06:08 639232346196373643
92 ms 166.1.136.4
17 2026-08-25 05:52 639232336112370741
70 ms 166.1.136.4
16 2026-08-25 05:35 639232326146508970
90 ms 166.1.136.4
15 2026-08-25 05:18 639232316189381720
89 ms 166.1.136.4
14 2026-08-25 05:02 639232306217998913
82 ms 166.1.136.4
13 2026-08-25 04:45 639232296255744174
98 ms 166.1.136.4
12 2026-08-25 04:28 639232286095760789
93 ms 166.1.136.4
11 2026-08-25 04:12 639232276086186273
72 ms 166.1.136.4
10 2026-08-25 03:55 639232265900986425
93 ms 166.1.136.4
9 2026-08-25 03:38 639232255723518075
97 ms 166.1.136.4
8 2026-08-25 03:21 639232245484452890
109 ms 166.1.136.4
7 2026-08-25 03:03 639232235157175331
101 ms 166.1.136.4
6 2026-08-25 02:10 639232203197189095
2137 ms 166.1.136.4
5 2026-08-25 01:53 639232192844564298
53 ms 166.1.136.4
4 2026-08-25 01:36 639232182496008942
92 ms 166.1.136.4
3 2026-08-25 01:18 639232172197053132
75 ms 166.1.136.4
2 2026-08-25 00:25 639232140250307418
107 ms 166.1.136.4
1 2026-08-25 00:08 639232129927860324
75 ms 166.1.136.4