DNS response history for ns2.webcaresolutionz.com

ns2.webcaresolutionz.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 392 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.webcaresolutionz.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

392 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.181.200.95

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.webcaresolutionz.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:34 639232576780683689
79 ms 103.181.200.95
35 2026-08-25 12:17 639232566381512620
267 ms 103.181.200.95
34 2026-08-25 12:00 639232556111768563
-
33 2026-08-25 11:43 639232545839529039
2142 ms 103.181.200.95
32 2026-08-25 11:25 639232535349285207
258 ms 103.181.200.95
31 2026-08-25 11:08 639232524938080723
80 ms 103.181.200.95
30 2026-08-25 10:14 639232492740373468
2185 ms 103.181.200.95
29 2026-08-25 09:57 639232482235303141
63 ms 103.181.200.95
28 2026-08-25 09:39 639232471861770303
36 ms 103.181.200.95
27 2026-08-25 09:22 639232461630217327
59 ms 103.181.200.95
26 2026-08-25 09:05 639232451282965990
102 ms 103.181.200.95
25 2026-08-25 08:48 639232440814614938
345 ms 103.181.200.95
24 2026-08-25 08:30 639232430410720425
56 ms 103.181.200.95
23 2026-08-25 08:13 639232420003096185
79 ms 103.181.200.95
22 2026-08-25 07:55 639232409467287444
113 ms 103.181.200.95
21 2026-08-25 07:38 639232399077195997
34 ms 103.181.200.95
20 2026-08-25 07:21 639232388731528337
314 ms 103.181.200.95
19 2026-08-25 07:03 639232378288598612
60 ms 103.181.200.95
18 2026-08-25 06:10 639232346196373643
59 ms 103.181.200.95
17 2026-08-25 05:53 639232336112370741
33 ms 103.181.200.95
16 2026-08-25 05:36 639232326146508970
184 ms 103.181.200.95
15 2026-08-25 05:20 639232316189381720
68 ms 103.181.200.95
14 2026-08-25 05:03 639232306217998913
16 ms 103.181.200.95
13 2026-08-25 04:47 639232296255744174
30 ms 103.181.200.95
12 2026-08-25 04:30 639232286095760789
72 ms 103.181.200.95
11 2026-08-25 04:13 639232276086186273
72 ms 103.181.200.95
10 2026-08-25 03:56 639232265900986425
34 ms 103.181.200.95
9 2026-08-25 03:39 639232255723518075
52 ms 103.181.200.95
8 2026-08-25 03:22 639232245484452890
2110 ms 103.181.200.95
7 2026-08-25 03:05 639232235157175331
2062 ms 103.181.200.95
6 2026-08-25 02:12 639232203197189095
168 ms 103.181.200.95
5 2026-08-25 01:54 639232192844564298
242 ms 103.181.200.95
4 2026-08-25 01:37 639232182496008942
60 ms 103.181.200.95
3 2026-08-25 01:20 639232172197053132
2055 ms 103.181.200.95
2 2026-08-25 00:26 639232140250307418
75 ms 103.181.200.95
1 2026-08-25 00:09 639232129927860324
57 ms 103.181.200.95