DNS response history for ns2.miweblink.com

ns2.miweblink.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-24. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 617 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.miweblink.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

617 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.150.237.170

Most recently resolved hosting IP on selected date

Successful Responses

26

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.miweblink.com

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
26 2026-08-24 10:38 639231641791249939
127 ms 216.150.237.170
25 2026-08-24 10:22 639231631866211033
281 ms 216.150.237.170
24 2026-08-24 10:05 639231621644955316
172 ms 216.150.237.170
23 2026-08-24 09:48 639231611478799259
234 ms 216.150.237.170
22 2026-08-24 08:55 639231579923718211
237 ms 216.150.237.170
21 2026-08-24 08:39 639231569810702936
4117 ms 216.150.237.170
20 2026-08-24 08:21 639231559762411619
15 ms 216.150.237.170
19 2026-08-24 08:05 639231549663595407
230 ms 216.150.237.170
18 2026-08-24 07:12 639231518076817246
233 ms 216.150.237.170
17 2026-08-24 06:56 639231508078650885
165 ms 216.150.237.170
16 2026-08-24 06:39 639231498210697093
227 ms 216.150.237.170
15 2026-08-24 06:22 639231488109699360
2231 ms 216.150.237.170
14 2026-08-24 05:30 639231456772510692
235 ms 216.150.237.170
13 2026-08-24 05:14 639231447084631185
240 ms 216.150.237.170
12 2026-08-24 04:57 639231437208519473
133 ms 216.150.237.170
11 2026-08-24 04:41 639231427209627490
2008 ms 216.150.237.170
10 2026-08-24 03:48 639231395791246644
2013 ms 216.150.237.170
9 2026-08-24 03:32 639231386075551458
8 ms 216.150.237.170
8 2026-08-24 03:16 639231376208713791
228 ms 216.150.237.170
7 2026-08-24 02:59 639231366170589276
243 ms 216.150.237.170
6 2026-08-24 02:07 639231334732159368
144 ms 216.150.237.170
5 2026-08-24 01:50 639231325035670078
152 ms 216.150.237.170
4 2026-08-24 01:34 639231315132253837
2126 ms 216.150.237.170
3 2026-08-24 01:17 639231305014280808
233 ms 216.150.237.170
2 2026-08-24 00:25 639231273779380675
4 ms 216.150.237.170
1 2026-08-24 00:09 639231264180839154
6 ms 216.150.237.170