DNS response history for ns2.dopule.com

ns2.dopule.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 39 DNS check records, 39 successful responses, 0 failed responses, and 201 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.dopule.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

201 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.159.3.160

Most recently resolved hosting IP on selected date

Successful Responses

39

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.dopule.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
39 2026-08-27 12:52 639234317475724313
57 ms 51.159.3.160
38 2026-08-27 12:34 639234307007468133
35 ms 51.159.3.160
37 2026-08-27 12:17 639234296664302575
44 ms 51.159.3.160
36 2026-08-27 12:00 639234286253196126
41 ms 51.159.3.160
35 2026-08-27 11:06 639234253963286387
25 ms 51.159.3.160
34 2026-08-27 10:49 639234243654907465
34 ms 51.159.3.160
33 2026-08-27 10:31 639234233269654413
49 ms 51.159.3.160
32 2026-08-27 10:14 639234222943951923
2045 ms 51.159.3.160
31 2026-08-27 09:57 639234212558002823
64 ms 51.159.3.160
30 2026-08-27 09:40 639234202117531850
49 ms 51.159.3.160
29 2026-08-27 09:22 639234191649612722
58 ms 51.159.3.160
28 2026-08-27 09:05 639234181105879568
99 ms 51.159.3.160
27 2026-08-27 08:47 639234170713214496
45 ms 51.159.3.160
26 2026-08-27 08:30 639234160341037652
80 ms 51.159.3.160
25 2026-08-27 08:13 639234149799404224
26 ms 51.159.3.160
24 2026-08-27 07:55 639234139553286469
12 ms 51.159.3.160
23 2026-08-27 07:01 639234107183588293
51 ms 51.159.3.160
22 2026-08-27 06:44 639234096905435724
40 ms 51.159.3.160
21 2026-08-27 06:27 639234086579410775
51 ms 51.159.3.160
20 2026-08-27 06:10 639234076291157956
44 ms 51.159.3.160
19 2026-08-27 05:53 639234065981939454
58 ms 51.159.3.160
18 2026-08-27 05:36 639234055548642997
42 ms 51.159.3.160
17 2026-08-27 05:18 639234045267979603
50 ms 51.159.3.160
16 2026-08-27 05:01 639234034999717463
35 ms 51.159.3.160
15 2026-08-27 04:44 639234024739225358
41 ms 51.159.3.160
14 2026-08-27 04:27 639234014311170162
2041 ms 51.159.3.160
13 2026-08-27 04:09 639234003806017640
38 ms 51.159.3.160
12 2026-08-27 03:52 639233993356203030
37 ms 51.159.3.160
11 2026-08-27 02:58 639233961301716608
43 ms 51.159.3.160
10 2026-08-27 02:41 639233950834200647
34 ms 51.159.3.160
9 2026-08-27 02:24 639233940431849026
34 ms 51.159.3.160
8 2026-08-27 02:06 639233930110596398
56 ms 51.159.3.160
7 2026-08-27 01:49 639233919705434540
2080 ms 51.159.3.160
6 2026-08-27 01:32 639233909452807845
22 ms 51.159.3.160
5 2026-08-27 01:15 639233899096420820
80 ms 51.159.3.160
4 2026-08-27 00:57 639233888707824939
47 ms 51.159.3.160
3 2026-08-27 00:40 639233878461203802
49 ms 51.159.3.160
2 2026-08-27 00:23 639233868060868209
60 ms 51.159.3.160
1 2026-08-27 00:05 639233857450922991
50 ms 51.159.3.160