DNS response history for ns2.guyhoffmann.com

ns2.guyhoffmann.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 35 DNS check records, 35 successful responses, 0 failed responses, and 210 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.guyhoffmann.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

210 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.121.33.104

Most recently resolved hosting IP on selected date

Successful Responses

35

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