DNS response history for ns2.closepure.com

ns2.closepure.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-12. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 475 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.closepure.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

475 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-12 23:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.101.22.33

Most recently resolved hosting IP on selected date

Successful Responses

32

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.closepure.com

Showing DNS history for 2026-08-12 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
32 2026-08-12 23:48 639221744107644868
41 ms 185.101.22.33
31 2026-08-12 23:48 639221744107644868
41 ms 188.209.136.91
30 2026-08-12 23:33 639221735030187244
38 ms 185.101.22.33
29 2026-08-12 23:33 639221735030187244
38 ms 188.209.136.91
28 2026-08-12 23:18 639221725815508109
261 ms 185.101.22.33
27 2026-08-12 23:18 639221725815508109
261 ms 188.209.136.91
26 2026-08-12 22:26 639221694790955973
694 ms 188.209.136.91
25 2026-08-12 22:26 639221694790955973
694 ms 185.101.22.33
24 2026-08-12 20:47 639221635456432556
46 ms 188.209.136.91
23 2026-08-12 20:47 639221635456432556
46 ms 185.101.22.33
22 2026-08-12 19:09 639221576664330059
700 ms 188.209.136.91
21 2026-08-12 19:09 639221576664330059
700 ms 185.101.22.33
20 2026-08-12 17:31 639221517673834934
476 ms 188.209.136.91
19 2026-08-12 17:31 639221517673834934
476 ms 185.101.22.33
18 2026-08-12 15:51 639221457655914645
696 ms 188.209.136.91
17 2026-08-12 15:51 639221457655914645
696 ms 185.101.22.33
16 2026-08-12 14:11 639221397761278719
701 ms 188.209.136.91
15 2026-08-12 14:11 639221397761278719
701 ms 185.101.22.33
14 2026-08-12 12:31 639221337226647415
260 ms 188.209.136.91
13 2026-08-12 12:31 639221337226647415
260 ms 185.101.22.33
12 2026-08-12 10:51 639221277089610470
683 ms 185.101.22.33
11 2026-08-12 10:51 639221277089610470
683 ms 188.209.136.91
10 2026-08-12 09:10 639221216797540533
683 ms 185.101.22.33
9 2026-08-12 09:10 639221216797540533
683 ms 188.209.136.91
8 2026-08-12 07:30 639221157276484143
262 ms 185.101.22.33
7 2026-08-12 07:30 639221157276484143
262 ms 188.209.136.91
6 2026-08-12 05:51 639221097816416095
687 ms 185.101.22.33
5 2026-08-12 05:51 639221097816416095
687 ms 188.209.136.91
4 2026-08-12 04:12 639221038601577496
695 ms 185.101.22.33
3 2026-08-12 04:12 639221038601577496
695 ms 188.209.136.91
2 2026-08-12 02:35 639220979815209769
683 ms 185.101.22.33
1 2026-08-12 02:35 639220979815209769
683 ms 188.209.136.91