DNS response history for ns267.pair.com

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

39

Historical checks stored for this nameserver on selected date

Average Latency

473 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 16:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.2.112

Most recently resolved hosting IP on selected date

Successful Responses

39

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 ns267.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
39 2026-08-24 16:40 639231860258429562
155 ms 209.68.2.112
38 2026-08-24 15:46 639231828211839931
136 ms 209.68.2.112
37 2026-08-24 15:30 639231818080917481
2102 ms 209.68.2.112
36 2026-08-24 15:12 639231807961539652
140 ms 209.68.2.112
35 2026-08-24 14:55 639231797631669865
146 ms 209.68.2.112
34 2026-08-24 14:03 639231765923559455
101 ms 209.68.2.112
33 2026-08-24 13:46 639231755868832964
100 ms 209.68.2.112
32 2026-08-24 13:29 639231745628278877
2156 ms 209.68.2.112
31 2026-08-24 13:11 639231735407682062
106 ms 209.68.2.112
30 2026-08-24 12:19 639231703815441688
102 ms 209.68.2.112
29 2026-08-24 12:02 639231693747052549
2121 ms 209.68.2.112
28 2026-08-24 11:45 639231683712487276
101 ms 209.68.2.112
27 2026-08-24 11:28 639231673513573868
139 ms 209.68.2.112
26 2026-08-24 10:35 639231641791249939
100 ms 209.68.2.112
25 2026-08-24 10:19 639231631866211033
117 ms 209.68.2.112
24 2026-08-24 10:02 639231621644955316
2107 ms 209.68.2.112
23 2026-08-24 09:45 639231611478799259
105 ms 209.68.2.112
22 2026-08-24 08:53 639231579923718211
106 ms 209.68.2.112
21 2026-08-24 08:36 639231569810702936
103 ms 209.68.2.112
20 2026-08-24 08:19 639231559762411619
113 ms 209.68.2.112
19 2026-08-24 08:02 639231549663595407
124 ms 209.68.2.112
18 2026-08-24 07:09 639231518076817246
100 ms 209.68.2.112
17 2026-08-24 06:53 639231508078650885
99 ms 209.68.2.112
16 2026-08-24 06:36 639231498210697093
103 ms 209.68.2.112
15 2026-08-24 06:20 639231488109699360
101 ms 209.68.2.112
14 2026-08-24 05:27 639231456772510692
111 ms 209.68.2.112
13 2026-08-24 05:11 639231447084631185
116 ms 209.68.2.112
12 2026-08-24 04:55 639231437208519473
97 ms 209.68.2.112
11 2026-08-24 04:38 639231427209627490
2160 ms 209.68.2.112
10 2026-08-24 03:46 639231395791246644
115 ms 209.68.2.112
9 2026-08-24 03:29 639231386075551458
101 ms 209.68.2.112
8 2026-08-24 03:13 639231376208713791
98 ms 209.68.2.112
7 2026-08-24 02:56 639231366170589276
2103 ms 209.68.2.112
6 2026-08-24 02:04 639231334732159368
96 ms 209.68.2.112
5 2026-08-24 01:48 639231325035670078
100 ms 209.68.2.112
4 2026-08-24 01:31 639231315132253837
99 ms 209.68.2.112
3 2026-08-24 01:14 639231305014280808
101 ms 209.68.2.112
2 2026-08-24 00:22 639231273779380675
142 ms 209.68.2.112
1 2026-08-24 00:06 639231264180839154
2124 ms 209.68.2.112