DNS response history for ns1.tricentury.bank

ns1.tricentury.bank 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 26 DNS check records, 26 successful responses, 0 failed responses, and 420 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.tricentury.bank.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

420 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.24.202

Most recently resolved hosting IP on selected date

Successful Responses

26

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.tricentury.bank

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
26 2026-08-27 08:31 639234160341037652
57 ms 162.159.24.202
25 2026-08-27 08:14 639234149799404224
51 ms 162.159.24.202
24 2026-08-27 07:57 639234139553286469
21 ms 162.159.24.202
23 2026-08-27 07:03 639234107183588293
2009 ms 162.159.24.202
22 2026-08-27 06:45 639234096905435724
32 ms 162.159.24.202
21 2026-08-27 06:28 639234086579410775
70 ms 162.159.24.202
20 2026-08-27 06:11 639234076291157956
20 ms 162.159.24.202
19 2026-08-27 05:54 639234065981939454
5 ms 162.159.24.202
18 2026-08-27 05:37 639234055548642997
2009 ms 162.159.24.202
17 2026-08-27 05:19 639234045267979603
18 ms 162.159.24.202
16 2026-08-27 05:02 639234034999717463
59 ms 162.159.24.202
15 2026-08-27 04:45 639234024739225358
14 ms 162.159.24.202
14 2026-08-27 04:28 639234014311170162
11 ms 162.159.24.202
13 2026-08-27 04:10 639234003806017640
45 ms 162.159.24.202
12 2026-08-27 03:53 639233993356203030
7 ms 162.159.24.202
11 2026-08-27 03:00 639233961301716608
109 ms 162.159.24.202
10 2026-08-27 02:42 639233950834200647
11 ms 162.159.24.202
9 2026-08-27 02:25 639233940431849026
2077 ms 162.159.24.202
8 2026-08-27 02:08 639233930110596398
68 ms 162.159.24.202
7 2026-08-27 01:50 639233919705434540
28 ms 162.159.24.202
6 2026-08-27 01:33 639233909452807845
2079 ms 162.159.24.202
5 2026-08-27 01:16 639233899096420820
2072 ms 162.159.24.202
4 2026-08-27 00:59 639233888707824939
14 ms 162.159.24.202
3 2026-08-27 00:41 639233878461203802
19 ms 162.159.24.202
2 2026-08-27 00:24 639233868060868209
11 ms 162.159.24.202
1 2026-08-27 00:06 639233857450922991
13 ms 162.159.24.202