DNS response history for ns2.digipark.com

ns2.digipark.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-31. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 513 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.digipark.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

513 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.82.115.181

Most recently resolved hosting IP on selected date

Successful Responses

37

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.digipark.com

Showing DNS history for 2026-08-31 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
37 2026-08-31 12:07 639237742927117371
236 ms 208.82.115.181
36 2026-08-31 11:49 639237732538256235
234 ms 208.82.115.181
35 2026-08-31 11:32 639237722025682013
9 ms 208.82.115.181
34 2026-08-31 11:14 639237711568720101
237 ms 208.82.115.181
33 2026-08-31 10:57 639237701119461876
7 ms 208.82.115.181
32 2026-08-31 10:40 639237690759595513
2281 ms 208.82.115.181
31 2026-08-31 10:22 639237680122296836
278 ms 208.82.115.181
30 2026-08-31 09:28 639237647999458954
277 ms 208.82.115.181
29 2026-08-31 09:12 639237637680951774
2008 ms 208.82.115.181
28 2026-08-31 08:54 639237627437728712
142 ms 208.82.115.181
27 2026-08-31 08:37 639237617127808241
5 ms 208.82.115.181
26 2026-08-31 08:20 639237606990101394
233 ms 208.82.115.181
25 2026-08-31 08:03 639237596595480036
2031 ms 208.82.115.181
24 2026-08-31 07:46 639237586261012001
156 ms 208.82.115.181
23 2026-08-31 07:28 639237576047657695
117 ms 208.82.115.181
22 2026-08-31 07:11 639237565832936443
117 ms 208.82.115.181
21 2026-08-31 06:54 639237555466329546
2142 ms 208.82.115.181
20 2026-08-31 06:37 639237545032411072
4 ms 208.82.115.181
19 2026-08-31 06:19 639237534469438634
305 ms 208.82.115.181
18 2026-08-31 05:26 639237502279296801
3 ms 208.82.115.181
17 2026-08-31 05:09 639237492362730124
3 ms 208.82.115.181
16 2026-08-31 04:52 639237482311584319
143 ms 208.82.115.181
15 2026-08-31 04:36 639237472150685594
232 ms 208.82.115.181
14 2026-08-31 04:19 639237462055295430
230 ms 208.82.115.181
13 2026-08-31 04:02 639237452089913890
139 ms 208.82.115.181
12 2026-08-31 03:45 639237441972654103
3 ms 208.82.115.181
11 2026-08-31 03:28 639237432052396478
4 ms 208.82.115.181
10 2026-08-31 03:12 639237422012990851
2212 ms 208.82.115.181
9 2026-08-31 02:55 639237411889602012
3 ms 208.82.115.181
8 2026-08-31 02:38 639237401637354221
4 ms 208.82.115.181
7 2026-08-31 02:21 639237391412690360
3 ms 208.82.115.181
6 2026-08-31 01:28 639237359972957132
4 ms 208.82.115.181
5 2026-08-31 01:12 639237350032183979
228 ms 208.82.115.181
4 2026-08-31 00:55 639237340111452066
230 ms 208.82.115.181
3 2026-08-31 00:39 639237329967272514
226 ms 208.82.115.181
2 2026-08-31 00:22 639237319916508151
2364 ms 208.82.115.181
1 2026-08-31 00:05 639237309944877243
2120 ms 208.82.115.181