DNS response history for ns2.auralcon.com

ns2.auralcon.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 39 DNS check records, 39 successful responses, 0 failed responses, and 265 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 ns2.auralcon.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

265 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.222.12.137

Most recently resolved hosting IP on selected date

Successful Responses

39

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 ns2.auralcon.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
39 2026-08-25 13:31 639232608016476376
351 ms 67.222.12.137
38 2026-08-25 13:13 639232597643611557
326 ms 67.222.12.137
37 2026-08-25 12:56 639232587225721862
326 ms 67.222.12.137
36 2026-08-25 12:39 639232576780683689
308 ms 67.222.12.137
35 2026-08-25 12:21 639232566381512620
307 ms 67.222.12.137
34 2026-08-25 12:04 639232556111768563
338 ms 67.222.12.137
33 2026-08-25 11:47 639232545839529039
353 ms 67.222.12.137
32 2026-08-25 11:30 639232535349285207
307 ms 67.222.12.137
31 2026-08-25 11:12 639232524938080723
306 ms 67.222.12.137
30 2026-08-25 10:19 639232492740373468
335 ms 67.222.12.137
29 2026-08-25 10:01 639232482235303141
315 ms 67.222.12.137
28 2026-08-25 09:44 639232471861770303
335 ms 67.222.12.137
27 2026-08-25 09:27 639232461630217327
17 ms 67.222.12.137
26 2026-08-25 09:10 639232451282965990
216 ms 67.222.12.137
25 2026-08-25 08:52 639232440814614938
313 ms 67.222.12.137
24 2026-08-25 08:35 639232430410720425
361 ms 67.222.12.137
23 2026-08-25 08:18 639232420003096185
304 ms 67.222.12.137
22 2026-08-25 08:00 639232409467287444
310 ms 67.222.12.137
21 2026-08-25 07:43 639232399077195997
338 ms 67.222.12.137
20 2026-08-25 07:25 639232388731528337
322 ms 67.222.12.137
19 2026-08-25 07:08 639232378288598612
4 ms 67.222.12.137
18 2026-08-25 06:14 639232346196373643
17 ms 67.222.12.137
17 2026-08-25 05:57 639232336112370741
3 ms 67.222.12.137
16 2026-08-25 05:41 639232326146508970
302 ms 67.222.12.137
15 2026-08-25 05:24 639232316189381720
333 ms 67.222.12.137
14 2026-08-25 05:08 639232306217998913
309 ms 67.222.12.137
13 2026-08-25 04:51 639232296255744174
5 ms 67.222.12.137
12 2026-08-25 04:34 639232286095760789
333 ms 67.222.12.137
11 2026-08-25 04:17 639232276086186273
321 ms 67.222.12.137
10 2026-08-25 04:01 639232265900986425
201 ms 67.222.12.137
9 2026-08-25 03:44 639232255723518075
323 ms 67.222.12.137
8 2026-08-25 03:26 639232245484452890
158 ms 67.222.12.137
7 2026-08-25 03:09 639232235157175331
359 ms 67.222.12.137
6 2026-08-25 02:16 639232203197189095
4 ms 67.222.12.137
5 2026-08-25 01:59 639232192844564298
310 ms 67.222.12.137
4 2026-08-25 01:42 639232182496008942
319 ms 67.222.12.137
3 2026-08-25 01:24 639232172197053132
325 ms 67.222.12.137
2 2026-08-25 00:31 639232140250307418
319 ms 67.222.12.137
1 2026-08-25 00:14 639232129927860324
319 ms 67.222.12.137