DNS response history for ns2.dynopulse.com

ns2.dynopulse.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 33 DNS check records, 32 successful responses, 1 failed responses, and 337 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.dynopulse.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

337 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.33.20.119

Most recently resolved hosting IP on selected date

Successful Responses

32

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.dynopulse.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
33 2026-08-24 13:48 639231755868832964
2008 ms 45.33.20.119
32 2026-08-24 13:31 639231745628278877
157 ms 45.33.20.119
31 2026-08-24 13:14 639231735407682062
2146 ms 45.33.20.119
30 2026-08-24 12:21 639231703815441688
8 ms 45.33.20.119
29 2026-08-24 12:05 639231693747052549
151 ms 45.33.20.119
28 2026-08-24 11:48 639231683712487276
252 ms 45.33.20.119
27 2026-08-24 11:31 639231673513573868
320 ms 45.33.20.119
26 2026-08-24 10:38 639231641791249939
252 ms 45.33.20.119
25 2026-08-24 10:22 639231631866211033
2130 ms 45.33.20.119
24 2026-08-24 10:05 639231621644955316
129 ms 45.33.20.119
23 2026-08-24 09:48 639231611478799259
5 ms 45.33.20.119
22 2026-08-24 08:55 639231579923718211
12 ms 45.33.20.119
21 2026-08-24 08:38 639231569810702936
247 ms 45.33.20.119
20 2026-08-24 08:21 639231559762411619
5 ms 45.33.20.119
19 2026-08-24 08:04 639231549663595407
239 ms 45.33.20.119
18 2026-08-24 07:12 639231518076817246
245 ms 45.33.20.119
17 2026-08-24 06:55 639231508078650885
253 ms 45.33.20.119
16 2026-08-24 06:39 639231498210697093
143 ms 45.33.20.119
15 2026-08-24 06:22 639231488109699360
241 ms 45.33.20.119
14 2026-08-24 05:30 639231456772510692
6 ms 45.33.20.119
13 2026-08-24 05:14 639231447084631185
154 ms 45.33.20.119
12 2026-08-24 04:57 639231437208519473
242 ms 45.33.20.119
11 2026-08-24 04:40 639231427209627490
246 ms 45.33.20.119
10 2026-08-24 03:48 639231395791246644
296 ms 45.33.20.119
9 2026-08-24 03:32 639231386075551458
195 ms 45.33.20.119
8 2026-08-24 03:16 639231376208713791
261 ms 45.33.20.119
7 2026-08-24 02:59 639231366170589276
151 ms 45.33.20.119
6 2026-08-24 02:07 639231334732159368
253 ms 45.33.20.119
5 2026-08-24 01:50 639231325035670078
34 ms 45.33.20.119
4 2026-08-24 01:34 639231315132253837
-
3 2026-08-24 01:17 639231305014280808
3 ms 45.33.20.119
2 2026-08-24 00:25 639231273779380675
6 ms 45.33.20.119
1 2026-08-24 00:09 639231264180839154
2 ms 45.33.20.119