DNS response history for ns398.pair.com

ns398.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-27. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 371 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 ns398.pair.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

371 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.4.85

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

Showing DNS history for 2026-08-27 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-27 12:41 639234307007468133
2105 ms 209.68.4.85
37 2026-08-27 12:23 639234296664302575
101 ms 209.68.4.85
36 2026-08-27 12:06 639234286253196126
108 ms 209.68.4.85
35 2026-08-27 11:12 639234253963286387
99 ms 209.68.4.85
34 2026-08-27 10:55 639234243654907465
138 ms 209.68.4.85
33 2026-08-27 10:38 639234233269654413
105 ms 209.68.4.85
32 2026-08-27 10:20 639234222943951923
98 ms 209.68.4.85
31 2026-08-27 10:03 639234212558002823
98 ms 209.68.4.85
30 2026-08-27 09:46 639234202117531850
99 ms 209.68.4.85
29 2026-08-27 09:28 639234191649612722
138 ms 209.68.4.85
28 2026-08-27 09:11 639234181105879568
102 ms 209.68.4.85
27 2026-08-27 08:53 639234170713214496
111 ms 209.68.4.85
26 2026-08-27 08:36 639234160341037652
98 ms 209.68.4.85
25 2026-08-27 08:19 639234149799404224
130 ms 209.68.4.85
24 2026-08-27 08:01 639234139553286469
100 ms 209.68.4.85
23 2026-08-27 07:08 639234107183588293
2099 ms 209.68.4.85
22 2026-08-27 06:50 639234096905435724
98 ms 209.68.4.85
21 2026-08-27 06:33 639234086579410775
103 ms 209.68.4.85
20 2026-08-27 06:16 639234076291157956
99 ms 209.68.4.85
19 2026-08-27 05:59 639234065981939454
98 ms 209.68.4.85
18 2026-08-27 05:42 639234055548642997
98 ms 209.68.4.85
17 2026-08-27 05:24 639234045267979603
100 ms 209.68.4.85
16 2026-08-27 05:07 639234034999717463
149 ms 209.68.4.85
15 2026-08-27 04:50 639234024739225358
2141 ms 209.68.4.85
14 2026-08-27 04:33 639234014311170162
101 ms 209.68.4.85
13 2026-08-27 04:15 639234003806017640
101 ms 209.68.4.85
12 2026-08-27 03:58 639233993356203030
142 ms 209.68.4.85
11 2026-08-27 03:05 639233961301716608
98 ms 209.68.4.85
10 2026-08-27 02:47 639233950834200647
146 ms 209.68.4.85
9 2026-08-27 02:30 639233940431849026
98 ms 209.68.4.85
8 2026-08-27 02:13 639233930110596398
99 ms 209.68.4.85
7 2026-08-27 01:55 639233919705434540
108 ms 209.68.4.85
6 2026-08-27 01:38 639233909452807845
98 ms 209.68.4.85
5 2026-08-27 01:21 639233899096420820
98 ms 209.68.4.85
4 2026-08-27 01:04 639233888707824939
2099 ms 209.68.4.85
3 2026-08-27 00:46 639233878461203802
2100 ms 209.68.4.85
2 2026-08-27 00:29 639233868060868209
99 ms 209.68.4.85
1 2026-08-27 00:12 639233857450922991
112 ms 209.68.4.85