DNS response history for ns394.pair.com

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

39

Historical checks stored for this nameserver on selected date

Average Latency

270 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 16:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.4.64

Most recently resolved hosting IP on selected date

Successful Responses

39

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 ns394.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
39 2026-08-28 16:33 639235312230592801
95 ms 209.68.4.64
38 2026-08-28 16:16 639235301738139314
2104 ms 209.68.4.64
37 2026-08-28 15:58 639235291168160936
120 ms 209.68.4.64
36 2026-08-28 15:04 639235258803654519
157 ms 209.68.4.64
35 2026-08-28 14:47 639235248596087996
100 ms 209.68.4.64
34 2026-08-28 14:29 639235238225955920
101 ms 209.68.4.64
33 2026-08-28 14:12 639235227727862105
102 ms 209.68.4.64
32 2026-08-28 13:18 639235195230848570
131 ms 209.68.4.64
31 2026-08-28 13:01 639235184840503274
100 ms 209.68.4.64
30 2026-08-28 12:43 639235174453894956
110 ms 209.68.4.64
29 2026-08-28 12:26 639235163898672622
112 ms 209.68.4.64
28 2026-08-28 11:33 639235132147470568
106 ms 209.68.4.64
27 2026-08-28 11:16 639235121907744088
102 ms 209.68.4.64
26 2026-08-28 10:58 639235111428014262
2108 ms 209.68.4.64
25 2026-08-28 10:41 639235100921813626
109 ms 209.68.4.64
24 2026-08-28 09:47 639235068670703481
101 ms 209.68.4.64
23 2026-08-28 09:30 639235058337459445
117 ms 209.68.4.64
22 2026-08-28 09:12 639235047825109146
152 ms 209.68.4.64
21 2026-08-28 08:55 639235037383229033
109 ms 209.68.4.64
20 2026-08-28 08:02 639235005619242711
132 ms 209.68.4.64
19 2026-08-28 07:45 639234995310346584
101 ms 209.68.4.64
18 2026-08-28 07:28 639234984946548933
112 ms 209.68.4.64
17 2026-08-28 07:10 639234974608077290
121 ms 209.68.4.64
16 2026-08-28 06:17 639234942529845595
106 ms 209.68.4.64
15 2026-08-28 06:00 639234932259126627
102 ms 209.68.4.64
14 2026-08-28 05:42 639234921916735988
136 ms 209.68.4.64
13 2026-08-28 05:25 639234911470038027
139 ms 209.68.4.64
12 2026-08-28 04:32 639234879588411654
152 ms 209.68.4.64
11 2026-08-28 04:15 639234869341589104
137 ms 209.68.4.64
10 2026-08-28 03:58 639234859012216675
100 ms 209.68.4.64
9 2026-08-28 03:40 639234848695364934
96 ms 209.68.4.64
8 2026-08-28 02:48 639234816952458162
181 ms 209.68.4.64
7 2026-08-28 02:31 639234806773081598
94 ms 209.68.4.64
6 2026-08-28 02:13 639234796382955255
2131 ms 209.68.4.64
5 2026-08-28 01:56 639234786015782563
114 ms 209.68.4.64
4 2026-08-28 01:02 639234753811917646
117 ms 209.68.4.64
3 2026-08-28 00:45 639234743739767811
98 ms 209.68.4.64
2 2026-08-28 00:28 639234733372362811
106 ms 209.68.4.64
1 2026-08-28 00:11 639234723048550337
127 ms 209.68.4.64