DNS response history for ns336.pair.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

340 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.2.181

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 ns336.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
38 2026-08-24 15:47 639231828211839931
101 ms 209.68.2.181
37 2026-08-24 15:31 639231818080917481
100 ms 209.68.2.181
36 2026-08-24 15:13 639231807961539652
149 ms 209.68.2.181
35 2026-08-24 14:56 639231797631669865
107 ms 209.68.2.181
34 2026-08-24 14:04 639231765923559455
106 ms 209.68.2.181
33 2026-08-24 13:47 639231755868832964
102 ms 209.68.2.181
32 2026-08-24 13:30 639231745628278877
115 ms 209.68.2.181
31 2026-08-24 13:12 639231735407682062
101 ms 209.68.2.181
30 2026-08-24 12:20 639231703815441688
111 ms 209.68.2.181
29 2026-08-24 12:03 639231693747052549
137 ms 209.68.2.181
28 2026-08-24 11:46 639231683712487276
2153 ms 209.68.2.181
27 2026-08-24 11:29 639231673513573868
148 ms 209.68.2.181
26 2026-08-24 10:37 639231641791249939
2109 ms 209.68.2.181
25 2026-08-24 10:20 639231631866211033
104 ms 209.68.2.181
24 2026-08-24 10:03 639231621644955316
108 ms 209.68.2.181
23 2026-08-24 09:46 639231611478799259
2098 ms 209.68.2.181
22 2026-08-24 08:54 639231579923718211
97 ms 209.68.2.181
21 2026-08-24 08:37 639231569810702936
262 ms 209.68.2.181
20 2026-08-24 08:20 639231559762411619
2153 ms 209.68.2.181
19 2026-08-24 08:03 639231549663595407
145 ms 209.68.2.181
18 2026-08-24 07:11 639231518076817246
197 ms 209.68.2.181
17 2026-08-24 06:54 639231508078650885
188 ms 209.68.2.181
16 2026-08-24 06:37 639231498210697093
131 ms 209.68.2.181
15 2026-08-24 06:21 639231488109699360
100 ms 209.68.2.181
14 2026-08-24 05:28 639231456772510692
98 ms 209.68.2.181
13 2026-08-24 05:12 639231447084631185
98 ms 209.68.2.181
12 2026-08-24 04:56 639231437208519473
106 ms 209.68.2.181
11 2026-08-24 04:39 639231427209627490
136 ms 209.68.2.181
10 2026-08-24 03:46 639231395791246644
98 ms 209.68.2.181
9 2026-08-24 03:30 639231386075551458
152 ms 209.68.2.181
8 2026-08-24 03:14 639231376208713791
142 ms 209.68.2.181
7 2026-08-24 02:57 639231366170589276
149 ms 209.68.2.181
6 2026-08-24 02:05 639231334732159368
138 ms 209.68.2.181
5 2026-08-24 01:49 639231325035670078
131 ms 209.68.2.181
4 2026-08-24 01:32 639231315132253837
95 ms 209.68.2.181
3 2026-08-24 01:15 639231305014280808
149 ms 209.68.2.181
2 2026-08-24 00:23 639231273779380675
151 ms 209.68.2.181
1 2026-08-24 00:07 639231264180839154
155 ms 209.68.2.181