DNS response history for ns2.rm-manager.com

ns2.rm-manager.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-27. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 213 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 ns2.rm-manager.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

213 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.158.168.200

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns2.rm-manager.com

Showing DNS history for 2026-08-27 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
33 2026-08-27 10:39 639234233269654413
95 ms 78.158.168.200
32 2026-08-27 10:22 639234222943951923
90 ms 78.158.168.200
31 2026-08-27 10:05 639234212558002823
187 ms 78.158.168.200
30 2026-08-27 09:48 639234202117531850
187 ms 78.158.168.200
29 2026-08-27 09:30 639234191649612722
188 ms 78.158.168.200
28 2026-08-27 09:13 639234181105879568
90 ms 78.158.168.200
27 2026-08-27 08:55 639234170713214496
183 ms 78.158.168.200
26 2026-08-27 08:38 639234160341037652
334 ms 78.158.168.200
25 2026-08-27 08:20 639234149799404224
188 ms 78.158.168.200
24 2026-08-27 08:03 639234139553286469
135 ms 78.158.168.200
23 2026-08-27 07:09 639234107183588293
175 ms 78.158.168.200
22 2026-08-27 06:52 639234096905435724
177 ms 78.158.168.200
21 2026-08-27 06:35 639234086579410775
90 ms 78.158.168.200
20 2026-08-27 06:18 639234076291157956
104 ms 78.158.168.200
19 2026-08-27 06:01 639234065981939454
172 ms 78.158.168.200
18 2026-08-27 05:44 639234055548642997
97 ms 78.158.168.200
17 2026-08-27 05:26 639234045267979603
84 ms 78.158.168.200
16 2026-08-27 05:09 639234034999717463
174 ms 78.158.168.200
15 2026-08-27 04:52 639234024739225358
194 ms 78.158.168.200
14 2026-08-27 04:35 639234014311170162
194 ms 78.158.168.200
13 2026-08-27 04:17 639234003806017640
177 ms 78.158.168.200
12 2026-08-27 04:00 639233993356203030
181 ms 78.158.168.200
11 2026-08-27 03:06 639233961301716608
2085 ms 78.158.168.200
10 2026-08-27 02:49 639233950834200647
179 ms 78.158.168.200
9 2026-08-27 02:32 639233940431849026
181 ms 78.158.168.200
8 2026-08-27 02:14 639233930110596398
85 ms 78.158.168.200
7 2026-08-27 01:57 639233919705434540
87 ms 78.158.168.200
6 2026-08-27 01:40 639233909452807845
165 ms 78.158.168.200
5 2026-08-27 01:23 639233899096420820
177 ms 78.158.168.200
4 2026-08-27 01:05 639233888707824939
105 ms 78.158.168.200
3 2026-08-27 00:48 639233878461203802
97 ms 78.158.168.200
2 2026-08-27 00:31 639233868060868209
183 ms 78.158.168.200
1 2026-08-27 00:13 639233857450922991
194 ms 78.158.168.200