DNS response history for guild.dunetechnology.com

guild.dunetechnology.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, 34 successful responses, 1 failed responses, and 211 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 guild.dunetechnology.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

211 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.102.128.10

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for guild.dunetechnology.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:05 639234253963286387
14 ms 5.102.128.10
34 2026-08-27 10:47 639234243654907465
44 ms 5.102.128.10
33 2026-08-27 10:30 639234233269654413
-
32 2026-08-27 10:13 639234222943951923
84 ms 5.102.128.10
31 2026-08-27 09:56 639234212558002823
41 ms 5.102.128.10
30 2026-08-27 09:38 639234202117531850
11 ms 5.102.128.10
29 2026-08-27 09:21 639234191649612722
10 ms 5.102.128.10
28 2026-08-27 09:03 639234181105879568
4031 ms 5.102.128.10
27 2026-08-27 08:46 639234170713214496
2046 ms 5.102.128.10
26 2026-08-27 08:29 639234160341037652
32 ms 5.102.128.10
25 2026-08-27 08:11 639234149799404224
13 ms 5.102.128.10
24 2026-08-27 07:54 639234139553286469
6 ms 5.102.128.10
23 2026-08-27 07:00 639234107183588293
31 ms 5.102.128.10
22 2026-08-27 06:43 639234096905435724
24 ms 5.102.128.10
21 2026-08-27 06:26 639234086579410775
10 ms 5.102.128.10
20 2026-08-27 06:09 639234076291157956
38 ms 5.102.128.10
19 2026-08-27 05:51 639234065981939454
59 ms 5.102.128.10
18 2026-08-27 05:34 639234055548642997
9 ms 5.102.128.10
17 2026-08-27 05:17 639234045267979603
34 ms 5.102.128.10
16 2026-08-27 05:00 639234034999717463
33 ms 5.102.128.10
15 2026-08-27 04:43 639234024739225358
31 ms 5.102.128.10
14 2026-08-27 04:25 639234014311170162
50 ms 5.102.128.10
13 2026-08-27 04:08 639234003806017640
24 ms 5.102.128.10
12 2026-08-27 03:50 639233993356203030
28 ms 5.102.128.10
11 2026-08-27 02:57 639233961301716608
28 ms 5.102.128.10
10 2026-08-27 02:40 639233950834200647
22 ms 5.102.128.10
9 2026-08-27 02:22 639233940431849026
25 ms 5.102.128.10
8 2026-08-27 02:05 639233930110596398
45 ms 5.102.128.10
7 2026-08-27 01:48 639233919705434540
8 ms 5.102.128.10
6 2026-08-27 01:31 639233909452807845
50 ms 5.102.128.10
5 2026-08-27 01:13 639233899096420820
29 ms 5.102.128.10
4 2026-08-27 00:56 639233888707824939
118 ms 5.102.128.10
3 2026-08-27 00:39 639233878461203802
63 ms 5.102.128.10
2 2026-08-27 00:21 639233868060868209
48 ms 5.102.128.10
1 2026-08-27 00:04 639233857450922991
42 ms 5.102.128.10