DNS response history for ns244.pair.com

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

25

Historical checks stored for this nameserver on selected date

Average Latency

135 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 10:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.68.2.89

Most recently resolved hosting IP on selected date

Successful Responses

25

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 ns244.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
25 2026-08-28 10:41 639235100921813626
150 ms 209.68.2.89
24 2026-08-28 09:47 639235068670703481
159 ms 209.68.2.89
23 2026-08-28 09:30 639235058337459445
100 ms 209.68.2.89
22 2026-08-28 09:12 639235047825109146
133 ms 209.68.2.89
21 2026-08-28 08:55 639235037383229033
122 ms 209.68.2.89
20 2026-08-28 08:02 639235005619242711
152 ms 209.68.2.89
19 2026-08-28 07:45 639234995310346584
110 ms 209.68.2.89
18 2026-08-28 07:28 639234984946548933
207 ms 209.68.2.89
17 2026-08-28 07:10 639234974608077290
115 ms 209.68.2.89
16 2026-08-28 06:17 639234942529845595
132 ms 209.68.2.89
15 2026-08-28 06:00 639234932259126627
99 ms 209.68.2.89
14 2026-08-28 05:42 639234921916735988
265 ms 209.68.2.89
13 2026-08-28 05:25 639234911470038027
134 ms 209.68.2.89
12 2026-08-28 04:32 639234879588411654
175 ms 209.68.2.89
11 2026-08-28 04:15 639234869341589104
203 ms 209.68.2.89
10 2026-08-28 03:58 639234859012216675
109 ms 209.68.2.89
9 2026-08-28 03:40 639234848695364934
99 ms 209.68.2.89
8 2026-08-28 02:48 639234816952458162
146 ms 209.68.2.89
7 2026-08-28 02:31 639234806773081598
97 ms 209.68.2.89
6 2026-08-28 02:13 639234796382955255
133 ms 209.68.2.89
5 2026-08-28 01:56 639234786015782563
107 ms 209.68.2.89
4 2026-08-28 01:02 639234753811917646
119 ms 209.68.2.89
3 2026-08-28 00:45 639234743739767811
94 ms 209.68.2.89
2 2026-08-28 00:28 639234733372362811
112 ms 209.68.2.89
1 2026-08-28 00:11 639234723048550337
95 ms 209.68.2.89