DNS response history for harad.uberbox.org

harad.uberbox.org 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 28 DNS check records, 28 successful responses, 0 failed responses, and 292 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 harad.uberbox.org.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

292 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.190.112.202

Most recently resolved hosting IP on selected date

Successful Responses

28

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 harad.uberbox.org

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
28 2026-08-25 09:44 639232471861770303
8 ms 209.190.112.202
27 2026-08-25 09:27 639232461630217327
321 ms 209.190.112.202
26 2026-08-25 09:10 639232451282965990
194 ms 209.190.112.202
25 2026-08-25 08:52 639232440814614938
128 ms 209.190.112.202
24 2026-08-25 08:35 639232430410720425
2119 ms 209.190.112.202
23 2026-08-25 08:18 639232420003096185
238 ms 209.190.112.202
22 2026-08-25 08:00 639232409467287444
119 ms 209.190.112.202
21 2026-08-25 07:43 639232399077195997
10 ms 209.190.112.202
20 2026-08-25 07:25 639232388731528337
213 ms 209.190.112.202
19 2026-08-25 07:08 639232378288598612
116 ms 209.190.112.202
18 2026-08-25 06:14 639232346196373643
242 ms 209.190.112.202
17 2026-08-25 05:57 639232336112370741
4 ms 209.190.112.202
16 2026-08-25 05:41 639232326146508970
4 ms 209.190.112.202
15 2026-08-25 05:24 639232316189381720
116 ms 209.190.112.202
14 2026-08-25 05:08 639232306217998913
120 ms 209.190.112.202
13 2026-08-25 04:51 639232296255744174
242 ms 209.190.112.202
12 2026-08-25 04:34 639232286095760789
247 ms 209.190.112.202
11 2026-08-25 04:17 639232276086186273
233 ms 209.190.112.202
10 2026-08-25 04:01 639232265900986425
115 ms 209.190.112.202
9 2026-08-25 03:44 639232255723518075
112 ms 209.190.112.202
8 2026-08-25 03:27 639232245484452890
110 ms 209.190.112.202
7 2026-08-25 03:09 639232235157175331
281 ms 209.190.112.202
6 2026-08-25 02:16 639232203197189095
262 ms 209.190.112.202
5 2026-08-25 01:59 639232192844564298
2007 ms 209.190.112.202
4 2026-08-25 01:42 639232182496008942
124 ms 209.190.112.202
3 2026-08-25 01:24 639232172197053132
244 ms 209.190.112.202
2 2026-08-25 00:31 639232140250307418
3 ms 209.190.112.202
1 2026-08-25 00:14 639232129927860324
244 ms 209.190.112.202