DNS response history for ns322.pair.com

ns322.pair.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-24. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 307 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 ns322.pair.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

307 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.2.167

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns322.pair.com

Showing DNS history for 2026-08-24 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
33 2026-08-24 13:46 639231755868832964
96 ms 209.68.2.167
32 2026-08-24 13:29 639231745628278877
137 ms 209.68.2.167
31 2026-08-24 13:12 639231735407682062
108 ms 209.68.2.167
30 2026-08-24 12:19 639231703815441688
138 ms 209.68.2.167
29 2026-08-24 12:03 639231693747052549
119 ms 209.68.2.167
28 2026-08-24 11:46 639231683712487276
101 ms 209.68.2.167
27 2026-08-24 11:29 639231673513573868
2097 ms 209.68.2.167
26 2026-08-24 10:36 639231641791249939
108 ms 209.68.2.167
25 2026-08-24 10:19 639231631866211033
147 ms 209.68.2.167
24 2026-08-24 10:03 639231621644955316
105 ms 209.68.2.167
23 2026-08-24 09:46 639231611478799259
98 ms 209.68.2.167
22 2026-08-24 08:53 639231579923718211
129 ms 209.68.2.167
21 2026-08-24 08:36 639231569810702936
165 ms 209.68.2.167
20 2026-08-24 08:19 639231559762411619
105 ms 209.68.2.167
19 2026-08-24 08:03 639231549663595407
96 ms 209.68.2.167
18 2026-08-24 07:10 639231518076817246
120 ms 209.68.2.167
17 2026-08-24 06:54 639231508078650885
2236 ms 209.68.2.167
16 2026-08-24 06:37 639231498210697093
141 ms 209.68.2.167
15 2026-08-24 06:20 639231488109699360
100 ms 209.68.2.167
14 2026-08-24 05:28 639231456772510692
2166 ms 209.68.2.167
13 2026-08-24 05:12 639231447084631185
102 ms 209.68.2.167
12 2026-08-24 04:55 639231437208519473
100 ms 209.68.2.167
11 2026-08-24 04:38 639231427209627490
100 ms 209.68.2.167
10 2026-08-24 03:46 639231395791246644
118 ms 209.68.2.167
9 2026-08-24 03:30 639231386075551458
182 ms 209.68.2.167
8 2026-08-24 03:14 639231376208713791
137 ms 209.68.2.167
7 2026-08-24 02:57 639231366170589276
143 ms 209.68.2.167
6 2026-08-24 02:05 639231334732159368
137 ms 209.68.2.167
5 2026-08-24 01:48 639231325035670078
99 ms 209.68.2.167
4 2026-08-24 01:32 639231315132253837
108 ms 209.68.2.167
3 2026-08-24 01:15 639231305014280808
153 ms 209.68.2.167
2 2026-08-24 00:23 639231273779380675
106 ms 209.68.2.167
1 2026-08-24 00:07 639231264180839154
143 ms 209.68.2.167