DNS response history for ns2.apon.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

270 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.237.153.230

Most recently resolved hosting IP on selected date

Successful Responses

34

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.apon.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
34 2026-08-25 11:57 639232556111768563
34 ms 104.237.153.230
33 2026-08-25 11:40 639232545839529039
28 ms 104.237.153.230
32 2026-08-25 11:23 639232535349285207
2034 ms 104.237.153.230
31 2026-08-25 11:06 639232524938080723
10 ms 104.237.153.230
30 2026-08-25 10:12 639232492740373468
101 ms 104.237.153.230
29 2026-08-25 09:55 639232482235303141
2032 ms 104.237.153.230
28 2026-08-25 09:37 639232471861770303
72 ms 104.237.153.230
27 2026-08-25 09:20 639232461630217327
2041 ms 104.237.153.230
26 2026-08-25 09:03 639232451282965990
49 ms 104.237.153.230
25 2026-08-25 08:45 639232440814614938
104 ms 104.237.153.230
24 2026-08-25 08:28 639232430410720425
14 ms 104.237.153.230
23 2026-08-25 08:11 639232420003096185
37 ms 104.237.153.230
22 2026-08-25 07:53 639232409467287444
45 ms 104.237.153.230
21 2026-08-25 07:36 639232399077195997
13 ms 104.237.153.230
20 2026-08-25 07:19 639232388731528337
2024 ms 104.237.153.230
19 2026-08-25 07:01 639232378288598612
20 ms 104.237.153.230
18 2026-08-25 06:08 639232346196373643
21 ms 104.237.153.230
17 2026-08-25 05:51 639232336112370741
30 ms 104.237.153.230
16 2026-08-25 05:34 639232326146508970
10 ms 104.237.153.230
15 2026-08-25 05:18 639232316189381720
40 ms 104.237.153.230
14 2026-08-25 05:01 639232306217998913
52 ms 104.237.153.230
13 2026-08-25 04:45 639232296255744174
50 ms 104.237.153.230
12 2026-08-25 04:28 639232286095760789
48 ms 104.237.153.230
11 2026-08-25 04:11 639232276086186273
42 ms 104.237.153.230
10 2026-08-25 03:54 639232265900986425
17 ms 104.237.153.230
9 2026-08-25 03:37 639232255723518075
14 ms 104.237.153.230
8 2026-08-25 03:20 639232245484452890
13 ms 104.237.153.230
7 2026-08-25 03:03 639232235157175331
22 ms 104.237.153.230
6 2026-08-25 02:09 639232203197189095
27 ms 104.237.153.230
5 2026-08-25 01:52 639232192844564298
52 ms 104.237.153.230
4 2026-08-25 01:35 639232182496008942
26 ms 104.237.153.230
3 2026-08-25 01:18 639232172197053132
21 ms 104.237.153.230
2 2026-08-25 00:24 639232140250307418
27 ms 104.237.153.230
1 2026-08-25 00:07 639232129927860324
8 ms 104.237.153.230