DNS response history for ns138.pair.com

ns138.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 114 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 ns138.pair.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

114 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.1.164

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 ns138.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:10 639232524938080723
100 ms 209.68.1.164
30 2026-08-25 10:16 639232492740373468
103 ms 209.68.1.164
29 2026-08-25 09:59 639232482235303141
137 ms 209.68.1.164
28 2026-08-25 09:42 639232471861770303
99 ms 209.68.1.164
27 2026-08-25 09:25 639232461630217327
96 ms 209.68.1.164
26 2026-08-25 09:07 639232451282965990
100 ms 209.68.1.164
25 2026-08-25 08:50 639232440814614938
118 ms 209.68.1.164
24 2026-08-25 08:33 639232430410720425
103 ms 209.68.1.164
23 2026-08-25 08:15 639232420003096185
102 ms 209.68.1.164
22 2026-08-25 07:58 639232409467287444
99 ms 209.68.1.164
21 2026-08-25 07:40 639232399077195997
102 ms 209.68.1.164
20 2026-08-25 07:23 639232388731528337
104 ms 209.68.1.164
19 2026-08-25 07:06 639232378288598612
225 ms 209.68.1.164
18 2026-08-25 06:12 639232346196373643
99 ms 209.68.1.164
17 2026-08-25 05:55 639232336112370741
138 ms 209.68.1.164
16 2026-08-25 05:39 639232326146508970
144 ms 209.68.1.164
15 2026-08-25 05:22 639232316189381720
100 ms 209.68.1.164
14 2026-08-25 05:06 639232306217998913
99 ms 209.68.1.164
13 2026-08-25 04:49 639232296255744174
156 ms 209.68.1.164
12 2026-08-25 04:32 639232286095760789
141 ms 209.68.1.164
11 2026-08-25 04:15 639232276086186273
102 ms 209.68.1.164
10 2026-08-25 03:59 639232265900986425
183 ms 209.68.1.164
9 2026-08-25 03:42 639232255723518075
99 ms 209.68.1.164
8 2026-08-25 03:24 639232245484452890
95 ms 209.68.1.164
7 2026-08-25 03:07 639232235157175331
99 ms 209.68.1.164
6 2026-08-25 02:14 639232203197189095
99 ms 209.68.1.164
5 2026-08-25 01:57 639232192844564298
99 ms 209.68.1.164
4 2026-08-25 01:39 639232182496008942
101 ms 209.68.1.164
3 2026-08-25 01:22 639232172197053132
100 ms 209.68.1.164
2 2026-08-25 00:29 639232140250307418
94 ms 209.68.1.164
1 2026-08-25 00:12 639232129927860324
103 ms 209.68.1.164