DNS response history for ns2.ardent.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

1132 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.49.82.13

Most recently resolved hosting IP on selected date

Successful Responses

36

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.ardent.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
36 2026-08-25 12:26 639232566381512620
326 ms 65.49.82.13
35 2026-08-25 12:08 639232556111768563
315 ms 65.49.82.13
34 2026-08-25 11:51 639232545839529039
319 ms 65.49.82.13
33 2026-08-25 11:34 639232535349285207
3811 ms 65.49.82.13
32 2026-08-25 11:17 639232524938080723
2007 ms 65.49.82.13
31 2026-08-25 10:23 639232492740373468
311 ms 65.49.82.13
30 2026-08-25 10:06 639232482235303141
2008 ms 65.49.82.13
29 2026-08-25 09:48 639232471861770303
2031 ms 65.49.82.13
28 2026-08-25 09:31 639232461630217327
320 ms 65.49.82.13
27 2026-08-25 09:14 639232451282965990
321 ms 65.49.82.13
26 2026-08-25 08:56 639232440814614938
3800 ms 65.49.82.13
25 2026-08-25 08:39 639232430410720425
311 ms 65.49.82.13
24 2026-08-25 08:22 639232420003096185
308 ms 65.49.82.13
23 2026-08-25 08:04 639232409467287444
319 ms 65.49.82.13
22 2026-08-25 07:47 639232399077195997
2007 ms 65.49.82.13
21 2026-08-25 07:29 639232388731528337
3681 ms 65.49.82.13
20 2026-08-25 07:12 639232378288598612
4327 ms 65.49.82.13
19 2026-08-25 06:18 639232346196373643
318 ms 65.49.82.13
18 2026-08-25 06:01 639232336112370741
4 ms 65.49.82.13
17 2026-08-25 05:45 639232326146508970
2 ms 65.49.82.13
16 2026-08-25 05:28 639232316189381720
2 ms 65.49.82.13
15 2026-08-25 05:12 639232306217998913
302 ms 65.49.82.13
14 2026-08-25 04:55 639232296255744174
3 ms 65.49.82.13
13 2026-08-25 04:38 639232286095760789
2155 ms 65.49.82.13
12 2026-08-25 04:21 639232276086186273
2151 ms 65.49.82.13
11 2026-08-25 04:05 639232265900986425
304 ms 65.49.82.13
10 2026-08-25 03:48 639232255723518075
674 ms 65.49.82.13
9 2026-08-25 03:31 639232245484452890
518 ms 65.49.82.13
8 2026-08-25 03:14 639232235157175331
2303 ms 65.49.82.13
7 2026-08-25 02:20 639232203197189095
307 ms 65.49.82.13
6 2026-08-25 02:03 639232192844564298
3656 ms 65.49.82.13
5 2026-08-25 01:46 639232182496008942
302 ms 65.49.82.13
4 2026-08-25 01:28 639232172197053132
305 ms 65.49.82.13
3 2026-08-25 00:35 639232140250307418
303 ms 65.49.82.13
2 2026-08-25 00:18 639232129927860324
303 ms 65.49.82.13
1 2026-08-25 00:01 639232119551972438
307 ms 65.49.82.13