DNS response history for ns2.minggardenhotel.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

483 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

1.9.201.59

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

Showing DNS history for 2026-08-24 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-24 13:35 639231745628278877
404 ms 1.9.201.59
31 2026-08-24 13:17 639231735407682062
381 ms 1.9.201.59
30 2026-08-24 12:25 639231703815441688
386 ms 1.9.201.59
29 2026-08-24 12:08 639231693747052549
2197 ms 1.9.201.59
28 2026-08-24 11:51 639231683712487276
4 ms 1.9.201.59
27 2026-08-24 11:34 639231673513573868
390 ms 1.9.201.59
26 2026-08-24 10:41 639231641791249939
7 ms 1.9.201.59
25 2026-08-24 10:25 639231631866211033
412 ms 1.9.201.59
24 2026-08-24 10:08 639231621644955316
385 ms 1.9.201.59
23 2026-08-24 09:51 639231611478799259
206 ms 1.9.201.59
22 2026-08-24 08:58 639231579923718211
254 ms 1.9.201.59
21 2026-08-24 08:42 639231569810702936
5 ms 1.9.201.59
20 2026-08-24 08:25 639231559762411619
397 ms 1.9.201.59
19 2026-08-24 08:08 639231549663595407
3 ms 1.9.201.59
18 2026-08-24 07:15 639231518076817246
391 ms 1.9.201.59
17 2026-08-24 06:59 639231508078650885
380 ms 1.9.201.59
16 2026-08-24 06:42 639231498210697093
5 ms 1.9.201.59
15 2026-08-24 06:25 639231488109699360
392 ms 1.9.201.59
14 2026-08-24 05:33 639231456772510692
3 ms 1.9.201.59
13 2026-08-24 05:17 639231447084631185
357 ms 1.9.201.59
12 2026-08-24 05:00 639231437208519473
389 ms 1.9.201.59
11 2026-08-24 04:44 639231427209627490
398 ms 1.9.201.59
10 2026-08-24 03:51 639231395791246644
2006 ms 1.9.201.59
9 2026-08-24 03:35 639231386075551458
419 ms 1.9.201.59
8 2026-08-24 03:19 639231376208713791
3 ms 1.9.201.59
7 2026-08-24 03:02 639231366170589276
393 ms 1.9.201.59
6 2026-08-24 02:10 639231334732159368
2007 ms 1.9.201.59
5 2026-08-24 01:53 639231325035670078
252 ms 1.9.201.59
4 2026-08-24 01:37 639231315132253837
384 ms 1.9.201.59
3 2026-08-24 01:20 639231305014280808
9 ms 1.9.201.59
2 2026-08-24 00:28 639231273779380675
2 ms 1.9.201.59
1 2026-08-24 00:12 639231264180839154
2220 ms 1.9.201.59