DNS response history for ns2.apspune.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

381 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.50.119.2

Most recently resolved hosting IP on selected date

Successful Responses

31

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.apspune.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
31 2026-08-25 11:15 639232524938080723
4 ms 49.50.119.2
30 2026-08-25 10:21 639232492740373468
329 ms 49.50.119.2
29 2026-08-25 10:04 639232482235303141
322 ms 49.50.119.2
28 2026-08-25 09:46 639232471861770303
181 ms 49.50.119.2
27 2026-08-25 09:29 639232461630217327
3 ms 49.50.119.2
26 2026-08-25 09:12 639232451282965990
344 ms 49.50.119.2
25 2026-08-25 08:54 639232440814614938
351 ms 49.50.119.2
24 2026-08-25 08:37 639232430410720425
339 ms 49.50.119.2
23 2026-08-25 08:20 639232420003096185
351 ms 49.50.119.2
22 2026-08-25 08:02 639232409467287444
344 ms 49.50.119.2
21 2026-08-25 07:45 639232399077195997
337 ms 49.50.119.2
20 2026-08-25 07:27 639232388731528337
350 ms 49.50.119.2
19 2026-08-25 07:10 639232378288598612
339 ms 49.50.119.2
18 2026-08-25 06:16 639232346196373643
327 ms 49.50.119.2
17 2026-08-25 06:00 639232336112370741
5 ms 49.50.119.2
16 2026-08-25 05:43 639232326146508970
338 ms 49.50.119.2
15 2026-08-25 05:26 639232316189381720
1681 ms 49.50.119.2
14 2026-08-25 05:10 639232306217998913
1902 ms 49.50.119.2
13 2026-08-25 04:53 639232296255744174
333 ms 49.50.119.2
12 2026-08-25 04:36 639232286095760789
4 ms 49.50.119.2
11 2026-08-25 04:19 639232276086186273
330 ms 49.50.119.2
10 2026-08-25 04:03 639232265900986425
340 ms 49.50.119.2
9 2026-08-25 03:46 639232255723518075
353 ms 49.50.119.2
8 2026-08-25 03:29 639232245484452890
322 ms 49.50.119.2
7 2026-08-25 03:12 639232235157175331
356 ms 49.50.119.2
6 2026-08-25 02:18 639232203197189095
180 ms 49.50.119.2
5 2026-08-25 02:01 639232192844564298
346 ms 49.50.119.2
4 2026-08-25 01:44 639232182496008942
354 ms 49.50.119.2
3 2026-08-25 01:27 639232172197053132
376 ms 49.50.119.2
2 2026-08-25 00:33 639232140250307418
335 ms 49.50.119.2
1 2026-08-25 00:16 639232129927860324
341 ms 49.50.119.2