DNS response history for ns2.pazdigital.com

ns2.pazdigital.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-26. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 213 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.pazdigital.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

213 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

161.129.144.62

Most recently resolved hosting IP on selected date

Successful Responses

31

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.pazdigital.com

Showing DNS history for 2026-08-26 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
31 2026-08-26 09:51 639233339545274518
235 ms 161.129.144.62
30 2026-08-26 09:33 639233329214918079
241 ms 161.129.144.62
29 2026-08-26 09:16 639233318749762337
123 ms 161.129.144.62
28 2026-08-26 08:59 639233308387917838
121 ms 161.129.144.62
27 2026-08-26 08:41 639233297961740122
251 ms 161.129.144.62
26 2026-08-26 08:24 639233287487159094
245 ms 161.129.144.62
25 2026-08-26 08:06 639233276995531707
242 ms 161.129.144.62
24 2026-08-26 07:49 639233266521568229
237 ms 161.129.144.62
23 2026-08-26 07:31 639233256081047431
226 ms 161.129.144.62
22 2026-08-26 06:37 639233223620132921
225 ms 161.129.144.62
21 2026-08-26 06:20 639233213287814244
264 ms 161.129.144.62
20 2026-08-26 06:03 639233202925983161
226 ms 161.129.144.62
19 2026-08-26 05:46 639233192644780696
248 ms 161.129.144.62
18 2026-08-26 05:28 639233182401183833
237 ms 161.129.144.62
17 2026-08-26 05:11 639233172074181051
113 ms 161.129.144.62
16 2026-08-26 04:54 639233161808421455
238 ms 161.129.144.62
15 2026-08-26 04:37 639233151357344052
228 ms 161.129.144.62
14 2026-08-26 04:20 639233141034116946
338 ms 161.129.144.62
13 2026-08-26 04:03 639233130828334142
114 ms 161.129.144.62
12 2026-08-26 03:45 639233120373450007
120 ms 161.129.144.62
11 2026-08-26 03:28 639233110066216193
234 ms 161.129.144.62
10 2026-08-26 02:35 639233078065410564
122 ms 161.129.144.62
9 2026-08-26 02:18 639233067787457832
231 ms 161.129.144.62
8 2026-08-26 02:00 639233057501801162
238 ms 161.129.144.62
7 2026-08-26 01:43 639233047089431703
230 ms 161.129.144.62
6 2026-08-26 01:26 639233036754790688
226 ms 161.129.144.62
5 2026-08-26 01:09 639233026412602472
228 ms 161.129.144.62
4 2026-08-26 00:51 639233016064066127
235 ms 161.129.144.62
3 2026-08-26 00:34 639233005922655772
121 ms 161.129.144.62
2 2026-08-26 00:17 639232995672256907
230 ms 161.129.144.62
1 2026-08-26 00:00 639232985300872416
230 ms 161.129.144.62