DNS response history for ns1.dayver.net

ns1.dayver.net 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 33 DNS check records, 33 successful responses, 0 failed responses, and 416 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.dayver.net.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

416 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.200.43.225

Most recently resolved hosting IP on selected date

Successful Responses

33

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.dayver.net

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
33 2026-08-26 10:42 639233370841350248
5 ms 91.200.43.225
32 2026-08-26 10:25 639233360361507238
5 ms 91.200.43.225
31 2026-08-26 10:07 639233350067824371
24 ms 91.200.43.225
30 2026-08-26 09:50 639233339545274518
58 ms 91.200.43.225
29 2026-08-26 09:32 639233329214918079
210 ms 91.200.43.225
28 2026-08-26 09:15 639233318749762337
221 ms 91.200.43.225
27 2026-08-26 08:58 639233308387917838
2244 ms 91.200.43.225
26 2026-08-26 08:40 639233297961740122
206 ms 91.200.43.225
25 2026-08-26 08:23 639233287487159094
5 ms 91.200.43.225
24 2026-08-26 08:06 639233276995531707
370 ms 91.200.43.225
23 2026-08-26 07:48 639233266521568229
220 ms 91.200.43.225
22 2026-08-26 07:30 639233256081047431
238 ms 91.200.43.225
21 2026-08-26 06:37 639233223620132921
2092 ms 91.200.43.225
20 2026-08-26 06:19 639233213287814244
397 ms 91.200.43.225
19 2026-08-26 06:02 639233202925983161
245 ms 91.200.43.225
18 2026-08-26 05:45 639233192644780696
208 ms 91.200.43.225
17 2026-08-26 05:28 639233182401183833
246 ms 91.200.43.225
16 2026-08-26 05:11 639233172074181051
333 ms 91.200.43.225
15 2026-08-26 04:53 639233161808421455
2045 ms 91.200.43.225
14 2026-08-26 04:36 639233151357344052
343 ms 91.200.43.225
13 2026-08-26 04:19 639233141034116946
361 ms 91.200.43.225
12 2026-08-26 04:02 639233130828334142
229 ms 91.200.43.225
11 2026-08-26 03:45 639233120373450007
218 ms 91.200.43.225
10 2026-08-26 03:27 639233110066216193
9 ms 91.200.43.225
9 2026-08-26 02:34 639233078065410564
210 ms 91.200.43.225
8 2026-08-26 02:17 639233067787457832
78 ms 91.200.43.225
7 2026-08-26 02:00 639233057501801162
229 ms 91.200.43.225
6 2026-08-26 01:42 639233047089431703
2007 ms 91.200.43.225
5 2026-08-26 01:25 639233036754790688
386 ms 91.200.43.225
4 2026-08-26 01:08 639233026412602472
39 ms 91.200.43.225
3 2026-08-26 00:51 639233016064066127
223 ms 91.200.43.225
2 2026-08-26 00:33 639233005922655772
3 ms 91.200.43.225
1 2026-08-26 00:16 639232995672256907
7 ms 91.200.43.225