DNS response history for s2.mi-co.net

s2.mi-co.net 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-26. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 336 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 s2.mi-co.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

336 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.164.197.151

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 s2.mi-co.net

Showing DNS history for 2026-08-26 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-26 09:47 639233339545274518
6 ms 69.164.197.151
29 2026-08-26 09:29 639233329214918079
151 ms 69.164.197.151
28 2026-08-26 09:12 639233318749762337
23 ms 69.164.197.151
27 2026-08-26 08:55 639233308387917838
2027 ms 69.164.197.151
26 2026-08-26 08:38 639233297961740122
290 ms 69.164.197.151
25 2026-08-26 08:20 639233287487159094
146 ms 69.164.197.151
24 2026-08-26 08:03 639233276995531707
140 ms 69.164.197.151
23 2026-08-26 07:45 639233266521568229
129 ms 69.164.197.151
22 2026-08-26 07:28 639233256081047431
250 ms 69.164.197.151
21 2026-08-26 06:34 639233223620132921
123 ms 69.164.197.151
20 2026-08-26 06:16 639233213287814244
4 ms 69.164.197.151
19 2026-08-26 05:59 639233202925983161
22 ms 69.164.197.151
18 2026-08-26 05:42 639233192644780696
9 ms 69.164.197.151
17 2026-08-26 05:25 639233182401183833
120 ms 69.164.197.151
16 2026-08-26 05:08 639233172074181051
140 ms 69.164.197.151
15 2026-08-26 04:51 639233161808421455
2187 ms 69.164.197.151
14 2026-08-26 04:33 639233151357344052
151 ms 69.164.197.151
13 2026-08-26 04:16 639233141034116946
52 ms 69.164.197.151
12 2026-08-26 03:59 639233130828334142
2135 ms 69.164.197.151
11 2026-08-26 03:42 639233120373450007
250 ms 69.164.197.151
10 2026-08-26 03:24 639233110066216193
155 ms 69.164.197.151
9 2026-08-26 02:31 639233078065410564
151 ms 69.164.197.151
8 2026-08-26 02:14 639233067787457832
635 ms 69.164.197.151
7 2026-08-26 01:57 639233057501801162
32 ms 69.164.197.151
6 2026-08-26 01:39 639233047089431703
118 ms 69.164.197.151
5 2026-08-26 01:22 639233036754790688
124 ms 69.164.197.151
4 2026-08-26 01:05 639233026412602472
106 ms 69.164.197.151
3 2026-08-26 00:48 639233016064066127
130 ms 69.164.197.151
2 2026-08-26 00:31 639233005922655772
121 ms 69.164.197.151
1 2026-08-26 00:14 639232995672256907
165 ms 69.164.197.151