DNS response history for ns369.pair.com

ns369.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-31. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 374 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 ns369.pair.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

374 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 10:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.3.220

Most recently resolved hosting IP on selected date

Successful Responses

32

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

Showing DNS history for 2026-08-31 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
32 2026-08-31 10:37 639237690759595513
137 ms 209.68.3.220
31 2026-08-31 10:19 639237680122296836
2136 ms 209.68.3.220
30 2026-08-31 09:25 639237647999458954
103 ms 209.68.3.220
29 2026-08-31 09:08 639237637680951774
110 ms 209.68.3.220
28 2026-08-31 08:51 639237627437728712
103 ms 209.68.3.220
27 2026-08-31 08:34 639237617127808241
104 ms 209.68.3.220
26 2026-08-31 08:17 639237606990101394
2144 ms 209.68.3.220
25 2026-08-31 08:00 639237596595480036
130 ms 209.68.3.220
24 2026-08-31 07:43 639237586261012001
137 ms 209.68.3.220
23 2026-08-31 07:25 639237576047657695
104 ms 209.68.3.220
22 2026-08-31 07:08 639237565832936443
116 ms 209.68.3.220
21 2026-08-31 06:51 639237555466329546
118 ms 209.68.3.220
20 2026-08-31 06:34 639237545032411072
147 ms 209.68.3.220
19 2026-08-31 06:16 639237534469438634
103 ms 209.68.3.220
18 2026-08-31 05:23 639237502279296801
160 ms 209.68.3.220
17 2026-08-31 05:06 639237492362730124
98 ms 209.68.3.220
16 2026-08-31 04:49 639237482311584319
2206 ms 209.68.3.220
15 2026-08-31 04:33 639237472150685594
106 ms 209.68.3.220
14 2026-08-31 04:16 639237462055295430
142 ms 209.68.3.220
13 2026-08-31 03:59 639237452089913890
115 ms 209.68.3.220
12 2026-08-31 03:42 639237441972654103
2133 ms 209.68.3.220
11 2026-08-31 03:25 639237432052396478
134 ms 209.68.3.220
10 2026-08-31 03:09 639237422012990851
138 ms 209.68.3.220
9 2026-08-31 02:52 639237411889602012
133 ms 209.68.3.220
8 2026-08-31 02:35 639237401637354221
176 ms 209.68.3.220
7 2026-08-31 02:18 639237391412690360
98 ms 209.68.3.220
6 2026-08-31 01:25 639237359972957132
136 ms 209.68.3.220
5 2026-08-31 01:09 639237350032183979
117 ms 209.68.3.220
4 2026-08-31 00:52 639237340111452066
99 ms 209.68.3.220
3 2026-08-31 00:36 639237329967272514
98 ms 209.68.3.220
2 2026-08-31 00:19 639237319916508151
104 ms 209.68.3.220
1 2026-08-31 00:02 639237309944877243
98 ms 209.68.3.220