DNS response history for ns2.hollowmere.club

ns2.hollowmere.club 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 31 DNS check records, 31 successful responses, 0 failed responses, and 306 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.hollowmere.club.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

306 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

188.209.136.129

Most recently resolved hosting IP on selected date

Successful Responses

31

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.hollowmere.club

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
31 2026-08-25 11:08 639232524938080723
100 ms 188.209.136.129
30 2026-08-25 10:14 639232492740373468
129 ms 188.209.136.129
29 2026-08-25 09:56 639232482235303141
130 ms 188.209.136.129
28 2026-08-25 09:39 639232471861770303
71 ms 188.209.136.129
27 2026-08-25 09:22 639232461630217327
121 ms 188.209.136.129
26 2026-08-25 09:05 639232451282965990
85 ms 188.209.136.129
25 2026-08-25 08:47 639232440814614938
9 ms 188.209.136.129
24 2026-08-25 08:30 639232430410720425
2024 ms 188.209.136.129
23 2026-08-25 08:13 639232420003096185
82 ms 188.209.136.129
22 2026-08-25 07:55 639232409467287444
88 ms 188.209.136.129
21 2026-08-25 07:38 639232399077195997
119 ms 188.209.136.129
20 2026-08-25 07:20 639232388731528337
77 ms 188.209.136.129
19 2026-08-25 07:03 639232378288598612
129 ms 188.209.136.129
18 2026-08-25 06:10 639232346196373643
112 ms 188.209.136.129
17 2026-08-25 05:53 639232336112370741
147 ms 188.209.136.129
16 2026-08-25 05:36 639232326146508970
114 ms 188.209.136.129
15 2026-08-25 05:20 639232316189381720
3 ms 188.209.136.129
14 2026-08-25 05:03 639232306217998913
112 ms 188.209.136.129
13 2026-08-25 04:46 639232296255744174
78 ms 188.209.136.129
12 2026-08-25 04:29 639232286095760789
124 ms 188.209.136.129
11 2026-08-25 04:13 639232276086186273
105 ms 188.209.136.129
10 2026-08-25 03:56 639232265900986425
564 ms 188.209.136.129
9 2026-08-25 03:39 639232255723518075
2103 ms 188.209.136.129
8 2026-08-25 03:22 639232245484452890
2173 ms 188.209.136.129
7 2026-08-25 03:05 639232235157175331
111 ms 188.209.136.129
6 2026-08-25 02:11 639232203197189095
75 ms 188.209.136.129
5 2026-08-25 01:54 639232192844564298
95 ms 188.209.136.129
4 2026-08-25 01:37 639232182496008942
103 ms 188.209.136.129
3 2026-08-25 01:20 639232172197053132
114 ms 188.209.136.129
2 2026-08-25 00:26 639232140250307418
84 ms 188.209.136.129
1 2026-08-25 00:09 639232129927860324
114 ms 188.209.136.129