DNS response history for ns269.pair.com

ns269.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 35 DNS check records, 35 successful responses, 0 failed responses, and 594 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 ns269.pair.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

594 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.2.114

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns269.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
35 2026-08-24 14:56 639231797631669865
103 ms 209.68.2.114
34 2026-08-24 14:04 639231765923559455
102 ms 209.68.2.114
33 2026-08-24 13:47 639231755868832964
135 ms 209.68.2.114
32 2026-08-24 13:30 639231745628278877
137 ms 209.68.2.114
31 2026-08-24 13:12 639231735407682062
100 ms 209.68.2.114
30 2026-08-24 12:20 639231703815441688
100 ms 209.68.2.114
29 2026-08-24 12:03 639231693747052549
116 ms 209.68.2.114
28 2026-08-24 11:46 639231683712487276
4154 ms 209.68.2.114
27 2026-08-24 11:29 639231673513573868
186 ms 209.68.2.114
26 2026-08-24 10:36 639231641791249939
122 ms 209.68.2.114
25 2026-08-24 10:20 639231631866211033
4265 ms 209.68.2.114
24 2026-08-24 10:03 639231621644955316
2183 ms 209.68.2.114
23 2026-08-24 09:46 639231611478799259
100 ms 209.68.2.114
22 2026-08-24 08:53 639231579923718211
112 ms 209.68.2.114
21 2026-08-24 08:37 639231569810702936
183 ms 209.68.2.114
20 2026-08-24 08:20 639231559762411619
99 ms 209.68.2.114
19 2026-08-24 08:03 639231549663595407
137 ms 209.68.2.114
18 2026-08-24 07:10 639231518076817246
109 ms 209.68.2.114
17 2026-08-24 06:54 639231508078650885
177 ms 209.68.2.114
16 2026-08-24 06:37 639231498210697093
2096 ms 209.68.2.114
15 2026-08-24 06:21 639231488109699360
138 ms 209.68.2.114
14 2026-08-24 05:28 639231456772510692
2101 ms 209.68.2.114
13 2026-08-24 05:12 639231447084631185
138 ms 209.68.2.114
12 2026-08-24 04:56 639231437208519473
108 ms 209.68.2.114
11 2026-08-24 04:39 639231427209627490
102 ms 209.68.2.114
10 2026-08-24 03:46 639231395791246644
136 ms 209.68.2.114
9 2026-08-24 03:30 639231386075551458
105 ms 209.68.2.114
8 2026-08-24 03:14 639231376208713791
143 ms 209.68.2.114
7 2026-08-24 02:57 639231366170589276
104 ms 209.68.2.114
6 2026-08-24 02:05 639231334732159368
2256 ms 209.68.2.114
5 2026-08-24 01:49 639231325035670078
150 ms 209.68.2.114
4 2026-08-24 01:32 639231315132253837
161 ms 209.68.2.114
3 2026-08-24 01:15 639231305014280808
186 ms 209.68.2.114
2 2026-08-24 00:23 639231273779380675
97 ms 209.68.2.114
1 2026-08-24 00:07 639231264180839154
137 ms 209.68.2.114