DNS response history for ns2.pneusft.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

161 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

134.195.196.39

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.pneusft.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
32 2026-08-25 11:29 639232535349285207
3 ms 134.195.196.39
31 2026-08-25 11:12 639232524938080723
15 ms 134.195.196.39
30 2026-08-25 10:18 639232492740373468
234 ms 134.195.196.39
29 2026-08-25 10:01 639232482235303141
112 ms 134.195.196.39
28 2026-08-25 09:43 639232471861770303
243 ms 134.195.196.39
27 2026-08-25 09:26 639232461630217327
125 ms 134.195.196.39
26 2026-08-25 09:09 639232451282965990
235 ms 134.195.196.39
25 2026-08-25 08:52 639232440814614938
326 ms 134.195.196.39
24 2026-08-25 08:34 639232430410720425
244 ms 134.195.196.39
23 2026-08-25 08:17 639232420003096185
233 ms 134.195.196.39
22 2026-08-25 08:00 639232409467287444
259 ms 134.195.196.39
21 2026-08-25 07:42 639232399077195997
107 ms 134.195.196.39
20 2026-08-25 07:25 639232388731528337
266 ms 134.195.196.39
19 2026-08-25 07:07 639232378288598612
109 ms 134.195.196.39
18 2026-08-25 06:14 639232346196373643
11 ms 134.195.196.39
17 2026-08-25 05:57 639232336112370741
33 ms 134.195.196.39
16 2026-08-25 05:40 639232326146508970
25 ms 134.195.196.39
15 2026-08-25 05:24 639232316189381720
57 ms 134.195.196.39
14 2026-08-25 05:07 639232306217998913
440 ms 134.195.196.39
13 2026-08-25 04:50 639232296255744174
18 ms 134.195.196.39
12 2026-08-25 04:34 639232286095760789
224 ms 134.195.196.39
11 2026-08-25 04:17 639232276086186273
217 ms 134.195.196.39
10 2026-08-25 04:00 639232265900986425
212 ms 134.195.196.39
9 2026-08-25 03:43 639232255723518075
229 ms 134.195.196.39
8 2026-08-25 03:26 639232245484452890
111 ms 134.195.196.39
7 2026-08-25 03:09 639232235157175331
225 ms 134.195.196.39
6 2026-08-25 02:15 639232203197189095
4 ms 134.195.196.39
5 2026-08-25 01:58 639232192844564298
112 ms 134.195.196.39
4 2026-08-25 01:41 639232182496008942
227 ms 134.195.196.39
3 2026-08-25 01:24 639232172197053132
249 ms 134.195.196.39
2 2026-08-25 00:30 639232140250307418
7 ms 134.195.196.39
1 2026-08-25 00:14 639232129927860324
235 ms 134.195.196.39