DNS response history for ns560.pair.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

384 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.39.47.139

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 ns560.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
36 2026-08-28 15:09 639235258803654519
200 ms 66.39.47.139
35 2026-08-28 14:51 639235248596087996
480 ms 66.39.47.139
34 2026-08-28 14:34 639235238225955920
229 ms 66.39.47.139
33 2026-08-28 14:17 639235227727862105
196 ms 66.39.47.139
32 2026-08-28 13:22 639235195230848570
194 ms 66.39.47.139
31 2026-08-28 13:05 639235184840503274
183 ms 66.39.47.139
30 2026-08-28 12:48 639235174453894956
195 ms 66.39.47.139
29 2026-08-28 12:30 639235163898672622
191 ms 66.39.47.139
28 2026-08-28 11:37 639235132147470568
193 ms 66.39.47.139
27 2026-08-28 11:20 639235121907744088
249 ms 66.39.47.139
26 2026-08-28 11:03 639235111428014262
211 ms 66.39.47.139
25 2026-08-28 10:45 639235100921813626
2187 ms 66.39.47.139
24 2026-08-28 09:51 639235068670703481
193 ms 66.39.47.139
23 2026-08-28 09:34 639235058337459445
194 ms 66.39.47.139
22 2026-08-28 09:17 639235047825109146
207 ms 66.39.47.139
21 2026-08-28 08:59 639235037383229033
196 ms 66.39.47.139
20 2026-08-28 08:06 639235005619242711
195 ms 66.39.47.139
19 2026-08-28 07:49 639234995310346584
193 ms 66.39.47.139
18 2026-08-28 07:32 639234984946548933
194 ms 66.39.47.139
17 2026-08-28 07:15 639234974608077290
133 ms 66.39.47.139
16 2026-08-28 06:21 639234942529845595
196 ms 66.39.47.139
15 2026-08-28 06:04 639234932259126627
195 ms 66.39.47.139
14 2026-08-28 05:47 639234921916735988
194 ms 66.39.47.139
13 2026-08-28 05:30 639234911470038027
196 ms 66.39.47.139
12 2026-08-28 04:36 639234879588411654
193 ms 66.39.47.139
11 2026-08-28 04:19 639234869341589104
202 ms 66.39.47.139
10 2026-08-28 04:02 639234859012216675
459 ms 66.39.47.139
9 2026-08-28 03:45 639234848695364934
194 ms 66.39.47.139
8 2026-08-28 02:52 639234816952458162
193 ms 66.39.47.139
7 2026-08-28 02:35 639234806773081598
2218 ms 66.39.47.139
6 2026-08-28 02:18 639234796382955255
189 ms 66.39.47.139
5 2026-08-28 02:00 639234786015782563
2267 ms 66.39.47.139
4 2026-08-28 01:07 639234753811917646
193 ms 66.39.47.139
3 2026-08-28 00:50 639234743739767811
226 ms 66.39.47.139
2 2026-08-28 00:33 639234733372362811
314 ms 66.39.47.139
1 2026-08-28 00:15 639234723048550337
196 ms 66.39.47.139