DNS response history for ns139.pair.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

165 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.1.166

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns139.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
36 2026-08-25 12:34 639232576780683689
159 ms 209.68.1.166
35 2026-08-25 12:16 639232566381512620
114 ms 209.68.1.166
34 2026-08-25 11:59 639232556111768563
170 ms 209.68.1.166
33 2026-08-25 11:42 639232545839529039
111 ms 209.68.1.166
32 2026-08-25 11:25 639232535349285207
152 ms 209.68.1.166
31 2026-08-25 11:07 639232524938080723
148 ms 209.68.1.166
30 2026-08-25 10:14 639232492740373468
125 ms 209.68.1.166
29 2026-08-25 09:56 639232482235303141
209 ms 209.68.1.166
28 2026-08-25 09:39 639232471861770303
180 ms 209.68.1.166
27 2026-08-25 09:22 639232461630217327
155 ms 209.68.1.166
26 2026-08-25 09:05 639232451282965990
101 ms 209.68.1.166
25 2026-08-25 08:47 639232440814614938
220 ms 209.68.1.166
24 2026-08-25 08:30 639232430410720425
254 ms 209.68.1.166
23 2026-08-25 08:13 639232420003096185
144 ms 209.68.1.166
22 2026-08-25 07:55 639232409467287444
142 ms 209.68.1.166
21 2026-08-25 07:38 639232399077195997
115 ms 209.68.1.166
20 2026-08-25 07:20 639232388731528337
156 ms 209.68.1.166
19 2026-08-25 07:03 639232378288598612
189 ms 209.68.1.166
18 2026-08-25 06:09 639232346196373643
173 ms 209.68.1.166
17 2026-08-25 05:53 639232336112370741
232 ms 209.68.1.166
16 2026-08-25 05:36 639232326146508970
122 ms 209.68.1.166
15 2026-08-25 05:19 639232316189381720
177 ms 209.68.1.166
14 2026-08-25 05:03 639232306217998913
113 ms 209.68.1.166
13 2026-08-25 04:46 639232296255744174
203 ms 209.68.1.166
12 2026-08-25 04:29 639232286095760789
130 ms 209.68.1.166
11 2026-08-25 04:13 639232276086186273
179 ms 209.68.1.166
10 2026-08-25 03:56 639232265900986425
190 ms 209.68.1.166
9 2026-08-25 03:39 639232255723518075
192 ms 209.68.1.166
8 2026-08-25 03:22 639232245484452890
230 ms 209.68.1.166
7 2026-08-25 03:04 639232235157175331
122 ms 209.68.1.166
6 2026-08-25 02:11 639232203197189095
161 ms 209.68.1.166
5 2026-08-25 01:54 639232192844564298
170 ms 209.68.1.166
4 2026-08-25 01:37 639232182496008942
108 ms 209.68.1.166
3 2026-08-25 01:19 639232172197053132
170 ms 209.68.1.166
2 2026-08-25 00:26 639232140250307418
186 ms 209.68.1.166
1 2026-08-25 00:09 639232129927860324
221 ms 209.68.1.166