DNS response history for ns2.pfndesign.com

ns2.pfndesign.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 306 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.pfndesign.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

306 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.89.16.121

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.pfndesign.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:36 639232576780683689
138 ms 69.89.16.121
35 2026-08-25 12:19 639232566381512620
134 ms 69.89.16.121
34 2026-08-25 12:01 639232556111768563
130 ms 69.89.16.121
33 2026-08-25 11:44 639232545839529039
255 ms 69.89.16.121
32 2026-08-25 11:27 639232535349285207
139 ms 69.89.16.121
31 2026-08-25 11:09 639232524938080723
145 ms 69.89.16.121
30 2026-08-25 10:16 639232492740373468
157 ms 69.89.16.121
29 2026-08-25 09:59 639232482235303141
125 ms 69.89.16.121
28 2026-08-25 09:41 639232471861770303
142 ms 69.89.16.121
27 2026-08-25 09:24 639232461630217327
11 ms 69.89.16.121
26 2026-08-25 09:07 639232451282965990
129 ms 69.89.16.121
25 2026-08-25 08:49 639232440814614938
138 ms 69.89.16.121
24 2026-08-25 08:32 639232430410720425
276 ms 69.89.16.121
23 2026-08-25 08:15 639232420003096185
138 ms 69.89.16.121
22 2026-08-25 07:57 639232409467287444
133 ms 69.89.16.121
21 2026-08-25 07:40 639232399077195997
436 ms 69.89.16.121
20 2026-08-25 07:22 639232388731528337
2123 ms 69.89.16.121
19 2026-08-25 07:05 639232378288598612
128 ms 69.89.16.121
18 2026-08-25 06:12 639232346196373643
129 ms 69.89.16.121
17 2026-08-25 05:55 639232336112370741
2134 ms 69.89.16.121
16 2026-08-25 05:38 639232326146508970
141 ms 69.89.16.121
15 2026-08-25 05:21 639232316189381720
4 ms 69.89.16.121
14 2026-08-25 05:05 639232306217998913
8 ms 69.89.16.121
13 2026-08-25 04:48 639232296255744174
148 ms 69.89.16.121
12 2026-08-25 04:31 639232286095760789
138 ms 69.89.16.121
11 2026-08-25 04:15 639232276086186273
2119 ms 69.89.16.121
10 2026-08-25 03:58 639232265900986425
128 ms 69.89.16.121
9 2026-08-25 03:41 639232255723518075
269 ms 69.89.16.121
8 2026-08-25 03:24 639232245484452890
124 ms 69.89.16.121
7 2026-08-25 03:07 639232235157175331
32 ms 69.89.16.121
6 2026-08-25 02:13 639232203197189095
129 ms 69.89.16.121
5 2026-08-25 01:56 639232192844564298
7 ms 69.89.16.121
4 2026-08-25 01:39 639232182496008942
136 ms 69.89.16.121
3 2026-08-25 01:22 639232172197053132
127 ms 69.89.16.121
2 2026-08-25 00:28 639232140250307418
133 ms 69.89.16.121
1 2026-08-25 00:11 639232129927860324
245 ms 69.89.16.121