DNS response history for ns2.apskanpur.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

376 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:24

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

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 ns2.apskanpur.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
35 2026-08-25 12:24 639232566381512620
323 ms 49.50.119.2
34 2026-08-25 12:07 639232556111768563
334 ms 49.50.119.2
33 2026-08-25 11:50 639232545839529039
171 ms 49.50.119.2
32 2026-08-25 11:33 639232535349285207
325 ms 49.50.119.2
31 2026-08-25 11:15 639232524938080723
338 ms 49.50.119.2
30 2026-08-25 10:21 639232492740373468
342 ms 49.50.119.2
29 2026-08-25 10:04 639232482235303141
348 ms 49.50.119.2
28 2026-08-25 09:47 639232471861770303
334 ms 49.50.119.2
27 2026-08-25 09:29 639232461630217327
173 ms 49.50.119.2
26 2026-08-25 09:12 639232451282965990
339 ms 49.50.119.2
25 2026-08-25 08:55 639232440814614938
2317 ms 49.50.119.2
24 2026-08-25 08:38 639232430410720425
339 ms 49.50.119.2
23 2026-08-25 08:20 639232420003096185
365 ms 49.50.119.2
22 2026-08-25 08:03 639232409467287444
176 ms 49.50.119.2
21 2026-08-25 07:45 639232399077195997
384 ms 49.50.119.2
20 2026-08-25 07:28 639232388731528337
384 ms 49.50.119.2
19 2026-08-25 07:11 639232378288598612
182 ms 49.50.119.2
18 2026-08-25 06:17 639232346196373643
168 ms 49.50.119.2
17 2026-08-25 06:00 639232336112370741
348 ms 49.50.119.2
16 2026-08-25 05:43 639232326146508970
346 ms 49.50.119.2
15 2026-08-25 05:27 639232316189381720
334 ms 49.50.119.2
14 2026-08-25 05:10 639232306217998913
336 ms 49.50.119.2
13 2026-08-25 04:54 639232296255744174
177 ms 49.50.119.2
12 2026-08-25 04:37 639232286095760789
335 ms 49.50.119.2
11 2026-08-25 04:20 639232276086186273
344 ms 49.50.119.2
10 2026-08-25 04:03 639232265900986425
339 ms 49.50.119.2
9 2026-08-25 03:46 639232255723518075
375 ms 49.50.119.2
8 2026-08-25 03:29 639232245484452890
345 ms 49.50.119.2
7 2026-08-25 03:12 639232235157175331
349 ms 49.50.119.2
6 2026-08-25 02:19 639232203197189095
377 ms 49.50.119.2
5 2026-08-25 02:02 639232192844564298
365 ms 49.50.119.2
4 2026-08-25 01:44 639232182496008942
369 ms 49.50.119.2
3 2026-08-25 01:27 639232172197053132
358 ms 49.50.119.2
2 2026-08-25 00:34 639232140250307418
372 ms 49.50.119.2
1 2026-08-25 00:17 639232129927860324
351 ms 49.50.119.2