DNS response history for ns136.pair.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

256 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.1.160

Most recently resolved hosting IP on selected date

Successful Responses

31

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 ns136.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
31 2026-08-27 10:01 639234212558002823
109 ms 209.68.1.160
30 2026-08-27 09:43 639234202117531850
101 ms 209.68.1.160
29 2026-08-27 09:26 639234191649612722
266 ms 209.68.1.160
28 2026-08-27 09:08 639234181105879568
137 ms 209.68.1.160
27 2026-08-27 08:51 639234170713214496
136 ms 209.68.1.160
26 2026-08-27 08:33 639234160341037652
100 ms 209.68.1.160
25 2026-08-27 08:16 639234149799404224
106 ms 209.68.1.160
24 2026-08-27 07:59 639234139553286469
183 ms 209.68.1.160
23 2026-08-27 07:05 639234107183588293
2153 ms 209.68.1.160
22 2026-08-27 06:48 639234096905435724
108 ms 209.68.1.160
21 2026-08-27 06:31 639234086579410775
111 ms 209.68.1.160
20 2026-08-27 06:14 639234076291157956
142 ms 209.68.1.160
19 2026-08-27 05:56 639234065981939454
147 ms 209.68.1.160
18 2026-08-27 05:39 639234055548642997
100 ms 209.68.1.160
17 2026-08-27 05:22 639234045267979603
101 ms 209.68.1.160
16 2026-08-27 05:05 639234034999717463
117 ms 209.68.1.160
15 2026-08-27 04:48 639234024739225358
141 ms 209.68.1.160
14 2026-08-27 04:30 639234014311170162
149 ms 209.68.1.160
13 2026-08-27 04:13 639234003806017640
102 ms 209.68.1.160
12 2026-08-27 03:55 639233993356203030
101 ms 209.68.1.160
11 2026-08-27 03:02 639233961301716608
109 ms 209.68.1.160
10 2026-08-27 02:45 639233950834200647
148 ms 209.68.1.160
9 2026-08-27 02:27 639233940431849026
99 ms 209.68.1.160
8 2026-08-27 02:10 639233930110596398
98 ms 209.68.1.160
7 2026-08-27 01:53 639233919705434540
107 ms 209.68.1.160
6 2026-08-27 01:36 639233909452807845
105 ms 209.68.1.160
5 2026-08-27 01:18 639233899096420820
99 ms 209.68.1.160
4 2026-08-27 01:01 639233888707824939
100 ms 209.68.1.160
3 2026-08-27 00:44 639233878461203802
2133 ms 209.68.1.160
2 2026-08-27 00:27 639233868060868209
206 ms 209.68.1.160
1 2026-08-27 00:09 639233857450922991
133 ms 209.68.1.160