DNS response history for ns1.heroball.org

ns1.heroball.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-26. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 522 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 ns1.heroball.org.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

522 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

178.32.137.73

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns1.heroball.org

Showing DNS history for 2026-08-26 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
29 2026-08-26 09:27 639233329214918079
170 ms 178.32.137.73
28 2026-08-26 09:10 639233318749762337
393 ms 178.32.137.73
27 2026-08-26 08:52 639233308387917838
58 ms 178.32.137.73
26 2026-08-26 08:35 639233297961740122
288 ms 178.32.137.73
25 2026-08-26 08:18 639233287487159094
116 ms 178.32.137.73
24 2026-08-26 08:00 639233276995531707
48 ms 178.32.137.73
23 2026-08-26 07:43 639233266521568229
503 ms 178.32.137.73
22 2026-08-26 07:25 639233256081047431
177 ms 178.32.137.73
21 2026-08-26 06:31 639233223620132921
179 ms 178.32.137.73
20 2026-08-26 06:14 639233213287814244
105 ms 178.32.137.73
19 2026-08-26 05:57 639233202925983161
278 ms 178.32.137.73
18 2026-08-26 05:39 639233192644780696
45 ms 178.32.137.73
17 2026-08-26 05:22 639233182401183833
494 ms 178.32.137.73
16 2026-08-26 05:05 639233172074181051
160 ms 178.32.137.73
15 2026-08-26 04:48 639233161808421455
155 ms 178.32.137.73
14 2026-08-26 04:31 639233151357344052
271 ms 178.32.137.73
13 2026-08-26 04:14 639233141034116946
405 ms 178.32.137.73
12 2026-08-26 03:56 639233130828334142
2184 ms 178.32.137.73
11 2026-08-26 03:39 639233120373450007
2040 ms 178.32.137.73
10 2026-08-26 03:22 639233110066216193
434 ms 178.32.137.73
9 2026-08-26 02:29 639233078065410564
27 ms 178.32.137.73
8 2026-08-26 02:11 639233067787457832
35 ms 178.32.137.73
7 2026-08-26 01:54 639233057501801162
32 ms 178.32.137.73
6 2026-08-26 01:37 639233047089431703
2025 ms 178.32.137.73
5 2026-08-26 01:20 639233036754790688
2109 ms 178.32.137.73
4 2026-08-26 01:02 639233026412602472
2015 ms 178.32.137.73
3 2026-08-26 00:45 639233016064066127
181 ms 178.32.137.73
2 2026-08-26 00:28 639233005922655772
158 ms 178.32.137.73
1 2026-08-26 00:11 639232995672256907
52 ms 178.32.137.73