DNS response history for ns3.bluuurgh.com

ns3.bluuurgh.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-25. For this date, NameServerHistory found 33 DNS check records, 33 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 ns3.bluuurgh.com.
Records on Selected Date

33

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-25 11:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.80.98.114

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 ns3.bluuurgh.com

Showing DNS history for 2026-08-25 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-25 11:43 639232545839529039
47 ms 129.80.98.114
32 2026-08-25 11:25 639232535349285207
142 ms 129.80.98.114
31 2026-08-25 11:08 639232524938080723
10 ms 129.80.98.114
30 2026-08-25 10:14 639232492740373468
2011 ms 129.80.98.114
29 2026-08-25 09:57 639232482235303141
39 ms 129.80.98.114
28 2026-08-25 09:39 639232471861770303
24 ms 129.80.98.114
27 2026-08-25 09:22 639232461630217327
38 ms 129.80.98.114
26 2026-08-25 09:05 639232451282965990
159 ms 129.80.98.114
25 2026-08-25 08:48 639232440814614938
38 ms 129.80.98.114
24 2026-08-25 08:30 639232430410720425
1116 ms 129.80.98.114
23 2026-08-25 08:13 639232420003096185
19 ms 129.80.98.114
22 2026-08-25 07:56 639232409467287444
18 ms 129.80.98.114
21 2026-08-25 07:38 639232399077195997
28 ms 129.80.98.114
20 2026-08-25 07:21 639232388731528337
41 ms 129.80.98.114
19 2026-08-25 07:04 639232378288598612
2115 ms 129.80.98.114
18 2026-08-25 06:10 639232346196373643
126 ms 129.80.98.114
17 2026-08-25 05:53 639232336112370741
24 ms 129.80.98.114
16 2026-08-25 05:37 639232326146508970
32 ms 129.80.98.114
15 2026-08-25 05:20 639232316189381720
42 ms 129.80.98.114
14 2026-08-25 05:04 639232306217998913
13 ms 129.80.98.114
13 2026-08-25 04:47 639232296255744174
31 ms 129.80.98.114
12 2026-08-25 04:30 639232286095760789
24 ms 129.80.98.114
11 2026-08-25 04:13 639232276086186273
48 ms 129.80.98.114
10 2026-08-25 03:56 639232265900986425
21 ms 129.80.98.114
9 2026-08-25 03:39 639232255723518075
141 ms 129.80.98.114
8 2026-08-25 03:22 639232245484452890
28 ms 129.80.98.114
7 2026-08-25 03:05 639232235157175331
25 ms 129.80.98.114
6 2026-08-25 02:12 639232203197189095
105 ms 129.80.98.114
5 2026-08-25 01:55 639232192844564298
38 ms 129.80.98.114
4 2026-08-25 01:37 639232182496008942
50 ms 129.80.98.114
3 2026-08-25 01:20 639232172197053132
50 ms 129.80.98.114
2 2026-08-25 00:27 639232140250307418
40 ms 129.80.98.114
1 2026-08-25 00:10 639232129927860324
232 ms 129.80.98.114