DNS response history for ns1.inarea51.com

ns1.inarea51.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-27. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 199 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.inarea51.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

199 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.86.79.161

Most recently resolved hosting IP on selected date

Successful Responses

28

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.inarea51.com

Showing DNS history for 2026-08-27 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
28 2026-08-27 09:02 639234181105879568
53 ms 167.86.79.161
27 2026-08-27 08:45 639234170713214496
42 ms 167.86.79.161
26 2026-08-27 08:28 639234160341037652
38 ms 167.86.79.161
25 2026-08-27 08:10 639234149799404224
288 ms 167.86.79.161
24 2026-08-27 07:53 639234139553286469
46 ms 167.86.79.161
23 2026-08-27 06:59 639234107183588293
36 ms 167.86.79.161
22 2026-08-27 06:42 639234096905435724
79 ms 167.86.79.161
21 2026-08-27 06:25 639234086579410775
33 ms 167.86.79.161
20 2026-08-27 06:08 639234076291157956
47 ms 167.86.79.161
19 2026-08-27 05:51 639234065981939454
65 ms 167.86.79.161
18 2026-08-27 05:33 639234055548642997
36 ms 167.86.79.161
17 2026-08-27 05:16 639234045267979603
72 ms 167.86.79.161
16 2026-08-27 04:59 639234034999717463
45 ms 167.86.79.161
15 2026-08-27 04:42 639234024739225358
57 ms 167.86.79.161
14 2026-08-27 04:24 639234014311170162
55 ms 167.86.79.161
13 2026-08-27 04:07 639234003806017640
39 ms 167.86.79.161
12 2026-08-27 03:49 639233993356203030
50 ms 167.86.79.161
11 2026-08-27 02:56 639233961301716608
63 ms 167.86.79.161
10 2026-08-27 02:39 639233950834200647
40 ms 167.86.79.161
9 2026-08-27 02:21 639233940431849026
37 ms 167.86.79.161
8 2026-08-27 02:04 639233930110596398
2019 ms 167.86.79.161
7 2026-08-27 01:47 639233919705434540
37 ms 167.86.79.161
6 2026-08-27 01:30 639233909452807845
42 ms 167.86.79.161
5 2026-08-27 01:12 639233899096420820
2058 ms 167.86.79.161
4 2026-08-27 00:55 639233888707824939
52 ms 167.86.79.161
3 2026-08-27 00:38 639233878461203802
30 ms 167.86.79.161
2 2026-08-27 00:21 639233868060868209
74 ms 167.86.79.161
1 2026-08-27 00:03 639233857450922991
42 ms 167.86.79.161