DNS response history for ns1.mibooking.cl

ns1.mibooking.cl 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 30 DNS check records, 30 successful responses, 0 failed responses, and 529 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.mibooking.cl.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

529 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

200.63.96.127

Most recently resolved hosting IP on selected date

Successful Responses

30

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.mibooking.cl

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
30 2026-08-25 10:21 639232492740373468
839 ms 200.63.96.127
29 2026-08-25 10:04 639232482235303141
495 ms 200.63.96.127
28 2026-08-25 09:46 639232471861770303
565 ms 200.63.96.127
27 2026-08-25 09:29 639232461630217327
474 ms 200.63.96.127
26 2026-08-25 09:12 639232451282965990
474 ms 200.63.96.127
25 2026-08-25 08:55 639232440814614938
475 ms 200.63.96.127
24 2026-08-25 08:37 639232430410720425
479 ms 200.63.96.127
23 2026-08-25 08:20 639232420003096185
473 ms 200.63.96.127
22 2026-08-25 08:03 639232409467287444
475 ms 200.63.96.127
21 2026-08-25 07:45 639232399077195997
473 ms 200.63.96.127
20 2026-08-25 07:28 639232388731528337
485 ms 200.63.96.127
19 2026-08-25 07:10 639232378288598612
474 ms 200.63.96.127
18 2026-08-25 06:17 639232346196373643
473 ms 200.63.96.127
17 2026-08-25 06:00 639232336112370741
476 ms 200.63.96.127
16 2026-08-25 05:43 639232326146508970
473 ms 200.63.96.127
15 2026-08-25 05:27 639232316189381720
224 ms 200.63.96.127
14 2026-08-25 05:10 639232306217998913
475 ms 200.63.96.127
13 2026-08-25 04:53 639232296255744174
491 ms 200.63.96.127
12 2026-08-25 04:37 639232286095760789
478 ms 200.63.96.127
11 2026-08-25 04:20 639232276086186273
481 ms 200.63.96.127
10 2026-08-25 04:03 639232265900986425
471 ms 200.63.96.127
9 2026-08-25 03:46 639232255723518075
364 ms 200.63.96.127
8 2026-08-25 03:29 639232245484452890
486 ms 200.63.96.127
7 2026-08-25 03:12 639232235157175331
475 ms 200.63.96.127
6 2026-08-25 02:18 639232203197189095
2008 ms 200.63.96.127
5 2026-08-25 02:01 639232192844564298
471 ms 200.63.96.127
4 2026-08-25 01:44 639232182496008942
470 ms 200.63.96.127
3 2026-08-25 01:27 639232172197053132
401 ms 200.63.96.127
2 2026-08-25 00:33 639232140250307418
515 ms 200.63.96.127
1 2026-08-25 00:17 639232129927860324
470 ms 200.63.96.127