DNS response history for ns2.miportal.mx

ns2.miportal.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 36 DNS check records, 36 successful responses, 0 failed responses, and 468 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.miportal.mx.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

468 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.208.82.169

Most recently resolved hosting IP on selected date

Successful Responses

36

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.miportal.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
36 2026-08-24 15:17 639231807961539652
156 ms 74.208.82.169
35 2026-08-24 15:01 639231797631669865
326 ms 74.208.82.169
34 2026-08-24 14:08 639231765923559455
351 ms 74.208.82.169
33 2026-08-24 13:51 639231755868832964
2311 ms 74.208.82.169
32 2026-08-24 13:34 639231745628278877
317 ms 74.208.82.169
31 2026-08-24 13:17 639231735407682062
3 ms 74.208.82.169
30 2026-08-24 12:24 639231703815441688
278 ms 74.208.82.169
29 2026-08-24 12:07 639231693747052549
486 ms 74.208.82.169
28 2026-08-24 11:50 639231683712487276
484 ms 74.208.82.169
27 2026-08-24 11:34 639231673513573868
4 ms 74.208.82.169
26 2026-08-24 10:40 639231641791249939
324 ms 74.208.82.169
25 2026-08-24 10:24 639231631866211033
180 ms 74.208.82.169
24 2026-08-24 10:07 639231621644955316
182 ms 74.208.82.169
23 2026-08-24 09:50 639231611478799259
514 ms 74.208.82.169
22 2026-08-24 08:58 639231579923718211
326 ms 74.208.82.169
21 2026-08-24 08:41 639231569810702936
2146 ms 74.208.82.169
20 2026-08-24 08:24 639231559762411619
9 ms 74.208.82.169
19 2026-08-24 08:07 639231549663595407
339 ms 74.208.82.169
18 2026-08-24 07:14 639231518076817246
2 ms 74.208.82.169
17 2026-08-24 06:58 639231508078650885
431 ms 74.208.82.169
16 2026-08-24 06:41 639231498210697093
338 ms 74.208.82.169
15 2026-08-24 06:25 639231488109699360
3 ms 74.208.82.169
14 2026-08-24 05:32 639231456772510692
487 ms 74.208.82.169
13 2026-08-24 05:16 639231447084631185
136 ms 74.208.82.169
12 2026-08-24 05:00 639231437208519473
3274 ms 74.208.82.169
11 2026-08-24 04:43 639231427209627490
4 ms 74.208.82.169
10 2026-08-24 03:50 639231395791246644
3 ms 74.208.82.169
9 2026-08-24 03:34 639231386075551458
480 ms 74.208.82.169
8 2026-08-24 03:18 639231376208713791
3 ms 74.208.82.169
7 2026-08-24 03:01 639231366170589276
491 ms 74.208.82.169
6 2026-08-24 02:09 639231334732159368
148 ms 74.208.82.169
5 2026-08-24 01:52 639231325035670078
4 ms 74.208.82.169
4 2026-08-24 01:36 639231315132253837
4 ms 74.208.82.169
3 2026-08-24 01:20 639231305014280808
2282 ms 74.208.82.169
2 2026-08-24 00:27 639231273779380675
3 ms 74.208.82.169
1 2026-08-24 00:11 639231264180839154
2 ms 74.208.82.169