DNS response history for ns2.drivenhost.net

ns2.drivenhost.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-27. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 335 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 ns2.drivenhost.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

335 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

160.153.185.121

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns2.drivenhost.net

Showing DNS history for 2026-08-27 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
36 2026-08-27 12:07 639234286253196126
312 ms 160.153.185.121
35 2026-08-27 11:14 639234253963286387
301 ms 160.153.185.121
34 2026-08-27 10:56 639234243654907465
3 ms 160.153.185.121
33 2026-08-27 10:39 639234233269654413
5 ms 160.153.185.121
32 2026-08-27 10:22 639234222943951923
240 ms 160.153.185.121
31 2026-08-27 10:05 639234212558002823
4 ms 160.153.185.121
30 2026-08-27 09:47 639234202117531850
317 ms 160.153.185.121
29 2026-08-27 09:30 639234191649612722
323 ms 160.153.185.121
28 2026-08-27 09:12 639234181105879568
312 ms 160.153.185.121
27 2026-08-27 08:55 639234170713214496
312 ms 160.153.185.121
26 2026-08-27 08:38 639234160341037652
308 ms 160.153.185.121
25 2026-08-27 08:20 639234149799404224
323 ms 160.153.185.121
24 2026-08-27 08:03 639234139553286469
313 ms 160.153.185.121
23 2026-08-27 07:09 639234107183588293
305 ms 160.153.185.121
22 2026-08-27 06:52 639234096905435724
9 ms 160.153.185.121
21 2026-08-27 06:35 639234086579410775
296 ms 160.153.185.121
20 2026-08-27 06:17 639234076291157956
2167 ms 160.153.185.121
19 2026-08-27 06:00 639234065981939454
301 ms 160.153.185.121
18 2026-08-27 05:43 639234055548642997
297 ms 160.153.185.121
17 2026-08-27 05:26 639234045267979603
7 ms 160.153.185.121
16 2026-08-27 05:09 639234034999717463
298 ms 160.153.185.121
15 2026-08-27 04:52 639234024739225358
311 ms 160.153.185.121
14 2026-08-27 04:34 639234014311170162
249 ms 160.153.185.121
13 2026-08-27 04:17 639234003806017640
315 ms 160.153.185.121
12 2026-08-27 03:59 639233993356203030
312 ms 160.153.185.121
11 2026-08-27 03:06 639233961301716608
10 ms 160.153.185.121
10 2026-08-27 02:49 639233950834200647
310 ms 160.153.185.121
9 2026-08-27 02:31 639233940431849026
8 ms 160.153.185.121
8 2026-08-27 02:14 639233930110596398
310 ms 160.153.185.121
7 2026-08-27 01:57 639233919705434540
172 ms 160.153.185.121
6 2026-08-27 01:40 639233909452807845
315 ms 160.153.185.121
5 2026-08-27 01:22 639233899096420820
2161 ms 160.153.185.121
4 2026-08-27 01:05 639233888707824939
311 ms 160.153.185.121
3 2026-08-27 00:48 639233878461203802
307 ms 160.153.185.121
2 2026-08-27 00:31 639233868060868209
2 ms 160.153.185.121
1 2026-08-27 00:13 639233857450922991
218 ms 160.153.185.121