DNS response history for ns2.personal.net.py

ns2.personal.net.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-25. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 445 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.personal.net.py.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

445 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

190.104.137.150

Most recently resolved hosting IP on selected date

Successful Responses

32

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.personal.net.py

Showing DNS history for 2026-08-25 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
32 2026-08-25 11:32 639232535349285207
259 ms 190.104.137.150
31 2026-08-25 11:15 639232524938080723
259 ms 190.104.137.150
30 2026-08-25 10:21 639232492740373468
261 ms 190.104.137.150
29 2026-08-25 10:04 639232482235303141
5 ms 190.104.137.150
28 2026-08-25 09:46 639232471861770303
3 ms 190.104.137.150
27 2026-08-25 09:29 639232461630217327
253 ms 190.104.137.150
26 2026-08-25 09:12 639232451282965990
6 ms 190.104.137.150
25 2026-08-25 08:55 639232440814614938
525 ms 190.104.137.150
24 2026-08-25 08:37 639232430410720425
1031 ms 190.104.137.150
23 2026-08-25 08:20 639232420003096185
262 ms 190.104.137.150
22 2026-08-25 08:02 639232409467287444
5 ms 190.104.137.150
21 2026-08-25 07:45 639232399077195997
1029 ms 190.104.137.150
20 2026-08-25 07:28 639232388731528337
525 ms 190.104.137.150
19 2026-08-25 07:10 639232378288598612
1025 ms 190.104.137.150
18 2026-08-25 06:16 639232346196373643
694 ms 190.104.137.150
17 2026-08-25 06:00 639232336112370741
1021 ms 190.104.137.150
16 2026-08-25 05:43 639232326146508970
262 ms 190.104.137.150
15 2026-08-25 05:26 639232316189381720
265 ms 190.104.137.150
14 2026-08-25 05:10 639232306217998913
847 ms 190.104.137.150
13 2026-08-25 04:53 639232296255744174
242 ms 190.104.137.150
12 2026-08-25 04:36 639232286095760789
536 ms 190.104.137.150
11 2026-08-25 04:19 639232276086186273
261 ms 190.104.137.150
10 2026-08-25 04:03 639232265900986425
257 ms 190.104.137.150
9 2026-08-25 03:46 639232255723518075
263 ms 190.104.137.150
8 2026-08-25 03:29 639232245484452890
527 ms 190.104.137.150
7 2026-08-25 03:12 639232235157175331
258 ms 190.104.137.150
6 2026-08-25 02:18 639232203197189095
9 ms 190.104.137.150
5 2026-08-25 02:01 639232192844564298
267 ms 190.104.137.150
4 2026-08-25 01:44 639232182496008942
265 ms 190.104.137.150
3 2026-08-25 01:27 639232172197053132
257 ms 190.104.137.150
2 2026-08-25 00:33 639232140250307418
513 ms 190.104.137.150
1 2026-08-25 00:16 639232129927860324
2048 ms 190.104.137.150