DNS response history for ns2.mipanel.mx

ns2.mipanel.mx 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 397 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.mipanel.mx.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

397 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.140.167.50

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.mipanel.mx

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:34 639231745628278877
299 ms 64.140.167.50
31 2026-08-24 13:17 639231735407682062
297 ms 64.140.167.50
30 2026-08-24 12:24 639231703815441688
188 ms 64.140.167.50
29 2026-08-24 12:07 639231693747052549
307 ms 64.140.167.50
28 2026-08-24 11:50 639231683712487276
299 ms 64.140.167.50
27 2026-08-24 11:33 639231673513573868
288 ms 64.140.167.50
26 2026-08-24 10:40 639231641791249939
297 ms 64.140.167.50
25 2026-08-24 10:24 639231631866211033
2203 ms 64.140.167.50
24 2026-08-24 10:07 639231621644955316
155 ms 64.140.167.50
23 2026-08-24 09:50 639231611478799259
290 ms 64.140.167.50
22 2026-08-24 08:58 639231579923718211
2290 ms 64.140.167.50
21 2026-08-24 08:41 639231569810702936
388 ms 64.140.167.50
20 2026-08-24 08:24 639231559762411619
312 ms 64.140.167.50
19 2026-08-24 08:07 639231549663595407
299 ms 64.140.167.50
18 2026-08-24 07:14 639231518076817246
301 ms 64.140.167.50
17 2026-08-24 06:58 639231508078650885
146 ms 64.140.167.50
16 2026-08-24 06:41 639231498210697093
427 ms 64.140.167.50
15 2026-08-24 06:25 639231488109699360
298 ms 64.140.167.50
14 2026-08-24 05:32 639231456772510692
288 ms 64.140.167.50
13 2026-08-24 05:16 639231447084631185
297 ms 64.140.167.50
12 2026-08-24 04:59 639231437208519473
298 ms 64.140.167.50
11 2026-08-24 04:43 639231427209627490
304 ms 64.140.167.50
10 2026-08-24 03:50 639231395791246644
148 ms 64.140.167.50
9 2026-08-24 03:34 639231386075551458
146 ms 64.140.167.50
8 2026-08-24 03:18 639231376208713791
155 ms 64.140.167.50
7 2026-08-24 03:01 639231366170589276
298 ms 64.140.167.50
6 2026-08-24 02:09 639231334732159368
315 ms 64.140.167.50
5 2026-08-24 01:52 639231325035670078
304 ms 64.140.167.50
4 2026-08-24 01:36 639231315132253837
307 ms 64.140.167.50
3 2026-08-24 01:19 639231305014280808
299 ms 64.140.167.50
2 2026-08-24 00:27 639231273779380675
148 ms 64.140.167.50
1 2026-08-24 00:11 639231264180839154
300 ms 64.140.167.50