DNS response history for ns526.pair.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

444 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 13:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.5.140

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns526.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
32 2026-08-28 13:17 639235195230848570
2254 ms 209.68.5.140
31 2026-08-28 13:00 639235184840503274
202 ms 209.68.5.140
30 2026-08-28 12:43 639235174453894956
176 ms 209.68.5.140
29 2026-08-28 12:25 639235163898672622
101 ms 209.68.5.140
28 2026-08-28 11:32 639235132147470568
2139 ms 209.68.5.140
27 2026-08-28 11:15 639235121907744088
101 ms 209.68.5.140
26 2026-08-28 10:58 639235111428014262
106 ms 209.68.5.140
25 2026-08-28 10:40 639235100921813626
105 ms 209.68.5.140
24 2026-08-28 09:47 639235068670703481
112 ms 209.68.5.140
23 2026-08-28 09:29 639235058337459445
98 ms 209.68.5.140
22 2026-08-28 09:12 639235047825109146
161 ms 209.68.5.140
21 2026-08-28 08:54 639235037383229033
102 ms 209.68.5.140
20 2026-08-28 08:01 639235005619242711
94 ms 209.68.5.140
19 2026-08-28 07:44 639234995310346584
152 ms 209.68.5.140
18 2026-08-28 07:27 639234984946548933
102 ms 209.68.5.140
17 2026-08-28 07:10 639234974608077290
99 ms 209.68.5.140
16 2026-08-28 06:16 639234942529845595
108 ms 209.68.5.140
15 2026-08-28 05:59 639234932259126627
99 ms 209.68.5.140
14 2026-08-28 05:42 639234921916735988
147 ms 209.68.5.140
13 2026-08-28 05:25 639234911470038027
98 ms 209.68.5.140
12 2026-08-28 04:31 639234879588411654
2195 ms 209.68.5.140
11 2026-08-28 04:14 639234869341589104
111 ms 209.68.5.140
10 2026-08-28 03:57 639234859012216675
188 ms 209.68.5.140
9 2026-08-28 03:40 639234848695364934
103 ms 209.68.5.140
8 2026-08-28 02:47 639234816952458162
136 ms 209.68.5.140
7 2026-08-28 02:30 639234806773081598
115 ms 209.68.5.140
6 2026-08-28 02:13 639234796382955255
147 ms 209.68.5.140
5 2026-08-28 01:55 639234786015782563
2135 ms 209.68.5.140
4 2026-08-28 01:02 639234753811917646
116 ms 209.68.5.140
3 2026-08-28 00:45 639234743739767811
98 ms 209.68.5.140
2 2026-08-28 00:28 639234733372362811
2154 ms 209.68.5.140
1 2026-08-28 00:10 639234723048550337
143 ms 209.68.5.140