DNS response history for ns2.base.com.py

ns2.base.com.py 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 36 DNS check records, 36 successful responses, 0 failed responses, and 384 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.base.com.py.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

384 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

181.94.246.113

Most recently resolved hosting IP on selected date

Successful Responses

36

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.base.com.py

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
36 2026-08-24 15:19 639231807961539652
276 ms 181.94.246.113
35 2026-08-24 15:02 639231797631669865
359 ms 181.94.246.113
34 2026-08-24 14:09 639231765923559455
706 ms 181.94.246.113
33 2026-08-24 13:52 639231755868832964
4 ms 181.94.246.113
32 2026-08-24 13:36 639231745628278877
4 ms 181.94.246.113
31 2026-08-24 13:18 639231735407682062
4 ms 181.94.246.113
30 2026-08-24 12:26 639231703815441688
271 ms 181.94.246.113
29 2026-08-24 12:09 639231693747052549
263 ms 181.94.246.113
28 2026-08-24 11:52 639231683712487276
198 ms 181.94.246.113
27 2026-08-24 11:35 639231673513573868
536 ms 181.94.246.113
26 2026-08-24 10:42 639231641791249939
261 ms 181.94.246.113
25 2026-08-24 10:26 639231631866211033
48 ms 181.94.246.113
24 2026-08-24 10:09 639231621644955316
526 ms 181.94.246.113
23 2026-08-24 09:52 639231611478799259
528 ms 181.94.246.113
22 2026-08-24 08:59 639231579923718211
269 ms 181.94.246.113
21 2026-08-24 08:42 639231569810702936
527 ms 181.94.246.113
20 2026-08-24 08:25 639231559762411619
9 ms 181.94.246.113
19 2026-08-24 08:09 639231549663595407
4 ms 181.94.246.113
18 2026-08-24 07:16 639231518076817246
527 ms 181.94.246.113
17 2026-08-24 07:00 639231508078650885
263 ms 181.94.246.113
16 2026-08-24 06:43 639231498210697093
527 ms 181.94.246.113
15 2026-08-24 06:26 639231488109699360
17 ms 181.94.246.113
14 2026-08-24 05:34 639231456772510692
464 ms 181.94.246.113
13 2026-08-24 05:18 639231447084631185
3 ms 181.94.246.113
12 2026-08-24 05:01 639231437208519473
13 ms 181.94.246.113
11 2026-08-24 04:45 639231427209627490
2487 ms 181.94.246.113
10 2026-08-24 03:52 639231395791246644
526 ms 181.94.246.113
9 2026-08-24 03:36 639231386075551458
620 ms 181.94.246.113
8 2026-08-24 03:20 639231376208713791
2277 ms 181.94.246.113
7 2026-08-24 03:03 639231366170589276
265 ms 181.94.246.113
6 2026-08-24 02:11 639231334732159368
4 ms 181.94.246.113
5 2026-08-24 01:54 639231325035670078
3 ms 181.94.246.113
4 2026-08-24 01:38 639231315132253837
526 ms 181.94.246.113
3 2026-08-24 01:21 639231305014280808
263 ms 181.94.246.113
2 2026-08-24 00:29 639231273779380675
3 ms 181.94.246.113
1 2026-08-24 00:13 639231264180839154
259 ms 181.94.246.113