DNS response history for ns2.dapperfrog.com

ns2.dapperfrog.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 356 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.dapperfrog.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

356 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.79.57.225

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.dapperfrog.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:34 639234233269654413
111 ms 51.79.57.225
32 2026-08-27 10:17 639234222943951923
2103 ms 51.79.57.225
31 2026-08-27 10:00 639234212558002823
229 ms 51.79.57.225
30 2026-08-27 09:42 639234202117531850
215 ms 51.79.57.225
29 2026-08-27 09:25 639234191649612722
233 ms 51.79.57.225
28 2026-08-27 09:07 639234181105879568
227 ms 51.79.57.225
27 2026-08-27 08:50 639234170713214496
219 ms 51.79.57.225
26 2026-08-27 08:32 639234160341037652
226 ms 51.79.57.225
25 2026-08-27 08:15 639234149799404224
232 ms 51.79.57.225
24 2026-08-27 07:58 639234139553286469
134 ms 51.79.57.225
23 2026-08-27 07:04 639234107183588293
227 ms 51.79.57.225
22 2026-08-27 06:47 639234096905435724
202 ms 51.79.57.225
21 2026-08-27 06:30 639234086579410775
133 ms 51.79.57.225
20 2026-08-27 06:12 639234076291157956
231 ms 51.79.57.225
19 2026-08-27 05:55 639234065981939454
224 ms 51.79.57.225
18 2026-08-27 05:38 639234055548642997
138 ms 51.79.57.225
17 2026-08-27 05:21 639234045267979603
224 ms 51.79.57.225
16 2026-08-27 05:04 639234034999717463
215 ms 51.79.57.225
15 2026-08-27 04:47 639234024739225358
215 ms 51.79.57.225
14 2026-08-27 04:29 639234014311170162
238 ms 51.79.57.225
13 2026-08-27 04:12 639234003806017640
117 ms 51.79.57.225
12 2026-08-27 03:54 639233993356203030
219 ms 51.79.57.225
11 2026-08-27 03:01 639233961301716608
23 ms 51.79.57.225
10 2026-08-27 02:44 639233950834200647
9 ms 51.79.57.225
9 2026-08-27 02:26 639233940431849026
2113 ms 51.79.57.225
8 2026-08-27 02:09 639233930110596398
216 ms 51.79.57.225
7 2026-08-27 01:52 639233919705434540
223 ms 51.79.57.225
6 2026-08-27 01:34 639233909452807845
156 ms 51.79.57.225
5 2026-08-27 01:17 639233899096420820
152 ms 51.79.57.225
4 2026-08-27 01:00 639233888707824939
2115 ms 51.79.57.225
3 2026-08-27 00:43 639233878461203802
105 ms 51.79.57.225
2 2026-08-27 00:25 639233868060868209
234 ms 51.79.57.225
1 2026-08-27 00:08 639233857450922991
106 ms 51.79.57.225