DNS response history for ns.paralibros.com

ns.paralibros.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-25. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 863 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 ns.paralibros.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

863 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

190.210.9.230

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns.paralibros.com

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
29 2026-08-25 09:48 639232471861770303
961 ms 190.210.9.230
28 2026-08-25 09:30 639232461630217327
717 ms 190.210.9.230
27 2026-08-25 09:13 639232451282965990
713 ms 190.210.9.230
26 2026-08-25 08:56 639232440814614938
954 ms 190.210.9.230
25 2026-08-25 08:39 639232430410720425
721 ms 190.210.9.230
24 2026-08-25 08:21 639232420003096185
962 ms 190.210.9.230
23 2026-08-25 08:04 639232409467287444
957 ms 190.210.9.230
22 2026-08-25 07:46 639232399077195997
727 ms 190.210.9.230
21 2026-08-25 07:29 639232388731528337
720 ms 190.210.9.230
20 2026-08-25 07:12 639232378288598612
718 ms 190.210.9.230
19 2026-08-25 06:18 639232346196373643
239 ms 190.210.9.230
18 2026-08-25 06:01 639232336112370741
722 ms 190.210.9.230
17 2026-08-25 05:44 639232326146508970
959 ms 190.210.9.230
16 2026-08-25 05:28 639232316189381720
469 ms 190.210.9.230
15 2026-08-25 05:11 639232306217998913
954 ms 190.210.9.230
14 2026-08-25 04:54 639232296255744174
965 ms 190.210.9.230
13 2026-08-25 04:38 639232286095760789
984 ms 190.210.9.230
12 2026-08-25 04:21 639232276086186273
947 ms 190.210.9.230
11 2026-08-25 04:04 639232265900986425
954 ms 190.210.9.230
10 2026-08-25 03:47 639232255723518075
955 ms 190.210.9.230
9 2026-08-25 03:30 639232245484452890
957 ms 190.210.9.230
8 2026-08-25 03:13 639232235157175331
961 ms 190.210.9.230
7 2026-08-25 02:20 639232203197189095
709 ms 190.210.9.230
6 2026-08-25 02:03 639232192844564298
957 ms 190.210.9.230
5 2026-08-25 01:45 639232182496008942
717 ms 190.210.9.230
4 2026-08-25 01:28 639232172197053132
2249 ms 190.210.9.230
3 2026-08-25 00:35 639232140250307418
720 ms 190.210.9.230
2 2026-08-25 00:18 639232129927860324
715 ms 190.210.9.230
1 2026-08-25 00:00 639232119551972438
744 ms 190.210.9.230