DNS response history for ns34.twirlhost.com

ns34.twirlhost.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-27. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 271 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 ns34.twirlhost.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

271 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.160.151.106

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 ns34.twirlhost.com

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
33 2026-08-27 10:29 639234233269654413
21 ms 108.160.151.106
32 2026-08-27 10:12 639234222943951923
35 ms 108.160.151.106
31 2026-08-27 09:55 639234212558002823
34 ms 108.160.151.106
30 2026-08-27 09:37 639234202117531850
11 ms 108.160.151.106
29 2026-08-27 09:20 639234191649612722
19 ms 108.160.151.106
28 2026-08-27 09:02 639234181105879568
15 ms 108.160.151.106
27 2026-08-27 08:45 639234170713214496
29 ms 108.160.151.106
26 2026-08-27 08:28 639234160341037652
21 ms 108.160.151.106
25 2026-08-27 08:10 639234149799404224
35 ms 108.160.151.106
24 2026-08-27 07:53 639234139553286469
7 ms 108.160.151.106
23 2026-08-27 06:59 639234107183588293
11 ms 108.160.151.106
22 2026-08-27 06:42 639234096905435724
2081 ms 108.160.151.106
21 2026-08-27 06:25 639234086579410775
28 ms 108.160.151.106
20 2026-08-27 06:08 639234076291157956
12 ms 108.160.151.106
19 2026-08-27 05:50 639234065981939454
34 ms 108.160.151.106
18 2026-08-27 05:33 639234055548642997
22 ms 108.160.151.106
17 2026-08-27 05:16 639234045267979603
59 ms 108.160.151.106
16 2026-08-27 04:59 639234034999717463
2079 ms 108.160.151.106
15 2026-08-27 04:42 639234024739225358
2022 ms 108.160.151.106
14 2026-08-27 04:24 639234014311170162
36 ms 108.160.151.106
13 2026-08-27 04:07 639234003806017640
35 ms 108.160.151.106
12 2026-08-27 03:49 639233993356203030
4 ms 108.160.151.106
11 2026-08-27 02:56 639233961301716608
32 ms 108.160.151.106
10 2026-08-27 02:39 639233950834200647
13 ms 108.160.151.106
9 2026-08-27 02:21 639233940431849026
2020 ms 108.160.151.106
8 2026-08-27 02:04 639233930110596398
22 ms 108.160.151.106
7 2026-08-27 01:47 639233919705434540
37 ms 108.160.151.106
6 2026-08-27 01:30 639233909452807845
16 ms 108.160.151.106
5 2026-08-27 01:12 639233899096420820
5 ms 108.160.151.106
4 2026-08-27 00:55 639233888707824939
32 ms 108.160.151.106
3 2026-08-27 00:38 639233878461203802
8 ms 108.160.151.106
2 2026-08-27 00:21 639233868060868209
76 ms 108.160.151.106
1 2026-08-27 00:03 639233857450922991
26 ms 108.160.151.106