DNS response history for ns2.miramid.xyz

ns2.miramid.xyz 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 30 DNS check records, 30 successful responses, 0 failed responses, and 333 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.miramid.xyz.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

333 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.141.50.35

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 ns2.miramid.xyz

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
30 2026-08-24 12:25 639231703815441688
228 ms 209.141.50.35
29 2026-08-24 12:09 639231693747052549
233 ms 209.141.50.35
28 2026-08-24 11:52 639231683712487276
233 ms 209.141.50.35
27 2026-08-24 11:35 639231673513573868
235 ms 209.141.50.35
26 2026-08-24 10:42 639231641791249939
227 ms 209.141.50.35
25 2026-08-24 10:26 639231631866211033
1187 ms 209.141.50.35
24 2026-08-24 10:09 639231621644955316
227 ms 209.141.50.35
23 2026-08-24 09:52 639231611478799259
233 ms 209.141.50.35
22 2026-08-24 08:59 639231579923718211
227 ms 209.141.50.35
21 2026-08-24 08:42 639231569810702936
231 ms 209.141.50.35
20 2026-08-24 08:25 639231559762411619
230 ms 209.141.50.35
19 2026-08-24 08:09 639231549663595407
234 ms 209.141.50.35
18 2026-08-24 07:16 639231518076817246
223 ms 209.141.50.35
17 2026-08-24 07:00 639231508078650885
229 ms 209.141.50.35
16 2026-08-24 06:43 639231498210697093
226 ms 209.141.50.35
15 2026-08-24 06:26 639231488109699360
232 ms 209.141.50.35
14 2026-08-24 05:34 639231456772510692
117 ms 209.141.50.35
13 2026-08-24 05:18 639231447084631185
232 ms 209.141.50.35
12 2026-08-24 05:01 639231437208519473
1194 ms 209.141.50.35
11 2026-08-24 04:45 639231427209627490
232 ms 209.141.50.35
10 2026-08-24 03:52 639231395791246644
174 ms 209.141.50.35
9 2026-08-24 03:36 639231386075551458
225 ms 209.141.50.35
8 2026-08-24 03:20 639231376208713791
229 ms 209.141.50.35
7 2026-08-24 03:03 639231366170589276
232 ms 209.141.50.35
6 2026-08-24 02:11 639231334732159368
245 ms 209.141.50.35
5 2026-08-24 01:54 639231325035670078
121 ms 209.141.50.35
4 2026-08-24 01:38 639231315132253837
239 ms 209.141.50.35
3 2026-08-24 01:21 639231305014280808
393 ms 209.141.50.35
2 2026-08-24 00:29 639231273779380675
1589 ms 209.141.50.35
1 2026-08-24 00:13 639231264180839154
121 ms 209.141.50.35