DNS response history for ns1.seenly.ai

ns1.seenly.ai 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-24. For this date, NameServerHistory found 34 DNS check records, 33 successful responses, 1 failed responses, and 366 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.seenly.ai.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

366 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

176.126.172.228

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.seenly.ai

Showing DNS history for 2026-08-24 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
34 2026-08-24 14:00 639231765923559455
28 ms 176.126.172.228
33 2026-08-24 13:43 639231755868832964
147 ms 176.126.172.228
32 2026-08-24 13:26 639231745628278877
52 ms 176.126.172.228
31 2026-08-24 13:09 639231735407682062
52 ms 176.126.172.228
30 2026-08-24 12:17 639231703815441688
4046 ms 176.126.172.228
29 2026-08-24 12:00 639231693747052549
-
28 2026-08-24 11:43 639231683712487276
72 ms 176.126.172.228
27 2026-08-24 11:26 639231673513573868
30 ms 176.126.172.228
26 2026-08-24 10:33 639231641791249939
43 ms 176.126.172.228
25 2026-08-24 10:17 639231631866211033
37 ms 176.126.172.228
24 2026-08-24 10:00 639231621644955316
54 ms 176.126.172.228
23 2026-08-24 09:43 639231611478799259
37 ms 176.126.172.228
22 2026-08-24 08:50 639231579923718211
115 ms 176.126.172.228
21 2026-08-24 08:33 639231569810702936
71 ms 176.126.172.228
20 2026-08-24 08:16 639231559762411619
302 ms 176.126.172.228
19 2026-08-24 08:00 639231549663595407
39 ms 176.126.172.228
18 2026-08-24 07:07 639231518076817246
33 ms 176.126.172.228
17 2026-08-24 06:51 639231508078650885
60 ms 176.126.172.228
16 2026-08-24 06:34 639231498210697093
53 ms 176.126.172.228
15 2026-08-24 06:17 639231488109699360
65 ms 176.126.172.228
14 2026-08-24 05:25 639231456772510692
29 ms 176.126.172.228
13 2026-08-24 05:09 639231447084631185
8 ms 176.126.172.228
12 2026-08-24 04:52 639231437208519473
31 ms 176.126.172.228
11 2026-08-24 04:36 639231427209627490
29 ms 176.126.172.228
10 2026-08-24 03:43 639231395791246644
37 ms 176.126.172.228
9 2026-08-24 03:27 639231386075551458
2042 ms 176.126.172.228
8 2026-08-24 03:11 639231376208713791
27 ms 176.126.172.228
7 2026-08-24 02:54 639231366170589276
35 ms 176.126.172.228
6 2026-08-24 02:02 639231334732159368
51 ms 176.126.172.228
5 2026-08-24 01:45 639231325035670078
2274 ms 176.126.172.228
4 2026-08-24 01:29 639231315132253837
25 ms 176.126.172.228
3 2026-08-24 01:12 639231305014280808
27 ms 176.126.172.228
2 2026-08-24 00:20 639231273779380675
98 ms 176.126.172.228
1 2026-08-24 00:04 639231264180839154
2032 ms 176.126.172.228