DNS response history for ns1.richardmeg.com

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

27

Historical checks stored for this nameserver on selected date

Average Latency

461 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.135.250.62

Most recently resolved hosting IP on selected date

Successful Responses

27

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.richardmeg.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
27 2026-08-25 09:12 639232451282965990
576 ms 220.135.250.62
26 2026-08-25 08:55 639232440814614938
292 ms 220.135.250.62
25 2026-08-25 08:38 639232430410720425
602 ms 220.135.250.62
24 2026-08-25 08:20 639232420003096185
596 ms 220.135.250.62
23 2026-08-25 08:03 639232409467287444
598 ms 220.135.250.62
22 2026-08-25 07:46 639232399077195997
299 ms 220.135.250.62
21 2026-08-25 07:28 639232388731528337
601 ms 220.135.250.62
20 2026-08-25 07:11 639232378288598612
586 ms 220.135.250.62
19 2026-08-25 06:17 639232346196373643
589 ms 220.135.250.62
18 2026-08-25 06:00 639232336112370741
590 ms 220.135.250.62
17 2026-08-25 05:44 639232326146508970
591 ms 220.135.250.62
16 2026-08-25 05:27 639232316189381720
582 ms 220.135.250.62
15 2026-08-25 05:10 639232306217998913
582 ms 220.135.250.62
14 2026-08-25 04:54 639232296255744174
594 ms 220.135.250.62
13 2026-08-25 04:37 639232286095760789
309 ms 220.135.250.62
12 2026-08-25 04:20 639232276086186273
607 ms 220.135.250.62
11 2026-08-25 04:03 639232265900986425
4 ms 220.135.250.62
10 2026-08-25 03:46 639232255723518075
587 ms 220.135.250.62
9 2026-08-25 03:29 639232245484452890
603 ms 220.135.250.62
8 2026-08-25 03:12 639232235157175331
604 ms 220.135.250.62
7 2026-08-25 02:19 639232203197189095
572 ms 220.135.250.62
6 2026-08-25 02:02 639232192844564298
9 ms 220.135.250.62
5 2026-08-25 01:45 639232182496008942
293 ms 220.135.250.62
4 2026-08-25 01:27 639232172197053132
584 ms 220.135.250.62
3 2026-08-25 00:34 639232140250307418
3 ms 220.135.250.62
2 2026-08-25 00:17 639232129927860324
586 ms 220.135.250.62
1 2026-08-25 00:00 639232119551972438
3 ms 220.135.250.62