DNS response history for ns1.seehowcan.com

ns1.seehowcan.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-24. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 337 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.seehowcan.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

337 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.191.209.155

Most recently resolved hosting IP on selected date

Successful Responses

38

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

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
38 2026-08-24 15:51 639231828211839931
12 ms 103.191.209.155
37 2026-08-24 15:34 639231818080917481
181 ms 103.191.209.155
36 2026-08-24 15:17 639231807961539652
291 ms 103.191.209.155
35 2026-08-24 15:00 639231797631669865
291 ms 103.191.209.155
34 2026-08-24 14:07 639231765923559455
292 ms 103.191.209.155
33 2026-08-24 13:50 639231755868832964
290 ms 103.191.209.155
32 2026-08-24 13:33 639231745628278877
306 ms 103.191.209.155
31 2026-08-24 13:16 639231735407682062
182 ms 103.191.209.155
30 2026-08-24 12:23 639231703815441688
2305 ms 103.191.209.155
29 2026-08-24 12:06 639231693747052549
6 ms 103.191.209.155
28 2026-08-24 11:50 639231683712487276
290 ms 103.191.209.155
27 2026-08-24 11:33 639231673513573868
310 ms 103.191.209.155
26 2026-08-24 10:40 639231641791249939
291 ms 103.191.209.155
25 2026-08-24 10:23 639231631866211033
7 ms 103.191.209.155
24 2026-08-24 10:06 639231621644955316
299 ms 103.191.209.155
23 2026-08-24 09:49 639231611478799259
157 ms 103.191.209.155
22 2026-08-24 08:57 639231579923718211
152 ms 103.191.209.155
21 2026-08-24 08:40 639231569810702936
301 ms 103.191.209.155
20 2026-08-24 08:23 639231559762411619
284 ms 103.191.209.155
19 2026-08-24 08:06 639231549663595407
2153 ms 103.191.209.155
18 2026-08-24 07:14 639231518076817246
149 ms 103.191.209.155
17 2026-08-24 06:57 639231508078650885
152 ms 103.191.209.155
16 2026-08-24 06:40 639231498210697093
291 ms 103.191.209.155
15 2026-08-24 06:24 639231488109699360
7 ms 103.191.209.155
14 2026-08-24 05:32 639231456772510692
2007 ms 103.191.209.155
13 2026-08-24 05:15 639231447084631185
290 ms 103.191.209.155
12 2026-08-24 04:59 639231437208519473
293 ms 103.191.209.155
11 2026-08-24 04:42 639231427209627490
261 ms 103.191.209.155
10 2026-08-24 03:50 639231395791246644
289 ms 103.191.209.155
9 2026-08-24 03:34 639231386075551458
2 ms 103.191.209.155
8 2026-08-24 03:17 639231376208713791
290 ms 103.191.209.155
7 2026-08-24 03:01 639231366170589276
161 ms 103.191.209.155
6 2026-08-24 02:08 639231334732159368
3 ms 103.191.209.155
5 2026-08-24 01:52 639231325035670078
3 ms 103.191.209.155
4 2026-08-24 01:35 639231315132253837
3 ms 103.191.209.155
3 2026-08-24 01:19 639231305014280808
5 ms 103.191.209.155
2 2026-08-24 00:26 639231273779380675
18 ms 103.191.209.155
1 2026-08-24 00:11 639231264180839154
179 ms 103.191.209.155