DNS response history for ns2.aplusmedia.com

ns2.aplusmedia.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-29. For this date, NameServerHistory found 28 DNS check records, 27 successful responses, 1 failed responses, and 71 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.aplusmedia.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

71 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 09:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

139.180.172.112

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.aplusmedia.com

Showing DNS history for 2026-08-29 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
28 2026-08-29 09:28 639235924465736791
79 ms 139.180.172.112
27 2026-08-29 09:12 639235914430611197
53 ms 139.180.172.112
26 2026-08-29 08:55 639235904343784853
33 ms 139.180.172.112
25 2026-08-29 08:38 639235894201078068
153 ms 139.180.172.112
24 2026-08-29 08:21 639235884233447452
121 ms 139.180.172.112
23 2026-08-29 08:05 639235874142207309
101 ms 139.180.172.112
22 2026-08-29 07:48 639235863974652466
70 ms 139.180.172.112
21 2026-08-29 07:30 639235853716243436
142 ms 139.180.172.112
20 2026-08-29 07:14 639235843614494759
83 ms 139.180.172.112
19 2026-08-29 06:57 639235833401459551
39 ms 139.180.172.112
18 2026-08-29 06:40 639235823220464528
29 ms 139.180.172.112
17 2026-08-29 06:23 639235812997510905
65 ms 139.180.172.112
16 2026-08-29 05:30 639235781101962521
-
15 2026-08-29 05:13 639235771207673260
78 ms 139.180.172.112
14 2026-08-29 04:56 639235761047429642
38 ms 139.180.172.112
13 2026-08-29 04:39 639235750964347246
25 ms 139.180.172.112
12 2026-08-29 04:22 639235740923490874
55 ms 139.180.172.112
11 2026-08-29 04:06 639235730842894399
29 ms 139.180.172.112
10 2026-08-29 03:49 639235720760084717
40 ms 139.180.172.112
9 2026-08-29 03:32 639235710843666743
53 ms 139.180.172.112
8 2026-08-29 03:16 639235700733510561
31 ms 139.180.172.112
7 2026-08-29 02:58 639235690509906192
98 ms 139.180.172.112
6 2026-08-29 02:41 639235680156673501
116 ms 139.180.172.112
5 2026-08-29 02:24 639235669720606443
58 ms 139.180.172.112
4 2026-08-29 01:30 639235637451417084
185 ms 139.180.172.112
3 2026-08-29 01:13 639235627307383453
53 ms 139.180.172.112
2 2026-08-29 00:56 639235616906386856
24 ms 139.180.172.112
1 2026-08-29 00:39 639235606582912691
61 ms 139.180.172.112