DNS response history for ns1.hom.to

ns1.hom.to 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-26. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 161 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.hom.to.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

161 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.67.240.180

Most recently resolved hosting IP on selected date

Successful Responses

31

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.hom.to

Showing DNS history for 2026-08-26 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
31 2026-08-26 10:02 639233350067824371
12 ms 203.67.240.180
30 2026-08-26 09:45 639233339545274518
12 ms 203.67.240.180
29 2026-08-26 09:28 639233329214918079
15 ms 203.67.240.180
28 2026-08-26 09:10 639233318749762337
2056 ms 203.67.240.180
27 2026-08-26 08:53 639233308387917838
38 ms 203.67.240.180
26 2026-08-26 08:36 639233297961740122
21 ms 203.67.240.180
25 2026-08-26 08:18 639233287487159094
20 ms 203.67.240.180
24 2026-08-26 08:01 639233276995531707
69 ms 203.67.240.180
23 2026-08-26 07:43 639233266521568229
55 ms 203.67.240.180
22 2026-08-26 07:26 639233256081047431
43 ms 203.67.240.180
21 2026-08-26 06:32 639233223620132921
13 ms 203.67.240.180
20 2026-08-26 06:14 639233213287814244
23 ms 203.67.240.180
19 2026-08-26 05:57 639233202925983161
33 ms 203.67.240.180
18 2026-08-26 05:40 639233192644780696
77 ms 203.67.240.180
17 2026-08-26 05:23 639233182401183833
23 ms 203.67.240.180
16 2026-08-26 05:06 639233172074181051
17 ms 203.67.240.180
15 2026-08-26 04:49 639233161808421455
29 ms 203.67.240.180
14 2026-08-26 04:31 639233151357344052
37 ms 203.67.240.180
13 2026-08-26 04:14 639233141034116946
13 ms 203.67.240.180
12 2026-08-26 03:57 639233130828334142
15 ms 203.67.240.180
11 2026-08-26 03:40 639233120373450007
2032 ms 203.67.240.180
10 2026-08-26 03:22 639233110066216193
46 ms 203.67.240.180
9 2026-08-26 02:29 639233078065410564
10 ms 203.67.240.180
8 2026-08-26 02:12 639233067787457832
24 ms 203.67.240.180
7 2026-08-26 01:55 639233057501801162
37 ms 203.67.240.180
6 2026-08-26 01:37 639233047089431703
45 ms 203.67.240.180
5 2026-08-26 01:20 639233036754790688
41 ms 203.67.240.180
4 2026-08-26 01:03 639233026412602472
39 ms 203.67.240.180
3 2026-08-26 00:46 639233016064066127
18 ms 203.67.240.180
2 2026-08-26 00:29 639233005922655772
38 ms 203.67.240.180
1 2026-08-26 00:12 639232995672256907
52 ms 203.67.240.180