DNS response history for heron.ns.supposedly.org

heron.ns.supposedly.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 35 DNS check records, 35 successful responses, 0 failed responses, and 337 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 heron.ns.supposedly.org.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

337 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.251.153.106

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 heron.ns.supposedly.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
35 2026-08-25 12:20 639232566381512620
484 ms 216.251.153.106
34 2026-08-25 12:03 639232556111768563
445 ms 216.251.153.106
33 2026-08-25 11:46 639232545839529039
171 ms 216.251.153.106
32 2026-08-25 11:29 639232535349285207
316 ms 216.251.153.106
31 2026-08-25 11:11 639232524938080723
42 ms 216.251.153.106
30 2026-08-25 10:17 639232492740373468
162 ms 216.251.153.106
29 2026-08-25 10:00 639232482235303141
598 ms 216.251.153.106
28 2026-08-25 09:43 639232471861770303
318 ms 216.251.153.106
27 2026-08-25 09:26 639232461630217327
561 ms 216.251.153.106
26 2026-08-25 09:08 639232451282965990
174 ms 216.251.153.106
25 2026-08-25 08:51 639232440814614938
328 ms 216.251.153.106
24 2026-08-25 08:34 639232430410720425
321 ms 216.251.153.106
23 2026-08-25 08:16 639232420003096185
491 ms 216.251.153.106
22 2026-08-25 07:59 639232409467287444
490 ms 216.251.153.106
21 2026-08-25 07:41 639232399077195997
5 ms 216.251.153.106
20 2026-08-25 07:24 639232388731528337
4 ms 216.251.153.106
19 2026-08-25 07:07 639232378288598612
318 ms 216.251.153.106
18 2026-08-25 06:13 639232346196373643
5 ms 216.251.153.106
17 2026-08-25 05:56 639232336112370741
167 ms 216.251.153.106
16 2026-08-25 05:40 639232326146508970
710 ms 216.251.153.106
15 2026-08-25 05:23 639232316189381720
326 ms 216.251.153.106
14 2026-08-25 05:07 639232306217998913
500 ms 216.251.153.106
13 2026-08-25 04:50 639232296255744174
317 ms 216.251.153.106
12 2026-08-25 04:33 639232286095760789
576 ms 216.251.153.106
11 2026-08-25 04:16 639232276086186273
323 ms 216.251.153.106
10 2026-08-25 03:59 639232265900986425
687 ms 216.251.153.106
9 2026-08-25 03:42 639232255723518075
4 ms 216.251.153.106
8 2026-08-25 03:25 639232245484452890
318 ms 216.251.153.106
7 2026-08-25 03:08 639232235157175331
313 ms 216.251.153.106
6 2026-08-25 02:15 639232203197189095
335 ms 216.251.153.106
5 2026-08-25 01:58 639232192844564298
495 ms 216.251.153.106
4 2026-08-25 01:40 639232182496008942
315 ms 216.251.153.106
3 2026-08-25 01:23 639232172197053132
377 ms 216.251.153.106
2 2026-08-25 00:30 639232140250307418
323 ms 216.251.153.106
1 2026-08-25 00:13 639232129927860324
480 ms 216.251.153.106