DNS response history for ns2.perditum.com

ns2.perditum.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 176 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.perditum.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

176 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.242.203.68

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.perditum.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:00 639232556111768563
125 ms 38.242.203.68
33 2026-08-25 11:43 639232545839529039
23 ms 38.242.203.68
32 2026-08-25 11:26 639232535349285207
125 ms 38.242.203.68
31 2026-08-25 11:08 639232524938080723
70 ms 38.242.203.68
30 2026-08-25 10:15 639232492740373468
10 ms 38.242.203.68
29 2026-08-25 09:57 639232482235303141
36 ms 38.242.203.68
28 2026-08-25 09:40 639232471861770303
5 ms 38.242.203.68
27 2026-08-25 09:23 639232461630217327
15 ms 38.242.203.68
26 2026-08-25 09:06 639232451282965990
105 ms 38.242.203.68
25 2026-08-25 08:48 639232440814614938
126 ms 38.242.203.68
24 2026-08-25 08:31 639232430410720425
30 ms 38.242.203.68
23 2026-08-25 08:14 639232420003096185
104 ms 38.242.203.68
22 2026-08-25 07:56 639232409467287444
258 ms 38.242.203.68
21 2026-08-25 07:39 639232399077195997
35 ms 38.242.203.68
20 2026-08-25 07:21 639232388731528337
114 ms 38.242.203.68
19 2026-08-25 07:04 639232378288598612
2008 ms 38.242.203.68
18 2026-08-25 06:11 639232346196373643
20 ms 38.242.203.68
17 2026-08-25 05:54 639232336112370741
18 ms 38.242.203.68
16 2026-08-25 05:37 639232326146508970
10 ms 38.242.203.68
15 2026-08-25 05:20 639232316189381720
12 ms 38.242.203.68
14 2026-08-25 05:04 639232306217998913
13 ms 38.242.203.68
13 2026-08-25 04:47 639232296255744174
31 ms 38.242.203.68
12 2026-08-25 04:30 639232286095760789
8 ms 38.242.203.68
11 2026-08-25 04:14 639232276086186273
26 ms 38.242.203.68
10 2026-08-25 03:57 639232265900986425
7 ms 38.242.203.68
9 2026-08-25 03:40 639232255723518075
53 ms 38.242.203.68
8 2026-08-25 03:23 639232245484452890
16 ms 38.242.203.68
7 2026-08-25 03:06 639232235157175331
27 ms 38.242.203.68
6 2026-08-25 02:12 639232203197189095
111 ms 38.242.203.68
5 2026-08-25 01:55 639232192844564298
112 ms 38.242.203.68
4 2026-08-25 01:38 639232182496008942
111 ms 38.242.203.68
3 2026-08-25 01:20 639232172197053132
11 ms 38.242.203.68
2 2026-08-25 00:27 639232140250307418
2110 ms 38.242.203.68
1 2026-08-25 00:10 639232129927860324
114 ms 38.242.203.68