DNS response history for ns2.perrolento.com

ns2.perrolento.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 34 DNS check records, 34 successful responses, 0 failed responses, and 343 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.perrolento.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

343 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.98.65.232

Most recently resolved hosting IP on selected date

Successful Responses

34

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.perrolento.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
34 2026-08-25 12:01 639232556111768563
83 ms 91.98.65.232
33 2026-08-25 11:44 639232545839529039
1574 ms 91.98.65.232
32 2026-08-25 11:26 639232535349285207
70 ms 91.98.65.232
31 2026-08-25 11:09 639232524938080723
88 ms 91.98.65.232
30 2026-08-25 10:15 639232492740373468
85 ms 91.98.65.232
29 2026-08-25 09:58 639232482235303141
7 ms 91.98.65.232
28 2026-08-25 09:40 639232471861770303
99 ms 91.98.65.232
27 2026-08-25 09:23 639232461630217327
15 ms 91.98.65.232
26 2026-08-25 09:06 639232451282965990
82 ms 91.98.65.232
25 2026-08-25 08:48 639232440814614938
83 ms 91.98.65.232
24 2026-08-25 08:31 639232430410720425
74 ms 91.98.65.232
23 2026-08-25 08:14 639232420003096185
45 ms 91.98.65.232
22 2026-08-25 07:56 639232409467287444
74 ms 91.98.65.232
21 2026-08-25 07:39 639232399077195997
90 ms 91.98.65.232
20 2026-08-25 07:22 639232388731528337
90 ms 91.98.65.232
19 2026-08-25 07:04 639232378288598612
77 ms 91.98.65.232
18 2026-08-25 06:11 639232346196373643
73 ms 91.98.65.232
17 2026-08-25 05:54 639232336112370741
34 ms 91.98.65.232
16 2026-08-25 05:37 639232326146508970
68 ms 91.98.65.232
15 2026-08-25 05:21 639232316189381720
91 ms 91.98.65.232
14 2026-08-25 05:04 639232306217998913
52 ms 91.98.65.232
13 2026-08-25 04:48 639232296255744174
106 ms 91.98.65.232
12 2026-08-25 04:31 639232286095760789
2048 ms 91.98.65.232
11 2026-08-25 04:14 639232276086186273
64 ms 91.98.65.232
10 2026-08-25 03:57 639232265900986425
55 ms 91.98.65.232
9 2026-08-25 03:40 639232255723518075
37 ms 91.98.65.232
8 2026-08-25 03:23 639232245484452890
55 ms 91.98.65.232
7 2026-08-25 03:06 639232235157175331
98 ms 91.98.65.232
6 2026-08-25 02:12 639232203197189095
446 ms 91.98.65.232
5 2026-08-25 01:55 639232192844564298
4035 ms 91.98.65.232
4 2026-08-25 01:38 639232182496008942
8 ms 91.98.65.232
3 2026-08-25 01:21 639232172197053132
76 ms 91.98.65.232
2 2026-08-25 00:27 639232140250307418
1563 ms 91.98.65.232
1 2026-08-25 00:10 639232129927860324
101 ms 91.98.65.232