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-25. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 324 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

324 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:08

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-25 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-25 11:08 639232524938080723
149 ms 209.68.1.160
30 2026-08-25 10:14 639232492740373468
109 ms 209.68.1.160
29 2026-08-25 09:57 639232482235303141
129 ms 209.68.1.160
28 2026-08-25 09:39 639232471861770303
104 ms 209.68.1.160
27 2026-08-25 09:22 639232461630217327
115 ms 209.68.1.160
26 2026-08-25 09:05 639232451282965990
128 ms 209.68.1.160
25 2026-08-25 08:48 639232440814614938
207 ms 209.68.1.160
24 2026-08-25 08:31 639232430410720425
149 ms 209.68.1.160
23 2026-08-25 08:13 639232420003096185
103 ms 209.68.1.160
22 2026-08-25 07:56 639232409467287444
124 ms 209.68.1.160
21 2026-08-25 07:38 639232399077195997
146 ms 209.68.1.160
20 2026-08-25 07:21 639232388731528337
115 ms 209.68.1.160
19 2026-08-25 07:04 639232378288598612
227 ms 209.68.1.160
18 2026-08-25 06:10 639232346196373643
99 ms 209.68.1.160
17 2026-08-25 05:53 639232336112370741
132 ms 209.68.1.160
16 2026-08-25 05:37 639232326146508970
135 ms 209.68.1.160
15 2026-08-25 05:20 639232316189381720
105 ms 209.68.1.160
14 2026-08-25 05:04 639232306217998913
136 ms 209.68.1.160
13 2026-08-25 04:47 639232296255744174
151 ms 209.68.1.160
12 2026-08-25 04:30 639232286095760789
101 ms 209.68.1.160
11 2026-08-25 04:13 639232276086186273
108 ms 209.68.1.160
10 2026-08-25 03:56 639232265900986425
109 ms 209.68.1.160
9 2026-08-25 03:39 639232255723518075
2191 ms 209.68.1.160
8 2026-08-25 03:22 639232245484452890
100 ms 209.68.1.160
7 2026-08-25 03:05 639232235157175331
97 ms 209.68.1.160
6 2026-08-25 02:12 639232203197189095
99 ms 209.68.1.160
5 2026-08-25 01:55 639232192844564298
185 ms 209.68.1.160
4 2026-08-25 01:37 639232182496008942
155 ms 209.68.1.160
3 2026-08-25 01:20 639232172197053132
4105 ms 209.68.1.160
2 2026-08-25 00:27 639232140250307418
133 ms 209.68.1.160
1 2026-08-25 00:10 639232129927860324
100 ms 209.68.1.160