DNS response history for ns2.apsahmedabad.co.in

ns2.apsahmedabad.co.in 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 26 DNS check records, 26 successful responses, 0 failed responses, and 342 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.apsahmedabad.co.in.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

342 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:12

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

26

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.apsahmedabad.co.in

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
26 2026-08-25 09:12 639232451282965990
340 ms 49.50.119.2
25 2026-08-25 08:55 639232440814614938
361 ms 49.50.119.2
24 2026-08-25 08:37 639232430410720425
340 ms 49.50.119.2
23 2026-08-25 08:20 639232420003096185
363 ms 49.50.119.2
22 2026-08-25 08:03 639232409467287444
357 ms 49.50.119.2
21 2026-08-25 07:45 639232399077195997
12 ms 49.50.119.2
20 2026-08-25 07:28 639232388731528337
351 ms 49.50.119.2
19 2026-08-25 07:10 639232378288598612
343 ms 49.50.119.2
18 2026-08-25 06:17 639232346196373643
340 ms 49.50.119.2
17 2026-08-25 06:00 639232336112370741
166 ms 49.50.119.2
16 2026-08-25 05:43 639232326146508970
348 ms 49.50.119.2
15 2026-08-25 05:26 639232316189381720
9 ms 49.50.119.2
14 2026-08-25 05:10 639232306217998913
1694 ms 49.50.119.2
13 2026-08-25 04:53 639232296255744174
336 ms 49.50.119.2
12 2026-08-25 04:37 639232286095760789
352 ms 49.50.119.2
11 2026-08-25 04:20 639232276086186273
342 ms 49.50.119.2
10 2026-08-25 04:03 639232265900986425
345 ms 49.50.119.2
9 2026-08-25 03:46 639232255723518075
368 ms 49.50.119.2
8 2026-08-25 03:29 639232245484452890
176 ms 49.50.119.2
7 2026-08-25 03:12 639232235157175331
203 ms 49.50.119.2
6 2026-08-25 02:18 639232203197189095
189 ms 49.50.119.2
5 2026-08-25 02:01 639232192844564298
340 ms 49.50.119.2
4 2026-08-25 01:44 639232182496008942
360 ms 49.50.119.2
3 2026-08-25 01:27 639232172197053132
341 ms 49.50.119.2
2 2026-08-25 00:33 639232140250307418
184 ms 49.50.119.2
1 2026-08-25 00:17 639232129927860324
344 ms 49.50.119.2