DNS response history for ns2.apurvawater.com

ns2.apurvawater.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 196 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.apurvawater.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

196 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.127.146.160

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.apurvawater.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 10:22 639232492740373468
3 ms 103.127.146.160
30 2026-08-25 10:05 639232482235303141
276 ms 103.127.146.160
29 2026-08-25 09:47 639232471861770303
282 ms 103.127.146.160
28 2026-08-25 09:30 639232461630217327
288 ms 103.127.146.160
27 2026-08-25 09:13 639232451282965990
279 ms 103.127.146.160
26 2026-08-25 08:56 639232440814614938
277 ms 103.127.146.160
25 2026-08-25 08:38 639232430410720425
278 ms 103.127.146.160
24 2026-08-25 08:21 639232420003096185
282 ms 103.127.146.160
23 2026-08-25 08:04 639232409467287444
315 ms 103.127.146.160
22 2026-08-25 07:46 639232399077195997
278 ms 103.127.146.160
21 2026-08-25 07:29 639232388731528337
280 ms 103.127.146.160
20 2026-08-25 07:12 639232378288598612
277 ms 103.127.146.160
19 2026-08-25 06:18 639232346196373643
282 ms 103.127.146.160
18 2026-08-25 06:01 639232336112370741
3 ms 103.127.146.160
17 2026-08-25 05:44 639232326146508970
3 ms 103.127.146.160
16 2026-08-25 05:28 639232316189381720
3 ms 103.127.146.160
15 2026-08-25 05:11 639232306217998913
2 ms 103.127.146.160
14 2026-08-25 04:54 639232296255744174
277 ms 103.127.146.160
13 2026-08-25 04:38 639232286095760789
4 ms 103.127.146.160
12 2026-08-25 04:21 639232276086186273
277 ms 103.127.146.160
11 2026-08-25 04:04 639232265900986425
276 ms 103.127.146.160
10 2026-08-25 03:47 639232255723518075
271 ms 103.127.146.160
9 2026-08-25 03:30 639232245484452890
293 ms 103.127.146.160
8 2026-08-25 03:13 639232235157175331
143 ms 103.127.146.160
7 2026-08-25 02:20 639232203197189095
287 ms 103.127.146.160
6 2026-08-25 02:03 639232192844564298
2 ms 103.127.146.160
5 2026-08-25 01:45 639232182496008942
3 ms 103.127.146.160
4 2026-08-25 01:28 639232172197053132
279 ms 103.127.146.160
3 2026-08-25 00:34 639232140250307418
278 ms 103.127.146.160
2 2026-08-25 00:18 639232129927860324
280 ms 103.127.146.160
1 2026-08-25 00:00 639232119551972438
3 ms 103.127.146.160