DNS response history for ns2.divparty1.com

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

26

Historical checks stored for this nameserver on selected date

Average Latency

420 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.230.156.205

Most recently resolved hosting IP on selected date

Successful Responses

26

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.divparty1.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
26 2026-08-24 10:36 639231641791249939
43 ms 173.230.156.205
25 2026-08-24 10:20 639231631866211033
2296 ms 173.230.156.205
24 2026-08-24 10:03 639231621644955316
47 ms 173.230.156.205
23 2026-08-24 09:46 639231611478799259
22 ms 173.230.156.205
22 2026-08-24 08:53 639231579923718211
273 ms 173.230.156.205
21 2026-08-24 08:37 639231569810702936
204 ms 173.230.156.205
20 2026-08-24 08:20 639231559762411619
26 ms 173.230.156.205
19 2026-08-24 08:03 639231549663595407
20 ms 173.230.156.205
18 2026-08-24 07:10 639231518076817246
21 ms 173.230.156.205
17 2026-08-24 06:54 639231508078650885
342 ms 173.230.156.205
16 2026-08-24 06:37 639231498210697093
32 ms 173.230.156.205
15 2026-08-24 06:21 639231488109699360
73 ms 173.230.156.205
14 2026-08-24 05:28 639231456772510692
20 ms 173.230.156.205
13 2026-08-24 05:12 639231447084631185
2028 ms 173.230.156.205
12 2026-08-24 04:56 639231437208519473
42 ms 173.230.156.205
11 2026-08-24 04:39 639231427209627490
37 ms 173.230.156.205
10 2026-08-24 03:46 639231395791246644
268 ms 173.230.156.205
9 2026-08-24 03:30 639231386075551458
24 ms 173.230.156.205
8 2026-08-24 03:14 639231376208713791
42 ms 173.230.156.205
7 2026-08-24 02:57 639231366170589276
2012 ms 173.230.156.205
6 2026-08-24 02:05 639231334732159368
355 ms 173.230.156.205
5 2026-08-24 01:49 639231325035670078
47 ms 173.230.156.205
4 2026-08-24 01:32 639231315132253837
206 ms 173.230.156.205
3 2026-08-24 01:15 639231305014280808
2185 ms 173.230.156.205
2 2026-08-24 00:23 639231273779380675
242 ms 173.230.156.205
1 2026-08-24 00:07 639231264180839154
24 ms 173.230.156.205