DNS response history for ns2.mingaticspy.com

ns2.mingaticspy.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-27. For this date, NameServerHistory found 30 DNS check records, 28 successful responses, 2 failed responses, and 556 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.mingaticspy.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

556 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.85.47.172

Most recently resolved hosting IP on selected date

Successful Responses

28

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

7%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.mingaticspy.com

Showing DNS history for 2026-08-27 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
30 2026-08-27 09:43 639234202117531850
51 ms 66.85.47.172
29 2026-08-27 09:25 639234191649612722
24 ms 66.85.47.172
28 2026-08-27 09:08 639234181105879568
67 ms 66.85.47.172
27 2026-08-27 08:51 639234170713214496
4029 ms 66.85.47.172
26 2026-08-27 08:33 639234160341037652
55 ms 66.85.47.172
25 2026-08-27 08:16 639234149799404224
51 ms 66.85.47.172
24 2026-08-27 07:59 639234139553286469
2166 ms 66.85.47.172
23 2026-08-27 07:05 639234107183588293
29 ms 66.85.47.172
22 2026-08-27 06:48 639234096905435724
4049 ms 66.85.47.172
21 2026-08-27 06:30 639234086579410775
26 ms 66.85.47.172
20 2026-08-27 06:13 639234076291157956
157 ms 66.85.47.172
19 2026-08-27 05:56 639234065981939454
59 ms 66.85.47.172
18 2026-08-27 05:39 639234055548642997
198 ms 66.85.47.172
17 2026-08-27 05:21 639234045267979603
47 ms 66.85.47.172
16 2026-08-27 05:04 639234034999717463
46 ms 66.85.47.172
15 2026-08-27 04:47 639234024739225358
73 ms 66.85.47.172
14 2026-08-27 04:30 639234014311170162
-
13 2026-08-27 04:12 639234003806017640
2015 ms 66.85.47.172
12 2026-08-27 03:55 639233993356203030
46 ms 66.85.47.172
11 2026-08-27 03:02 639233961301716608
51 ms 66.85.47.172
10 2026-08-27 02:44 639233950834200647
2057 ms 66.85.47.172
9 2026-08-27 02:27 639233940431849026
46 ms 66.85.47.172
8 2026-08-27 02:10 639233930110596398
44 ms 66.85.47.172
7 2026-08-27 01:52 639233919705434540
45 ms 66.85.47.172
6 2026-08-27 01:35 639233909452807845
48 ms 66.85.47.172
5 2026-08-27 01:18 639233899096420820
25 ms 66.85.47.172
4 2026-08-27 01:01 639233888707824939
24 ms 66.85.47.172
3 2026-08-27 00:43 639233878461203802
30 ms 66.85.47.172
2 2026-08-27 00:26 639233868060868209
-
1 2026-08-27 00:09 639233857450922991
7 ms 66.85.47.172