DNS response history for ns3.webcaresolutionz.com

ns3.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-27. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 347 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 ns3.webcaresolutionz.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

347 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

139.180.146.105

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns3.webcaresolutionz.com

Showing DNS history for 2026-08-27 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
33 2026-08-27 10:32 639234233269654413
2038 ms 139.180.146.105
32 2026-08-27 10:15 639234222943951923
74 ms 139.180.146.105
31 2026-08-27 09:58 639234212558002823
48 ms 139.180.146.105
30 2026-08-27 09:40 639234202117531850
62 ms 139.180.146.105
29 2026-08-27 09:23 639234191649612722
35 ms 139.180.146.105
28 2026-08-27 09:05 639234181105879568
86 ms 139.180.146.105
27 2026-08-27 08:48 639234170713214496
88 ms 139.180.146.105
26 2026-08-27 08:31 639234160341037652
144 ms 139.180.146.105
25 2026-08-27 08:13 639234149799404224
53 ms 139.180.146.105
24 2026-08-27 07:56 639234139553286469
116 ms 139.180.146.105
23 2026-08-27 07:02 639234107183588293
88 ms 139.180.146.105
22 2026-08-27 06:45 639234096905435724
84 ms 139.180.146.105
21 2026-08-27 06:28 639234086579410775
266 ms 139.180.146.105
20 2026-08-27 06:11 639234076291157956
81 ms 139.180.146.105
19 2026-08-27 05:53 639234065981939454
67 ms 139.180.146.105
18 2026-08-27 05:36 639234055548642997
56 ms 139.180.146.105
17 2026-08-27 05:19 639234045267979603
89 ms 139.180.146.105
16 2026-08-27 05:02 639234034999717463
75 ms 139.180.146.105
15 2026-08-27 04:45 639234024739225358
2101 ms 139.180.146.105
14 2026-08-27 04:27 639234014311170162
57 ms 139.180.146.105
13 2026-08-27 04:10 639234003806017640
352 ms 139.180.146.105
12 2026-08-27 03:52 639233993356203030
42 ms 139.180.146.105
11 2026-08-27 02:59 639233961301716608
58 ms 139.180.146.105
10 2026-08-27 02:42 639233950834200647
97 ms 139.180.146.105
9 2026-08-27 02:24 639233940431849026
4394 ms 139.180.146.105
8 2026-08-27 02:07 639233930110596398
255 ms 139.180.146.105
7 2026-08-27 01:50 639233919705434540
59 ms 139.180.146.105
6 2026-08-27 01:32 639233909452807845
51 ms 139.180.146.105
5 2026-08-27 01:15 639233899096420820
57 ms 139.180.146.105
4 2026-08-27 00:58 639233888707824939
45 ms 139.180.146.105
3 2026-08-27 00:41 639233878461203802
195 ms 139.180.146.105
2 2026-08-27 00:24 639233868060868209
37 ms 139.180.146.105
1 2026-08-27 00:06 639233857450922991
90 ms 139.180.146.105