DNS response history for ns2.apsdanapur.com

ns2.apsdanapur.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-28. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 303 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.apsdanapur.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

303 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:33

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

29

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.apsdanapur.com

Showing DNS history for 2026-08-28 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
29 2026-08-28 12:33 639235163898672622
324 ms 49.50.119.2
28 2026-08-28 11:40 639235132147470568
452 ms 49.50.119.2
27 2026-08-28 11:23 639235121907744088
330 ms 49.50.119.2
26 2026-08-28 11:05 639235111428014262
343 ms 49.50.119.2
25 2026-08-28 10:48 639235100921813626
330 ms 49.50.119.2
24 2026-08-28 09:54 639235068670703481
328 ms 49.50.119.2
23 2026-08-28 09:37 639235058337459445
326 ms 49.50.119.2
22 2026-08-28 09:19 639235047825109146
320 ms 49.50.119.2
21 2026-08-28 09:02 639235037383229033
318 ms 49.50.119.2
20 2026-08-28 08:09 639235005619242711
330 ms 49.50.119.2
19 2026-08-28 07:52 639234995310346584
321 ms 49.50.119.2
18 2026-08-28 07:34 639234984946548933
314 ms 49.50.119.2
17 2026-08-28 07:17 639234974608077290
317 ms 49.50.119.2
16 2026-08-28 06:24 639234942529845595
320 ms 49.50.119.2
15 2026-08-28 06:07 639234932259126627
319 ms 49.50.119.2
14 2026-08-28 05:49 639234921916735988
314 ms 49.50.119.2
13 2026-08-28 05:32 639234911470038027
313 ms 49.50.119.2
12 2026-08-28 04:39 639234879588411654
333 ms 49.50.119.2
11 2026-08-28 04:22 639234869341589104
308 ms 49.50.119.2
10 2026-08-28 04:04 639234859012216675
310 ms 49.50.119.2
9 2026-08-28 03:47 639234848695364934
316 ms 49.50.119.2
8 2026-08-28 02:54 639234816952458162
315 ms 49.50.119.2
7 2026-08-28 02:37 639234806773081598
313 ms 49.50.119.2
6 2026-08-28 02:20 639234796382955255
320 ms 49.50.119.2
5 2026-08-28 02:03 639234786015782563
328 ms 49.50.119.2
4 2026-08-28 01:09 639234753811917646
305 ms 49.50.119.2
3 2026-08-28 00:52 639234743739767811
9 ms 49.50.119.2
2 2026-08-28 00:35 639234733372362811
3 ms 49.50.119.2
1 2026-08-28 00:18 639234723048550337
319 ms 49.50.119.2