DNS response history for ns2.digitalapss.com

ns2.digitalapss.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-30. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 295 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.digitalapss.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

295 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 08:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.191.132.192

Most recently resolved hosting IP on selected date

Successful Responses

27

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

Showing DNS history for 2026-08-30 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
27 2026-08-30 08:43 639236755602384085
352 ms 103.191.132.192
26 2026-08-30 08:26 639236745600094925
353 ms 103.191.132.192
25 2026-08-30 08:09 639236735311262753
169 ms 103.191.132.192
24 2026-08-30 07:52 639236724996745235
322 ms 103.191.132.192
23 2026-08-30 07:35 639236714839899761
352 ms 103.191.132.192
22 2026-08-30 07:18 639236704748431488
231 ms 103.191.132.192
21 2026-08-30 07:01 639236694430128550
339 ms 103.191.132.192
20 2026-08-30 06:44 639236684143292417
355 ms 103.191.132.192
19 2026-08-30 06:27 639236673972499943
361 ms 103.191.132.192
18 2026-08-30 05:34 639236642126522802
365 ms 103.191.132.192
17 2026-08-30 05:17 639236632183518198
367 ms 103.191.132.192
16 2026-08-30 05:01 639236622289312589
3 ms 103.191.132.192
15 2026-08-30 04:44 639236612490676525
217 ms 103.191.132.192
14 2026-08-30 04:28 639236602582494852
171 ms 103.191.132.192
13 2026-08-30 04:11 639236592511706469
364 ms 103.191.132.192
12 2026-08-30 03:54 639236582441006869
365 ms 103.191.132.192
11 2026-08-30 03:38 639236572478785089
326 ms 103.191.132.192
10 2026-08-30 03:21 639236562556749999
181 ms 103.191.132.192
9 2026-08-30 03:04 639236552353482281
364 ms 103.191.132.192
8 2026-08-30 02:47 639236542188881607
180 ms 103.191.132.192
7 2026-08-30 02:30 639236531885440105
325 ms 103.191.132.192
6 2026-08-30 01:37 639236499922985383
333 ms 103.191.132.192
5 2026-08-30 01:20 639236489713594431
265 ms 103.191.132.192
4 2026-08-30 01:03 639236479750443901
368 ms 103.191.132.192
3 2026-08-30 00:46 639236469719936375
273 ms 103.191.132.192
2 2026-08-30 00:30 639236459579244885
323 ms 103.191.132.192
1 2026-08-30 00:13 639236449582837549
335 ms 103.191.132.192