DNS response history for ns30.pair.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

245 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 11:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.1.69

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

Showing DNS history for 2026-08-29 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-29 11:20 639235987487833458
156 ms 209.68.1.69
31 2026-08-29 11:03 639235977211002296
101 ms 209.68.1.69
30 2026-08-29 10:45 639235966864596836
98 ms 209.68.1.69
29 2026-08-29 10:28 639235956590882003
2099 ms 209.68.1.69
28 2026-08-29 09:35 639235924465736791
137 ms 209.68.1.69
27 2026-08-29 09:18 639235914430611197
115 ms 209.68.1.69
26 2026-08-29 09:01 639235904343784853
102 ms 209.68.1.69
25 2026-08-29 08:44 639235894201078068
144 ms 209.68.1.69
24 2026-08-29 08:27 639235884233447452
2103 ms 209.68.1.69
23 2026-08-29 08:11 639235874142207309
105 ms 209.68.1.69
22 2026-08-29 07:54 639235863974652466
98 ms 209.68.1.69
21 2026-08-29 07:37 639235853716243436
99 ms 209.68.1.69
20 2026-08-29 07:20 639235843614494759
98 ms 209.68.1.69
19 2026-08-29 07:03 639235833401459551
106 ms 209.68.1.69
18 2026-08-29 06:46 639235823220464528
100 ms 209.68.1.69
17 2026-08-29 06:29 639235812997510905
99 ms 209.68.1.69
16 2026-08-29 05:35 639235781101962521
128 ms 209.68.1.69
15 2026-08-29 05:19 639235771207673260
98 ms 209.68.1.69
14 2026-08-29 05:02 639235761047429642
98 ms 209.68.1.69
13 2026-08-29 04:45 639235750964347246
99 ms 209.68.1.69
12 2026-08-29 04:29 639235740923490874
200 ms 209.68.1.69
11 2026-08-29 04:12 639235730842894399
121 ms 209.68.1.69
10 2026-08-29 03:55 639235720760084717
149 ms 209.68.1.69
9 2026-08-29 03:38 639235710843666743
99 ms 209.68.1.69
8 2026-08-29 03:22 639235700733510561
100 ms 209.68.1.69
7 2026-08-29 03:05 639235690509906192
94 ms 209.68.1.69
6 2026-08-29 02:47 639235680156673501
139 ms 209.68.1.69
5 2026-08-29 02:30 639235669720606443
102 ms 209.68.1.69
4 2026-08-29 01:36 639235637451417084
97 ms 209.68.1.69
3 2026-08-29 01:19 639235627307383453
133 ms 209.68.1.69
2 2026-08-29 01:02 639235616906386856
185 ms 209.68.1.69
1 2026-08-29 00:45 639235606582912691
225 ms 209.68.1.69