DNS response history for ns2.moneopolicy.org

ns2.moneopolicy.org 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 33 DNS check records, 33 successful responses, 0 failed responses, and 113 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.moneopolicy.org.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

113 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.5.5.204

Most recently resolved hosting IP on selected date

Successful Responses

33

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.moneopolicy.org

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
33 2026-08-25 11:34 639232535349285207
104 ms 5.5.5.204
32 2026-08-25 11:17 639232524938080723
98 ms 5.5.5.204
31 2026-08-25 10:23 639232492740373468
84 ms 5.5.5.204
30 2026-08-25 10:06 639232482235303141
96 ms 5.5.5.204
29 2026-08-25 09:48 639232471861770303
200 ms 5.5.5.204
28 2026-08-25 09:31 639232461630217327
273 ms 5.5.5.204
27 2026-08-25 09:14 639232451282965990
4 ms 5.5.5.204
26 2026-08-25 08:56 639232440814614938
102 ms 5.5.5.204
25 2026-08-25 08:39 639232430410720425
201 ms 5.5.5.204
24 2026-08-25 08:22 639232420003096185
202 ms 5.5.5.204
23 2026-08-25 08:04 639232409467287444
333 ms 5.5.5.204
22 2026-08-25 07:47 639232399077195997
106 ms 5.5.5.204
21 2026-08-25 07:29 639232388731528337
95 ms 5.5.5.204
20 2026-08-25 07:12 639232378288598612
214 ms 5.5.5.204
19 2026-08-25 06:18 639232346196373643
3 ms 5.5.5.204
18 2026-08-25 06:01 639232336112370741
191 ms 5.5.5.204
17 2026-08-25 05:45 639232326146508970
3 ms 5.5.5.204
16 2026-08-25 05:28 639232316189381720
3 ms 5.5.5.204
15 2026-08-25 05:12 639232306217998913
2 ms 5.5.5.204
14 2026-08-25 04:55 639232296255744174
61 ms 5.5.5.204
13 2026-08-25 04:38 639232286095760789
61 ms 5.5.5.204
12 2026-08-25 04:21 639232276086186273
93 ms 5.5.5.204
11 2026-08-25 04:05 639232265900986425
98 ms 5.5.5.204
10 2026-08-25 03:48 639232255723518075
86 ms 5.5.5.204
9 2026-08-25 03:31 639232245484452890
101 ms 5.5.5.204
8 2026-08-25 03:14 639232235157175331
102 ms 5.5.5.204
7 2026-08-25 02:20 639232203197189095
91 ms 5.5.5.204
6 2026-08-25 02:03 639232192844564298
114 ms 5.5.5.204
5 2026-08-25 01:46 639232182496008942
100 ms 5.5.5.204
4 2026-08-25 01:29 639232172197053132
87 ms 5.5.5.204
3 2026-08-25 00:35 639232140250307418
99 ms 5.5.5.204
2 2026-08-25 00:18 639232129927860324
224 ms 5.5.5.204
1 2026-08-25 00:01 639232119551972438
96 ms 5.5.5.204