DNS response history for ns1.mc2.software

ns1.mc2.software 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 37 DNS check records, 37 successful responses, 0 failed responses, and 390 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 ns1.mc2.software.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

390 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.143.183.99

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns1.mc2.software

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
37 2026-08-25 12:51 639232587225721862
134 ms 95.143.183.99
36 2026-08-25 12:34 639232576780683689
113 ms 95.143.183.99
35 2026-08-25 12:17 639232566381512620
115 ms 95.143.183.99
34 2026-08-25 12:00 639232556111768563
109 ms 95.143.183.99
33 2026-08-25 11:42 639232545839529039
117 ms 95.143.183.99
32 2026-08-25 11:25 639232535349285207
133 ms 95.143.183.99
31 2026-08-25 11:08 639232524938080723
139 ms 95.143.183.99
30 2026-08-25 10:14 639232492740373468
2131 ms 95.143.183.99
29 2026-08-25 09:57 639232482235303141
113 ms 95.143.183.99
28 2026-08-25 09:39 639232471861770303
101 ms 95.143.183.99
27 2026-08-25 09:22 639232461630217327
104 ms 95.143.183.99
26 2026-08-25 09:05 639232451282965990
150 ms 95.143.183.99
25 2026-08-25 08:47 639232440814614938
72 ms 95.143.183.99
24 2026-08-25 08:30 639232430410720425
284 ms 95.143.183.99
23 2026-08-25 08:13 639232420003096185
67 ms 95.143.183.99
22 2026-08-25 07:55 639232409467287444
67 ms 95.143.183.99
21 2026-08-25 07:38 639232399077195997
2169 ms 95.143.183.99
20 2026-08-25 07:21 639232388731528337
2068 ms 95.143.183.99
19 2026-08-25 07:03 639232378288598612
193 ms 95.143.183.99
18 2026-08-25 06:10 639232346196373643
485 ms 95.143.183.99
17 2026-08-25 05:53 639232336112370741
2249 ms 95.143.183.99
16 2026-08-25 05:36 639232326146508970
111 ms 95.143.183.99
15 2026-08-25 05:20 639232316189381720
115 ms 95.143.183.99
14 2026-08-25 05:03 639232306217998913
88 ms 95.143.183.99
13 2026-08-25 04:47 639232296255744174
63 ms 95.143.183.99
12 2026-08-25 04:30 639232286095760789
49 ms 95.143.183.99
11 2026-08-25 04:13 639232276086186273
103 ms 95.143.183.99
10 2026-08-25 03:56 639232265900986425
89 ms 95.143.183.99
9 2026-08-25 03:39 639232255723518075
65 ms 95.143.183.99
8 2026-08-25 03:22 639232245484452890
43 ms 95.143.183.99
7 2026-08-25 03:05 639232235157175331
118 ms 95.143.183.99
6 2026-08-25 02:11 639232203197189095
51 ms 95.143.183.99
5 2026-08-25 01:54 639232192844564298
63 ms 95.143.183.99
4 2026-08-25 01:37 639232182496008942
113 ms 95.143.183.99
3 2026-08-25 01:20 639232172197053132
102 ms 95.143.183.99
2 2026-08-25 00:26 639232140250307418
104 ms 95.143.183.99
1 2026-08-25 00:09 639232129927860324
2057 ms 95.143.183.99