DNS response history for ns343.pair.com

ns343.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 229 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 ns343.pair.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

229 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.2.188

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 ns343.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:06 639235258803654519
98 ms 209.68.2.188
35 2026-08-28 14:49 639235248596087996
326 ms 209.68.2.188
34 2026-08-28 14:32 639235238225955920
102 ms 209.68.2.188
33 2026-08-28 14:14 639235227727862105
102 ms 209.68.2.188
32 2026-08-28 13:20 639235195230848570
103 ms 209.68.2.188
31 2026-08-28 13:03 639235184840503274
2101 ms 209.68.2.188
30 2026-08-28 12:45 639235174453894956
2131 ms 209.68.2.188
29 2026-08-28 12:28 639235163898672622
105 ms 209.68.2.188
28 2026-08-28 11:35 639235132147470568
101 ms 209.68.2.188
27 2026-08-28 11:18 639235121907744088
109 ms 209.68.2.188
26 2026-08-28 11:01 639235111428014262
139 ms 209.68.2.188
25 2026-08-28 10:43 639235100921813626
112 ms 209.68.2.188
24 2026-08-28 09:49 639235068670703481
128 ms 209.68.2.188
23 2026-08-28 09:32 639235058337459445
131 ms 209.68.2.188
22 2026-08-28 09:15 639235047825109146
100 ms 209.68.2.188
21 2026-08-28 08:57 639235037383229033
101 ms 209.68.2.188
20 2026-08-28 08:04 639235005619242711
107 ms 209.68.2.188
19 2026-08-28 07:47 639234995310346584
99 ms 209.68.2.188
18 2026-08-28 07:30 639234984946548933
102 ms 209.68.2.188
17 2026-08-28 07:12 639234974608077290
99 ms 209.68.2.188
16 2026-08-28 06:19 639234942529845595
100 ms 209.68.2.188
15 2026-08-28 06:02 639234932259126627
104 ms 209.68.2.188
14 2026-08-28 05:45 639234921916735988
98 ms 209.68.2.188
13 2026-08-28 05:27 639234911470038027
98 ms 209.68.2.188
12 2026-08-28 04:34 639234879588411654
138 ms 209.68.2.188
11 2026-08-28 04:17 639234869341589104
106 ms 209.68.2.188
10 2026-08-28 04:00 639234859012216675
109 ms 209.68.2.188
9 2026-08-28 03:42 639234848695364934
116 ms 209.68.2.188
8 2026-08-28 02:50 639234816952458162
95 ms 209.68.2.188
7 2026-08-28 02:33 639234806773081598
108 ms 209.68.2.188
6 2026-08-28 02:15 639234796382955255
128 ms 209.68.2.188
5 2026-08-28 01:58 639234786015782563
142 ms 209.68.2.188
4 2026-08-28 01:04 639234753811917646
99 ms 209.68.2.188
3 2026-08-28 00:48 639234743739767811
109 ms 209.68.2.188
2 2026-08-28 00:30 639234733372362811
136 ms 209.68.2.188
1 2026-08-28 00:13 639234723048550337
160 ms 209.68.2.188