DNS response history for ns378.pair.com

ns378.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, 29 successful responses, 1 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 ns378.pair.com.
Records on Selected Date

30

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 12:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.4.21

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns378.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:43 639235174453894956
107 ms 209.68.4.21
29 2026-08-28 12:26 639235163898672622
99 ms 209.68.4.21
28 2026-08-28 11:33 639235132147470568
102 ms 209.68.4.21
27 2026-08-28 11:16 639235121907744088
100 ms 209.68.4.21
26 2026-08-28 10:58 639235111428014262
100 ms 209.68.4.21
25 2026-08-28 10:41 639235100921813626
205 ms 209.68.4.21
24 2026-08-28 09:47 639235068670703481
-
23 2026-08-28 09:30 639235058337459445
116 ms 209.68.4.21
22 2026-08-28 09:12 639235047825109146
135 ms 209.68.4.21
21 2026-08-28 08:55 639235037383229033
109 ms 209.68.4.21
20 2026-08-28 08:02 639235005619242711
2131 ms 209.68.4.21
19 2026-08-28 07:45 639234995310346584
109 ms 209.68.4.21
18 2026-08-28 07:28 639234984946548933
98 ms 209.68.4.21
17 2026-08-28 07:10 639234974608077290
2140 ms 209.68.4.21
16 2026-08-28 06:17 639234942529845595
203 ms 209.68.4.21
15 2026-08-28 06:00 639234932259126627
115 ms 209.68.4.21
14 2026-08-28 05:42 639234921916735988
133 ms 209.68.4.21
13 2026-08-28 05:25 639234911470038027
2140 ms 209.68.4.21
12 2026-08-28 04:32 639234879588411654
126 ms 209.68.4.21
11 2026-08-28 04:15 639234869341589104
110 ms 209.68.4.21
10 2026-08-28 03:58 639234859012216675
106 ms 209.68.4.21
9 2026-08-28 03:40 639234848695364934
99 ms 209.68.4.21
8 2026-08-28 02:48 639234816952458162
94 ms 209.68.4.21
7 2026-08-28 02:31 639234806773081598
194 ms 209.68.4.21
6 2026-08-28 02:13 639234796382955255
102 ms 209.68.4.21
5 2026-08-28 01:56 639234786015782563
101 ms 209.68.4.21
4 2026-08-28 01:02 639234753811917646
131 ms 209.68.4.21
3 2026-08-28 00:46 639234743739767811
100 ms 209.68.4.21
2 2026-08-28 00:28 639234733372362811
106 ms 209.68.4.21
1 2026-08-28 00:11 639234723048550337
117 ms 209.68.4.21