DNS response history for ns2.coovum.com

ns2.coovum.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 36 DNS check records, 35 successful responses, 1 failed responses, and 398 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.coovum.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

398 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.120.176.120

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.coovum.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
36 2026-08-25 12:36 639232576780683689
7 ms 103.120.176.120
35 2026-08-25 12:18 639232566381512620
8 ms 103.120.176.120
34 2026-08-25 12:01 639232556111768563
146 ms 103.120.176.120
33 2026-08-25 11:44 639232545839529039
277 ms 103.120.176.120
32 2026-08-25 11:27 639232535349285207
264 ms 103.120.176.120
31 2026-08-25 11:09 639232524938080723
10 ms 103.120.176.120
30 2026-08-25 10:15 639232492740373468
4 ms 103.120.176.120
29 2026-08-25 09:58 639232482235303141
267 ms 103.120.176.120
28 2026-08-25 09:41 639232471861770303
30 ms 103.120.176.120
27 2026-08-25 09:24 639232461630217327
280 ms 103.120.176.120
26 2026-08-25 09:07 639232451282965990
-
25 2026-08-25 08:49 639232440814614938
276 ms 103.120.176.120
24 2026-08-25 08:32 639232430410720425
4 ms 103.120.176.120
23 2026-08-25 08:14 639232420003096185
2198 ms 103.120.176.120
22 2026-08-25 07:57 639232409467287444
13 ms 103.120.176.120
21 2026-08-25 07:40 639232399077195997
2174 ms 103.120.176.120
20 2026-08-25 07:22 639232388731528337
4 ms 103.120.176.120
19 2026-08-25 07:05 639232378288598612
143 ms 103.120.176.120
18 2026-08-25 06:11 639232346196373643
6 ms 103.120.176.120
17 2026-08-25 05:54 639232336112370741
263 ms 103.120.176.120
16 2026-08-25 05:38 639232326146508970
277 ms 103.120.176.120
15 2026-08-25 05:21 639232316189381720
141 ms 103.120.176.120
14 2026-08-25 05:05 639232306217998913
2159 ms 103.120.176.120
13 2026-08-25 04:48 639232296255744174
283 ms 103.120.176.120
12 2026-08-25 04:31 639232286095760789
525 ms 103.120.176.120
11 2026-08-25 04:14 639232276086186273
13 ms 103.120.176.120
10 2026-08-25 03:57 639232265900986425
134 ms 103.120.176.120
9 2026-08-25 03:40 639232255723518075
294 ms 103.120.176.120
8 2026-08-25 03:23 639232245484452890
278 ms 103.120.176.120
7 2026-08-25 03:06 639232235157175331
281 ms 103.120.176.120
6 2026-08-25 02:13 639232203197189095
15 ms 103.120.176.120
5 2026-08-25 01:56 639232192844564298
2279 ms 103.120.176.120
4 2026-08-25 01:39 639232182496008942
316 ms 103.120.176.120
3 2026-08-25 01:21 639232172197053132
292 ms 103.120.176.120
2 2026-08-25 00:28 639232140250307418
134 ms 103.120.176.120
1 2026-08-25 00:11 639232129927860324
139 ms 103.120.176.120