DNS response history for ns2.mnfschedule.com

ns2.mnfschedule.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-25. For this date, NameServerHistory found 29 DNS check records, 28 successful responses, 1 failed responses, and 470 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.mnfschedule.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

470 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.23.253.250

Most recently resolved hosting IP on selected date

Successful Responses

28

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.mnfschedule.com

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
29 2026-08-25 10:04 639232482235303141
130 ms 67.23.253.250
28 2026-08-25 09:46 639232471861770303
249 ms 67.23.253.250
27 2026-08-25 09:29 639232461630217327
238 ms 67.23.253.250
26 2026-08-25 09:12 639232451282965990
246 ms 67.23.253.250
25 2026-08-25 08:54 639232440814614938
-
24 2026-08-25 08:37 639232430410720425
260 ms 67.23.253.250
23 2026-08-25 08:20 639232420003096185
6 ms 67.23.253.250
22 2026-08-25 08:02 639232409467287444
248 ms 67.23.253.250
21 2026-08-25 07:45 639232399077195997
5 ms 67.23.253.250
20 2026-08-25 07:27 639232388731528337
121 ms 67.23.253.250
19 2026-08-25 07:10 639232378288598612
1759 ms 67.23.253.250
18 2026-08-25 06:16 639232346196373643
5 ms 67.23.253.250
17 2026-08-25 05:59 639232336112370741
124 ms 67.23.253.250
16 2026-08-25 05:43 639232326146508970
119 ms 67.23.253.250
15 2026-08-25 05:26 639232316189381720
263 ms 67.23.253.250
14 2026-08-25 05:10 639232306217998913
2009 ms 67.23.253.250
13 2026-08-25 04:53 639232296255744174
3631 ms 67.23.253.250
12 2026-08-25 04:36 639232286095760789
125 ms 67.23.253.250
11 2026-08-25 04:19 639232276086186273
829 ms 67.23.253.250
10 2026-08-25 04:03 639232265900986425
261 ms 67.23.253.250
9 2026-08-25 03:46 639232255723518075
3 ms 67.23.253.250
8 2026-08-25 03:29 639232245484452890
1768 ms 67.23.253.250
7 2026-08-25 03:11 639232235157175331
256 ms 67.23.253.250
6 2026-08-25 02:18 639232203197189095
4 ms 67.23.253.250
5 2026-08-25 02:01 639232192844564298
252 ms 67.23.253.250
4 2026-08-25 01:44 639232182496008942
3 ms 67.23.253.250
3 2026-08-25 01:26 639232172197053132
126 ms 67.23.253.250
2 2026-08-25 00:33 639232140250307418
2 ms 67.23.253.250
1 2026-08-25 00:16 639232129927860324
121 ms 67.23.253.250