DNS response history for ns2.persecondnews.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

430 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.121.85.24

Most recently resolved hosting IP on selected date

Successful Responses

36

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.persecondnews.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
36 2026-08-25 12:34 639232576780683689
225 ms 129.121.85.24
35 2026-08-25 12:16 639232566381512620
156 ms 129.121.85.24
34 2026-08-25 11:59 639232556111768563
108 ms 129.121.85.24
33 2026-08-25 11:42 639232545839529039
109 ms 129.121.85.24
32 2026-08-25 11:25 639232535349285207
105 ms 129.121.85.24
31 2026-08-25 11:07 639232524938080723
217 ms 129.121.85.24
30 2026-08-25 10:13 639232492740373468
197 ms 129.121.85.24
29 2026-08-25 09:56 639232482235303141
125 ms 129.121.85.24
28 2026-08-25 09:39 639232471861770303
148 ms 129.121.85.24
27 2026-08-25 09:22 639232461630217327
267 ms 129.121.85.24
26 2026-08-25 09:04 639232451282965990
240 ms 129.121.85.24
25 2026-08-25 08:47 639232440814614938
196 ms 129.121.85.24
24 2026-08-25 08:29 639232430410720425
109 ms 129.121.85.24
23 2026-08-25 08:12 639232420003096185
114 ms 129.121.85.24
22 2026-08-25 07:55 639232409467287444
2123 ms 129.121.85.24
21 2026-08-25 07:37 639232399077195997
200 ms 129.121.85.24
20 2026-08-25 07:20 639232388731528337
15 ms 129.121.85.24
19 2026-08-25 07:03 639232378288598612
221 ms 129.121.85.24
18 2026-08-25 06:09 639232346196373643
24 ms 129.121.85.24
17 2026-08-25 05:52 639232336112370741
136 ms 129.121.85.24
16 2026-08-25 05:36 639232326146508970
4104 ms 129.121.85.24
15 2026-08-25 05:19 639232316189381720
2112 ms 129.121.85.24
14 2026-08-25 05:03 639232306217998913
206 ms 129.121.85.24
13 2026-08-25 04:46 639232296255744174
104 ms 129.121.85.24
12 2026-08-25 04:29 639232286095760789
240 ms 129.121.85.24
11 2026-08-25 04:12 639232276086186273
46 ms 129.121.85.24
10 2026-08-25 03:55 639232265900986425
38 ms 129.121.85.24
9 2026-08-25 03:38 639232255723518075
2121 ms 129.121.85.24
8 2026-08-25 03:21 639232245484452890
231 ms 129.121.85.24
7 2026-08-25 03:04 639232235157175331
212 ms 129.121.85.24
6 2026-08-25 02:11 639232203197189095
249 ms 129.121.85.24
5 2026-08-25 01:54 639232192844564298
14 ms 129.121.85.24
4 2026-08-25 01:36 639232182496008942
212 ms 129.121.85.24
3 2026-08-25 01:19 639232172197053132
195 ms 129.121.85.24
2 2026-08-25 00:26 639232140250307418
166 ms 129.121.85.24
1 2026-08-25 00:09 639232129927860324
198 ms 129.121.85.24