DNS response history for ns405.pair.com

ns405.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-28. For this date, NameServerHistory found 40 DNS check records, 40 successful responses, 0 failed responses, and 329 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 ns405.pair.com.
Records on Selected Date

40

Historical checks stored for this nameserver on selected date

Average Latency

329 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 16:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.4.105

Most recently resolved hosting IP on selected date

Successful Responses

40

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 ns405.pair.com

Showing DNS history for 2026-08-28 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
40 2026-08-28 16:47 639235322621629103
218 ms 209.68.4.105
39 2026-08-28 16:30 639235312230592801
131 ms 209.68.4.105
38 2026-08-28 16:13 639235301738139314
108 ms 209.68.4.105
37 2026-08-28 15:55 639235291168160936
140 ms 209.68.4.105
36 2026-08-28 15:01 639235258803654519
99 ms 209.68.4.105
35 2026-08-28 14:44 639235248596087996
96 ms 209.68.4.105
34 2026-08-28 14:27 639235238225955920
144 ms 209.68.4.105
33 2026-08-28 14:09 639235227727862105
2154 ms 209.68.4.105
32 2026-08-28 13:15 639235195230848570
99 ms 209.68.4.105
31 2026-08-28 12:58 639235184840503274
96 ms 209.68.4.105
30 2026-08-28 12:41 639235174453894956
126 ms 209.68.4.105
29 2026-08-28 12:23 639235163898672622
100 ms 209.68.4.105
28 2026-08-28 11:30 639235132147470568
2139 ms 209.68.4.105
27 2026-08-28 11:13 639235121907744088
121 ms 209.68.4.105
26 2026-08-28 10:56 639235111428014262
151 ms 209.68.4.105
25 2026-08-28 10:38 639235100921813626
172 ms 209.68.4.105
24 2026-08-28 09:44 639235068670703481
154 ms 209.68.4.105
23 2026-08-28 09:27 639235058337459445
139 ms 209.68.4.105
22 2026-08-28 09:10 639235047825109146
166 ms 209.68.4.105
21 2026-08-28 08:52 639235037383229033
105 ms 209.68.4.105
20 2026-08-28 07:59 639235005619242711
2137 ms 209.68.4.105
19 2026-08-28 07:42 639234995310346584
2164 ms 209.68.4.105
18 2026-08-28 07:25 639234984946548933
100 ms 209.68.4.105
17 2026-08-28 07:08 639234974608077290
100 ms 209.68.4.105
16 2026-08-28 06:14 639234942529845595
103 ms 209.68.4.105
15 2026-08-28 05:57 639234932259126627
98 ms 209.68.4.105
14 2026-08-28 05:40 639234921916735988
137 ms 209.68.4.105
13 2026-08-28 05:22 639234911470038027
136 ms 209.68.4.105
12 2026-08-28 04:29 639234879588411654
108 ms 209.68.4.105
11 2026-08-28 04:12 639234869341589104
190 ms 209.68.4.105
10 2026-08-28 03:55 639234859012216675
132 ms 209.68.4.105
9 2026-08-28 03:38 639234848695364934
98 ms 209.68.4.105
8 2026-08-28 02:45 639234816952458162
138 ms 209.68.4.105
7 2026-08-28 02:28 639234806773081598
107 ms 209.68.4.105
6 2026-08-28 02:11 639234796382955255
118 ms 209.68.4.105
5 2026-08-28 01:53 639234786015782563
147 ms 209.68.4.105
4 2026-08-28 00:59 639234753811917646
97 ms 209.68.4.105
3 2026-08-28 00:43 639234743739767811
163 ms 209.68.4.105
2 2026-08-28 00:25 639234733372362811
112 ms 209.68.4.105
1 2026-08-28 00:08 639234723048550337
111 ms 209.68.4.105