DNS response history for ns132.pair.com

ns132.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 176 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 ns132.pair.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

176 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.1.152

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 ns132.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:36 639232576780683689
100 ms 209.68.1.152
35 2026-08-25 12:19 639232566381512620
160 ms 209.68.1.152
34 2026-08-25 12:01 639232556111768563
102 ms 209.68.1.152
33 2026-08-25 11:44 639232545839529039
159 ms 209.68.1.152
32 2026-08-25 11:27 639232535349285207
135 ms 209.68.1.152
31 2026-08-25 11:09 639232524938080723
138 ms 209.68.1.152
30 2026-08-25 10:16 639232492740373468
2196 ms 209.68.1.152
29 2026-08-25 09:59 639232482235303141
135 ms 209.68.1.152
28 2026-08-25 09:41 639232471861770303
112 ms 209.68.1.152
27 2026-08-25 09:24 639232461630217327
128 ms 209.68.1.152
26 2026-08-25 09:07 639232451282965990
144 ms 209.68.1.152
25 2026-08-25 08:49 639232440814614938
100 ms 209.68.1.152
24 2026-08-25 08:32 639232430410720425
102 ms 209.68.1.152
23 2026-08-25 08:15 639232420003096185
117 ms 209.68.1.152
22 2026-08-25 07:57 639232409467287444
99 ms 209.68.1.152
21 2026-08-25 07:40 639232399077195997
106 ms 209.68.1.152
20 2026-08-25 07:22 639232388731528337
136 ms 209.68.1.152
19 2026-08-25 07:05 639232378288598612
103 ms 209.68.1.152
18 2026-08-25 06:11 639232346196373643
114 ms 209.68.1.152
17 2026-08-25 05:55 639232336112370741
106 ms 209.68.1.152
16 2026-08-25 05:38 639232326146508970
99 ms 209.68.1.152
15 2026-08-25 05:21 639232316189381720
100 ms 209.68.1.152
14 2026-08-25 05:05 639232306217998913
103 ms 209.68.1.152
13 2026-08-25 04:48 639232296255744174
133 ms 209.68.1.152
12 2026-08-25 04:31 639232286095760789
135 ms 209.68.1.152
11 2026-08-25 04:14 639232276086186273
96 ms 209.68.1.152
10 2026-08-25 03:58 639232265900986425
98 ms 209.68.1.152
9 2026-08-25 03:41 639232255723518075
99 ms 209.68.1.152
8 2026-08-25 03:24 639232245484452890
157 ms 209.68.1.152
7 2026-08-25 03:06 639232235157175331
99 ms 209.68.1.152
6 2026-08-25 02:13 639232203197189095
101 ms 209.68.1.152
5 2026-08-25 01:56 639232192844564298
140 ms 209.68.1.152
4 2026-08-25 01:39 639232182496008942
183 ms 209.68.1.152
3 2026-08-25 01:21 639232172197053132
103 ms 209.68.1.152
2 2026-08-25 00:28 639232140250307418
99 ms 209.68.1.152
1 2026-08-25 00:11 639232129927860324
101 ms 209.68.1.152