DNS response history for ns3.nimbware.com

ns3.nimbware.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-30. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 24 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.nimbware.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

24 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 12:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

195.250.25.105

Most recently resolved hosting IP on selected date

Successful Responses

38

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.nimbware.com

Showing DNS history for 2026-08-30 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
38 2026-08-30 12:13 639236888142648178
19 ms 195.250.25.105
37 2026-08-30 11:57 639236878057367680
24 ms 195.250.25.105
36 2026-08-30 11:40 639236867916029489
16 ms 195.250.25.105
35 2026-08-30 11:23 639236858088772005
17 ms 195.250.25.105
34 2026-08-30 11:07 639236848158742395
29 ms 195.250.25.105
33 2026-08-30 10:50 639236838137395574
35 ms 195.250.25.105
32 2026-08-30 10:33 639236827967386881
29 ms 195.250.25.105
31 2026-08-30 10:16 639236817708615077
21 ms 195.250.25.105
30 2026-08-30 09:23 639236785770651804
11 ms 195.250.25.105
29 2026-08-30 09:06 639236775820686373
45 ms 195.250.25.105
28 2026-08-30 08:49 639236765768339082
23 ms 195.250.25.105
27 2026-08-30 08:32 639236755602384085
23 ms 195.250.25.105
26 2026-08-30 08:16 639236745600094925
26 ms 195.250.25.105
25 2026-08-30 07:59 639236735311262753
20 ms 195.250.25.105
24 2026-08-30 07:41 639236724996745235
19 ms 195.250.25.105
23 2026-08-30 07:25 639236714839899761
11 ms 195.250.25.105
22 2026-08-30 07:08 639236704748431488
19 ms 195.250.25.105
21 2026-08-30 06:51 639236694430128550
35 ms 195.250.25.105
20 2026-08-30 06:33 639236684143292417
28 ms 195.250.25.105
19 2026-08-30 06:16 639236673972499943
46 ms 195.250.25.105
18 2026-08-30 05:23 639236642126522802
40 ms 195.250.25.105
17 2026-08-30 05:07 639236632183518198
24 ms 195.250.25.105
16 2026-08-30 04:50 639236622289312589
22 ms 195.250.25.105
15 2026-08-30 04:34 639236612490676525
32 ms 195.250.25.105
14 2026-08-30 04:17 639236602582494852
27 ms 195.250.25.105
13 2026-08-30 04:01 639236592511706469
23 ms 195.250.25.105
12 2026-08-30 03:44 639236582441006869
19 ms 195.250.25.105
11 2026-08-30 03:27 639236572478785089
17 ms 195.250.25.105
10 2026-08-30 03:11 639236562556749999
29 ms 195.250.25.105
9 2026-08-30 02:54 639236552353482281
14 ms 195.250.25.105
8 2026-08-30 02:37 639236542188881607
21 ms 195.250.25.105
7 2026-08-30 02:20 639236531885440105
31 ms 195.250.25.105
6 2026-08-30 01:26 639236499922985383
28 ms 195.250.25.105
5 2026-08-30 01:09 639236489713594431
18 ms 195.250.25.105
4 2026-08-30 00:53 639236479750443901
9 ms 195.250.25.105
3 2026-08-30 00:36 639236469719936375
38 ms 195.250.25.105
2 2026-08-30 00:19 639236459579244885
27 ms 195.250.25.105
1 2026-08-30 00:02 639236449582837549
15 ms 195.250.25.105