DNS response history for ns1.dmrgps.com

ns1.dmrgps.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 38 DNS check records, 36 successful responses, 2 failed responses, and 208 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.dmrgps.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

208 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.111.233.122

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.dmrgps.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
38 2026-08-24 15:43 639231828211839931
68 ms 95.111.233.122
37 2026-08-24 15:26 639231818080917481
49 ms 95.111.233.122
36 2026-08-24 15:09 639231807961539652
26 ms 95.111.233.122
35 2026-08-24 14:52 639231797631669865
44 ms 95.111.233.122
34 2026-08-24 13:59 639231765923559455
36 ms 95.111.233.122
33 2026-08-24 13:42 639231755868832964
48 ms 95.111.233.122
32 2026-08-24 13:25 639231745628278877
22 ms 95.111.233.122
31 2026-08-24 13:08 639231735407682062
44 ms 95.111.233.122
30 2026-08-24 12:15 639231703815441688
33 ms 95.111.233.122
29 2026-08-24 11:59 639231693747052549
44 ms 95.111.233.122
28 2026-08-24 11:42 639231683712487276
2053 ms 95.111.233.122
27 2026-08-24 11:25 639231673513573868
40 ms 95.111.233.122
26 2026-08-24 10:32 639231641791249939
37 ms 95.111.233.122
25 2026-08-24 10:15 639231631866211033
21 ms 95.111.233.122
24 2026-08-24 09:59 639231621644955316
44 ms 95.111.233.122
23 2026-08-24 09:42 639231611478799259
50 ms 95.111.233.122
22 2026-08-24 08:49 639231579923718211
35 ms 95.111.233.122
21 2026-08-24 08:32 639231569810702936
2134 ms 95.111.233.122
20 2026-08-24 08:15 639231559762411619
35 ms 95.111.233.122
19 2026-08-24 07:58 639231549663595407
59 ms 95.111.233.122
18 2026-08-24 07:06 639231518076817246
-
17 2026-08-24 06:49 639231508078650885
34 ms 95.111.233.122
16 2026-08-24 06:33 639231498210697093
23 ms 95.111.233.122
15 2026-08-24 06:16 639231488109699360
27 ms 95.111.233.122
14 2026-08-24 05:24 639231456772510692
39 ms 95.111.233.122
13 2026-08-24 05:08 639231447084631185
33 ms 95.111.233.122
12 2026-08-24 04:51 639231437208519473
2018 ms 95.111.233.122
11 2026-08-24 04:34 639231427209627490
22 ms 95.111.233.122
10 2026-08-24 03:42 639231395791246644
33 ms 95.111.233.122
9 2026-08-24 03:26 639231386075551458
-
8 2026-08-24 03:10 639231376208713791
18 ms 95.111.233.122
7 2026-08-24 02:53 639231366170589276
59 ms 95.111.233.122
6 2026-08-24 02:00 639231334732159368
76 ms 95.111.233.122
5 2026-08-24 01:44 639231325035670078
66 ms 95.111.233.122
4 2026-08-24 01:28 639231315132253837
27 ms 95.111.233.122
3 2026-08-24 01:11 639231305014280808
36 ms 95.111.233.122
2 2026-08-24 00:19 639231273779380675
17 ms 95.111.233.122
1 2026-08-24 00:03 639231264180839154
47 ms 95.111.233.122