DNS response history for ns2.mrserver.net

ns2.mrserver.net 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-28. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 183 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.mrserver.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

183 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.111.99.106

Most recently resolved hosting IP on selected date

Successful Responses

36

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.mrserver.net

Showing DNS history for 2026-08-28 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
36 2026-08-28 15:11 639235258803654519
104 ms 64.111.99.106
35 2026-08-28 14:54 639235248596087996
209 ms 64.111.99.106
34 2026-08-28 14:37 639235238225955920
219 ms 64.111.99.106
33 2026-08-28 14:19 639235227727862105
105 ms 64.111.99.106
32 2026-08-28 13:25 639235195230848570
119 ms 64.111.99.106
31 2026-08-28 13:08 639235184840503274
102 ms 64.111.99.106
30 2026-08-28 12:51 639235174453894956
104 ms 64.111.99.106
29 2026-08-28 12:33 639235163898672622
103 ms 64.111.99.106
28 2026-08-28 11:40 639235132147470568
103 ms 64.111.99.106
27 2026-08-28 11:23 639235121907744088
212 ms 64.111.99.106
26 2026-08-28 11:06 639235111428014262
102 ms 64.111.99.106
25 2026-08-28 10:48 639235100921813626
102 ms 64.111.99.106
24 2026-08-28 09:54 639235068670703481
220 ms 64.111.99.106
23 2026-08-28 09:37 639235058337459445
216 ms 64.111.99.106
22 2026-08-28 09:20 639235047825109146
206 ms 64.111.99.106
21 2026-08-28 09:02 639235037383229033
205 ms 64.111.99.106
20 2026-08-28 08:09 639235005619242711
111 ms 64.111.99.106
19 2026-08-28 07:52 639234995310346584
103 ms 64.111.99.106
18 2026-08-28 07:35 639234984946548933
104 ms 64.111.99.106
17 2026-08-28 07:17 639234974608077290
205 ms 64.111.99.106
16 2026-08-28 06:24 639234942529845595
204 ms 64.111.99.106
15 2026-08-28 06:07 639234932259126627
203 ms 64.111.99.106
14 2026-08-28 05:50 639234921916735988
103 ms 64.111.99.106
13 2026-08-28 05:32 639234911470038027
102 ms 64.111.99.106
12 2026-08-28 04:39 639234879588411654
201 ms 64.111.99.106
11 2026-08-28 04:22 639234869341589104
102 ms 64.111.99.106
10 2026-08-28 04:05 639234859012216675
202 ms 64.111.99.106
9 2026-08-28 03:48 639234848695364934
204 ms 64.111.99.106
8 2026-08-28 02:55 639234816952458162
102 ms 64.111.99.106
7 2026-08-28 02:38 639234806773081598
210 ms 64.111.99.106
6 2026-08-28 02:21 639234796382955255
103 ms 64.111.99.106
5 2026-08-28 02:03 639234786015782563
115 ms 64.111.99.106
4 2026-08-28 01:10 639234753811917646
102 ms 64.111.99.106
3 2026-08-28 00:52 639234743739767811
1365 ms 64.111.99.106
2 2026-08-28 00:36 639234733372362811
112 ms 64.111.99.106
1 2026-08-28 00:18 639234723048550337
209 ms 64.111.99.106