DNS response history for ns1.mircomreports.com

ns1.mircomreports.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-25. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 257 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.mircomreports.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

257 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.145.60.6

Most recently resolved hosting IP on selected date

Successful Responses

32

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

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
32 2026-08-25 11:29 639232535349285207
241 ms 209.145.60.6
31 2026-08-25 11:12 639232524938080723
257 ms 209.145.60.6
30 2026-08-25 10:18 639232492740373468
241 ms 209.145.60.6
29 2026-08-25 10:01 639232482235303141
251 ms 209.145.60.6
28 2026-08-25 09:44 639232471861770303
175 ms 209.145.60.6
27 2026-08-25 09:26 639232461630217327
253 ms 209.145.60.6
26 2026-08-25 09:09 639232451282965990
257 ms 209.145.60.6
25 2026-08-25 08:52 639232440814614938
259 ms 209.145.60.6
24 2026-08-25 08:34 639232430410720425
241 ms 209.145.60.6
23 2026-08-25 08:17 639232420003096185
242 ms 209.145.60.6
22 2026-08-25 08:00 639232409467287444
256 ms 209.145.60.6
21 2026-08-25 07:42 639232399077195997
245 ms 209.145.60.6
20 2026-08-25 07:25 639232388731528337
190 ms 209.145.60.6
19 2026-08-25 07:08 639232378288598612
238 ms 209.145.60.6
18 2026-08-25 06:14 639232346196373643
3 ms 209.145.60.6
17 2026-08-25 05:57 639232336112370741
257 ms 209.145.60.6
16 2026-08-25 05:40 639232326146508970
142 ms 209.145.60.6
15 2026-08-25 05:24 639232316189381720
247 ms 209.145.60.6
14 2026-08-25 05:07 639232306217998913
249 ms 209.145.60.6
13 2026-08-25 04:51 639232296255744174
236 ms 209.145.60.6
12 2026-08-25 04:34 639232286095760789
239 ms 209.145.60.6
11 2026-08-25 04:17 639232276086186273
12 ms 209.145.60.6
10 2026-08-25 04:00 639232265900986425
123 ms 209.145.60.6
9 2026-08-25 03:43 639232255723518075
4 ms 209.145.60.6
8 2026-08-25 03:26 639232245484452890
245 ms 209.145.60.6
7 2026-08-25 03:09 639232235157175331
239 ms 209.145.60.6
6 2026-08-25 02:16 639232203197189095
2127 ms 209.145.60.6
5 2026-08-25 01:59 639232192844564298
123 ms 209.145.60.6
4 2026-08-25 01:41 639232182496008942
123 ms 209.145.60.6
3 2026-08-25 01:24 639232172197053132
3 ms 209.145.60.6
2 2026-08-25 00:31 639232140250307418
241 ms 209.145.60.6
1 2026-08-25 00:14 639232129927860324
254 ms 209.145.60.6