DNS response history for ns1.faircom.com

ns1.faircom.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 37 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 ns1.faircom.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

37 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

208.80.124.159

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 ns1.faircom.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
24 ms 208.80.124.159
29 2026-08-28 12:25 639235163898672622
112 ms 208.80.124.159
28 2026-08-28 11:32 639235132147470568
28 ms 208.80.124.159
27 2026-08-28 11:15 639235121907744088
10 ms 208.80.124.159
26 2026-08-28 10:58 639235111428014262
11 ms 208.80.124.159
25 2026-08-28 10:40 639235100921813626
14 ms 208.80.124.159
24 2026-08-28 09:47 639235068670703481
64 ms 208.80.124.159
23 2026-08-28 09:29 639235058337459445
30 ms 208.80.124.159
22 2026-08-28 09:12 639235047825109146
11 ms 208.80.124.159
21 2026-08-28 08:54 639235037383229033
24 ms 208.80.124.159
20 2026-08-28 08:02 639235005619242711
29 ms 208.80.124.159
19 2026-08-28 07:45 639234995310346584
98 ms 208.80.124.159
18 2026-08-28 07:27 639234984946548933
10 ms 208.80.124.159
17 2026-08-28 07:10 639234974608077290
116 ms 208.80.124.159
16 2026-08-28 06:16 639234942529845595
9 ms 208.80.124.159
15 2026-08-28 05:59 639234932259126627
39 ms 208.80.124.159
14 2026-08-28 05:42 639234921916735988
9 ms 208.80.124.159
13 2026-08-28 05:25 639234911470038027
36 ms 208.80.124.159
12 2026-08-28 04:32 639234879588411654
76 ms 208.80.124.159
11 2026-08-28 04:14 639234869341589104
15 ms 208.80.124.159
10 2026-08-28 03:57 639234859012216675
10 ms 208.80.124.159
9 2026-08-28 03:40 639234848695364934
8 ms 208.80.124.159
8 2026-08-28 02:47 639234816952458162
112 ms 208.80.124.159
7 2026-08-28 02:30 639234806773081598
35 ms 208.80.124.159
6 2026-08-28 02:13 639234796382955255
18 ms 208.80.124.159
5 2026-08-28 01:56 639234786015782563
20 ms 208.80.124.159
4 2026-08-28 01:02 639234753811917646
60 ms 208.80.124.159
3 2026-08-28 00:45 639234743739767811
30 ms 208.80.124.159
2 2026-08-28 00:28 639234733372362811
25 ms 208.80.124.159
1 2026-08-28 00:11 639234723048550337
24 ms 208.80.124.159