DNS response history for ns2.pfupdate.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

272 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.123.73.78

Most recently resolved hosting IP on selected date

Successful Responses

38

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.pfupdate.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
38 2026-08-25 13:01 639232587225721862
279 ms 208.123.73.78
37 2026-08-25 12:43 639232576780683689
283 ms 208.123.73.78
36 2026-08-25 12:26 639232566381512620
275 ms 208.123.73.78
35 2026-08-25 12:09 639232556111768563
280 ms 208.123.73.78
34 2026-08-25 11:52 639232545839529039
275 ms 208.123.73.78
33 2026-08-25 11:34 639232535349285207
275 ms 208.123.73.78
32 2026-08-25 11:17 639232524938080723
275 ms 208.123.73.78
31 2026-08-25 10:23 639232492740373468
269 ms 208.123.73.78
30 2026-08-25 10:06 639232482235303141
275 ms 208.123.73.78
29 2026-08-25 09:48 639232471861770303
277 ms 208.123.73.78
28 2026-08-25 09:31 639232461630217327
282 ms 208.123.73.78
27 2026-08-25 09:14 639232451282965990
278 ms 208.123.73.78
26 2026-08-25 08:57 639232440814614938
277 ms 208.123.73.78
25 2026-08-25 08:39 639232430410720425
273 ms 208.123.73.78
24 2026-08-25 08:22 639232420003096185
280 ms 208.123.73.78
23 2026-08-25 08:05 639232409467287444
283 ms 208.123.73.78
22 2026-08-25 07:47 639232399077195997
275 ms 208.123.73.78
21 2026-08-25 07:30 639232388731528337
279 ms 208.123.73.78
20 2026-08-25 07:12 639232378288598612
275 ms 208.123.73.78
19 2026-08-25 06:18 639232346196373643
280 ms 208.123.73.78
18 2026-08-25 06:02 639232336112370741
275 ms 208.123.73.78
17 2026-08-25 05:45 639232326146508970
140 ms 208.123.73.78
16 2026-08-25 05:28 639232316189381720
272 ms 208.123.73.78
15 2026-08-25 05:12 639232306217998913
272 ms 208.123.73.78
14 2026-08-25 04:55 639232296255744174
274 ms 208.123.73.78
13 2026-08-25 04:38 639232286095760789
273 ms 208.123.73.78
12 2026-08-25 04:21 639232276086186273
272 ms 208.123.73.78
11 2026-08-25 04:05 639232265900986425
275 ms 208.123.73.78
10 2026-08-25 03:48 639232255723518075
274 ms 208.123.73.78
9 2026-08-25 03:31 639232245484452890
280 ms 208.123.73.78
8 2026-08-25 03:14 639232235157175331
273 ms 208.123.73.78
7 2026-08-25 02:20 639232203197189095
273 ms 208.123.73.78
6 2026-08-25 02:03 639232192844564298
271 ms 208.123.73.78
5 2026-08-25 01:46 639232182496008942
271 ms 208.123.73.78
4 2026-08-25 01:29 639232172197053132
273 ms 208.123.73.78
3 2026-08-25 00:35 639232140250307418
270 ms 208.123.73.78
2 2026-08-25 00:18 639232129927860324
273 ms 208.123.73.78
1 2026-08-25 00:01 639232119551972438
274 ms 208.123.73.78