DNS response history for ns376.pair.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

451 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.3.252

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns376.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
30 2026-08-28 12:45 639235174453894956
144 ms 209.68.3.252
29 2026-08-28 12:28 639235163898672622
105 ms 209.68.3.252
28 2026-08-28 11:35 639235132147470568
101 ms 209.68.3.252
27 2026-08-28 11:18 639235121907744088
96 ms 209.68.3.252
26 2026-08-28 11:01 639235111428014262
101 ms 209.68.3.252
25 2026-08-28 10:43 639235100921813626
2254 ms 209.68.3.252
24 2026-08-28 09:49 639235068670703481
99 ms 209.68.3.252
23 2026-08-28 09:32 639235058337459445
161 ms 209.68.3.252
22 2026-08-28 09:15 639235047825109146
102 ms 209.68.3.252
21 2026-08-28 08:57 639235037383229033
99 ms 209.68.3.252
20 2026-08-28 08:04 639235005619242711
4138 ms 209.68.3.252
19 2026-08-28 07:47 639234995310346584
99 ms 209.68.3.252
18 2026-08-28 07:30 639234984946548933
142 ms 209.68.3.252
17 2026-08-28 07:12 639234974608077290
100 ms 209.68.3.252
16 2026-08-28 06:19 639234942529845595
95 ms 209.68.3.252
15 2026-08-28 06:02 639234932259126627
106 ms 209.68.3.252
14 2026-08-28 05:45 639234921916735988
158 ms 209.68.3.252
13 2026-08-28 05:27 639234911470038027
102 ms 209.68.3.252
12 2026-08-28 04:34 639234879588411654
140 ms 209.68.3.252
11 2026-08-28 04:17 639234869341589104
97 ms 209.68.3.252
10 2026-08-28 04:00 639234859012216675
132 ms 209.68.3.252
9 2026-08-28 03:42 639234848695364934
2102 ms 209.68.3.252
8 2026-08-28 02:50 639234816952458162
99 ms 209.68.3.252
7 2026-08-28 02:33 639234806773081598
100 ms 209.68.3.252
6 2026-08-28 02:15 639234796382955255
2095 ms 209.68.3.252
5 2026-08-28 01:58 639234786015782563
151 ms 209.68.3.252
4 2026-08-28 01:04 639234753811917646
98 ms 209.68.3.252
3 2026-08-28 00:48 639234743739767811
100 ms 209.68.3.252
2 2026-08-28 00:30 639234733372362811
99 ms 209.68.3.252
1 2026-08-28 00:13 639234723048550337
124 ms 209.68.3.252