DNS response history for ns2.netlogic.com.py

ns2.netlogic.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-09-01. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 485 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.netlogic.com.py.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

485 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

190.104.148.78

Most recently resolved hosting IP on selected date

Successful Responses

35

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

Showing DNS history for 2026-09-01 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
35 2026-09-01 12:13 639238607506044626
2308 ms 190.104.148.78
34 2026-09-01 11:56 639238597040761406
549 ms 190.104.148.78
33 2026-09-01 11:38 639238586261546969
501 ms 190.104.148.78
32 2026-09-01 11:20 639238575587642333
261 ms 190.104.148.78
31 2026-09-01 10:26 639238543127398267
5 ms 190.104.148.78
30 2026-09-01 10:08 639238532668234016
3 ms 190.104.148.78
29 2026-09-01 09:51 639238522029321761
255 ms 190.104.148.78
28 2026-09-01 09:33 639238511519050351
264 ms 190.104.148.78
27 2026-09-01 09:16 639238500942239673
515 ms 190.104.148.78
26 2026-09-01 08:58 639238490412377398
521 ms 190.104.148.78
25 2026-09-01 08:40 639238479833203021
248 ms 190.104.148.78
24 2026-09-01 08:23 639238469140507479
510 ms 190.104.148.78
23 2026-09-01 08:05 639238458443560361
254 ms 190.104.148.78
22 2026-09-01 07:47 639238447694851502
260 ms 190.104.148.78
21 2026-09-01 07:29 639238436624109087
253 ms 190.104.148.78
20 2026-09-01 07:11 639238425565611335
264 ms 190.104.148.78
19 2026-09-01 06:15 639238392250222581
520 ms 190.104.148.78
18 2026-09-01 05:57 639238381322537831
261 ms 190.104.148.78
17 2026-09-01 05:38 639238370248186084
484 ms 190.104.148.78
16 2026-09-01 05:20 639238359264687845
627 ms 190.104.148.78
15 2026-09-01 05:02 639238348534621818
495 ms 190.104.148.78
14 2026-09-01 04:44 639238337725739433
518 ms 190.104.148.78
13 2026-09-01 04:26 639238326844749368
253 ms 190.104.148.78
12 2026-09-01 04:08 639238315792024737
255 ms 190.104.148.78
11 2026-09-01 03:49 639238304931064768
499 ms 190.104.148.78
10 2026-09-01 03:31 639238294131483803
524 ms 190.104.148.78
9 2026-09-01 03:13 639238283314985519
660 ms 190.104.148.78
8 2026-09-01 02:55 639238272374093187
505 ms 190.104.148.78
7 2026-09-01 02:01 639238240032549922
481 ms 190.104.148.78
6 2026-09-01 01:43 639238229204177368
952 ms 190.104.148.78
5 2026-09-01 01:25 639238218326150282
743 ms 190.104.148.78
4 2026-09-01 01:07 639238207574700853
483 ms 190.104.148.78
3 2026-09-01 00:49 639238196660283915
737 ms 190.104.148.78
2 2026-09-01 00:31 639238185782358546
499 ms 190.104.148.78
1 2026-09-01 00:13 639238175054391781
510 ms 190.104.148.78