DNS response history for ns1.myrmid.com

ns1.myrmid.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 31 DNS check records, 31 successful responses, 0 failed responses, and 327 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.myrmid.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

327 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.78.224.114

Most recently resolved hosting IP on selected date

Successful Responses

31

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.myrmid.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
31 2026-08-24 13:14 639231735407682062
321 ms 208.78.224.114
30 2026-08-24 12:22 639231703815441688
167 ms 208.78.224.114
29 2026-08-24 12:05 639231693747052549
351 ms 208.78.224.114
28 2026-08-24 11:48 639231683712487276
319 ms 208.78.224.114
27 2026-08-24 11:31 639231673513573868
319 ms 208.78.224.114
26 2026-08-24 10:38 639231641791249939
6 ms 208.78.224.114
25 2026-08-24 10:22 639231631866211033
297 ms 208.78.224.114
24 2026-08-24 10:05 639231621644955316
2170 ms 208.78.224.114
23 2026-08-24 09:48 639231611478799259
362 ms 208.78.224.114
22 2026-08-24 08:55 639231579923718211
4 ms 208.78.224.114
21 2026-08-24 08:39 639231569810702936
334 ms 208.78.224.114
20 2026-08-24 08:21 639231559762411619
340 ms 208.78.224.114
19 2026-08-24 08:05 639231549663595407
320 ms 208.78.224.114
18 2026-08-24 07:12 639231518076817246
298 ms 208.78.224.114
17 2026-08-24 06:56 639231508078650885
10 ms 208.78.224.114
16 2026-08-24 06:39 639231498210697093
8 ms 208.78.224.114
15 2026-08-24 06:23 639231488109699360
177 ms 208.78.224.114
14 2026-08-24 05:30 639231456772510692
165 ms 208.78.224.114
13 2026-08-24 05:14 639231447084631185
16 ms 208.78.224.114
12 2026-08-24 04:57 639231437208519473
325 ms 208.78.224.114
11 2026-08-24 04:41 639231427209627490
170 ms 208.78.224.114
10 2026-08-24 03:48 639231395791246644
2186 ms 208.78.224.114
9 2026-08-24 03:32 639231386075551458
151 ms 208.78.224.114
8 2026-08-24 03:16 639231376208713791
315 ms 208.78.224.114
7 2026-08-24 02:59 639231366170589276
8 ms 208.78.224.114
6 2026-08-24 02:07 639231334732159368
305 ms 208.78.224.114
5 2026-08-24 01:50 639231325035670078
4 ms 208.78.224.114
4 2026-08-24 01:34 639231315132253837
337 ms 208.78.224.114
3 2026-08-24 01:17 639231305014280808
344 ms 208.78.224.114
2 2026-08-24 00:25 639231273779380675
3 ms 208.78.224.114
1 2026-08-24 00:09 639231264180839154
3 ms 208.78.224.114