DNS response history for ns1.daycomdns.com

ns1.daycomdns.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-31. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 253 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.daycomdns.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

253 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.185.150.106

Most recently resolved hosting IP on selected date

Successful Responses

32

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

Showing DNS history for 2026-08-31 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
32 2026-08-31 10:42 639237690759595513
246 ms 192.185.150.106
31 2026-08-31 10:24 639237680122296836
7 ms 192.185.150.106
30 2026-08-31 09:30 639237647999458954
128 ms 192.185.150.106
29 2026-08-31 09:13 639237637680951774
137 ms 192.185.150.106
28 2026-08-31 08:56 639237627437728712
244 ms 192.185.150.106
27 2026-08-31 08:39 639237617127808241
242 ms 192.185.150.106
26 2026-08-31 08:22 639237606990101394
250 ms 192.185.150.106
25 2026-08-31 08:05 639237596595480036
127 ms 192.185.150.106
24 2026-08-31 07:48 639237586261012001
243 ms 192.185.150.106
23 2026-08-31 07:30 639237576047657695
124 ms 192.185.150.106
22 2026-08-31 07:13 639237565832936443
261 ms 192.185.150.106
21 2026-08-31 06:56 639237555466329546
243 ms 192.185.150.106
20 2026-08-31 06:39 639237545032411072
243 ms 192.185.150.106
19 2026-08-31 06:21 639237534469438634
247 ms 192.185.150.106
18 2026-08-31 05:28 639237502279296801
120 ms 192.185.150.106
17 2026-08-31 05:11 639237492362730124
248 ms 192.185.150.106
16 2026-08-31 04:54 639237482311584319
127 ms 192.185.150.106
15 2026-08-31 04:37 639237472150685594
129 ms 192.185.150.106
14 2026-08-31 04:20 639237462055295430
241 ms 192.185.150.106
13 2026-08-31 04:04 639237452089913890
243 ms 192.185.150.106
12 2026-08-31 03:47 639237441972654103
240 ms 192.185.150.106
11 2026-08-31 03:30 639237432052396478
242 ms 192.185.150.106
10 2026-08-31 03:14 639237422012990851
246 ms 192.185.150.106
9 2026-08-31 02:57 639237411889602012
243 ms 192.185.150.106
8 2026-08-31 02:40 639237401637354221
243 ms 192.185.150.106
7 2026-08-31 02:23 639237391412690360
246 ms 192.185.150.106
6 2026-08-31 01:30 639237359972957132
2175 ms 192.185.150.106
5 2026-08-31 01:14 639237350032183979
3 ms 192.185.150.106
4 2026-08-31 00:57 639237340111452066
117 ms 192.185.150.106
3 2026-08-31 00:40 639237329967272514
244 ms 192.185.150.106
2 2026-08-31 00:24 639237319916508151
122 ms 192.185.150.106
1 2026-08-31 00:07 639237309944877243
122 ms 192.185.150.106