PointCloudScene License Servers
Current availability
| Name | Status | Timestamp |
|---|---|---|
| dc-hu-ls | Up | 2025-12-06 03:34 |
| pcs-com-ls | Up | 2025-12-06 03:34 |
Past hours
Incidents
| Name | Timestamp | Duration | Cause |
|---|---|---|---|
| pcs-com-ls | 2025-06-02 16:18 | 00:00:15 | |
| dc-hu-ls | 2025-06-05 22:36 | 00:00:01 | |
| pcs-com-ls | 2025-06-10 00:02 | 00:00:40 | |
| pcs-com-ls | 2025-06-10 10:21 | 00:00:01 | |
| pcs-com-ls | 2025-06-18 08:08 | 00:00:10 | |
| pcs-com-ls | 2025-06-22 11:29 | 00:00:01 | |
| dc-hu-ls | 2025-06-24 21:53 | 00:00:01 | |
| pcs-com-ls | 2025-06-25 07:16 | 00:02:08 | |
| pcs-com-ls | 2025-06-25 23:26 | 00:00:44 | |
| pcs-com-ls | 2025-06-26 01:33 | 00:00:08 | |
| pcs-com-ls | 2025-06-27 03:39 | 00:00:01 | |
| dc-hu-ls | 2025-07-01 20:14 | 00:00:01 | |
| dc-hu-ls | 2025-07-03 09:43 | 00:00:01 | |
| pcs-com-ls | 2025-07-03 09:53 | 00:00:04 | |
| dc-hu-ls | 2025-07-06 10:26 | 00:00:01 | |
| dc-hu-ls | 2025-07-08 09:59 | 00:00:07 | |
| dc-hu-ls | 2025-07-08 10:13 | 00:00:41 | |
| dc-hu-ls | 2025-07-08 11:16 | 00:00:03 | |
| dc-hu-ls | 2025-07-08 12:02 | 00:02:23 | |
| dc-hu-ls | 2025-07-08 14:39 | 00:00:32 | |
| dc-hu-ls | 2025-07-08 15:18 | 00:00:29 | |
| dc-hu-ls | 2025-07-08 16:14 | 00:00:01 | |
| dc-hu-ls | 2025-07-08 16:22 | 00:00:07 | |
| dc-hu-ls | 2025-07-09 09:54 | 00:00:08 | |
| dc-hu-ls | 2025-07-09 10:18 | 00:00:05 | |
| dc-hu-ls | 2025-07-09 10:29 | 00:00:06 | |
| dc-hu-ls | 2025-07-09 11:10 | 00:21:00 | |
| dc-hu-ls | 2025-07-12 14:57 | 00:00:01 | |
| pcs-com-ls | 2025-07-12 14:58 | 00:00:01 | |
| dc-hu-ls | 2025-07-12 19:56 | 00:00:01 | |
| pcs-com-ls | 2025-07-15 12:23 | 00:00:01 | |
| dc-hu-ls | 2025-07-16 03:57 | 00:00:05 | |
| dc-hu-ls | 2025-07-19 16:34 | 00:00:42 | |
| dc-hu-ls | 2025-07-19 18:06 | 00:00:38 | |
| dc-hu-ls | 2025-07-22 13:46 | 00:00:24 | |
| dc-hu-ls | 2025-07-22 14:15 | 00:01:04 | |
| pcs-com-ls | 2025-07-23 18:45 | 00:00:01 | |
| pcs-com-ls | 2025-07-24 02:13 | 00:00:01 | |
| dc-hu-ls | 2025-07-25 10:19 | 00:00:29 | |
| dc-hu-ls | 2025-07-26 10:40 | 00:00:02 | |
| dc-hu-ls | 2025-07-26 11:33 | 00:00:01 | |
| dc-hu-ls | 2025-07-26 11:57 | 00:00:01 | |
| dc-hu-ls | 2025-07-26 12:23 | 00:00:01 | |
| pcs-com-ls | 2025-07-26 13:14 | 00:00:01 | |
| dc-hu-ls | 2025-07-26 13:30 | 00:00:01 | |
| dc-hu-ls | 2025-07-26 13:35 | 00:00:01 | |
| pcs-com-ls | 2025-07-27 12:21 | 00:00:01 | |
| dc-hu-ls | 2025-07-28 13:29 | 00:00:01 | |
| dc-hu-ls | 2025-07-28 13:44 | 00:00:01 | |
| pcs-com-ls | 2025-07-30 20:36 | 00:00:01 | |
| pcs-com-ls | 2025-08-24 22:00 | 00:00:35 | |
| pcs-com-ls | 2025-08-26 12:16 | 00:00:01 | |
| pcs-com-ls | 2025-08-31 11:03 | 00:00:06 | |
| dc-hu-ls | 2025-09-03 16:29 | 00:00:01 | |
| pcs-com-ls | 2025-09-05 09:38 | 00:00:02 | |
| dc-hu-ls | 2025-09-06 00:48 | 00:00:44 | |
| pcs-com-ls | 2025-09-06 00:49 | 00:00:01 | |
| pcs-com-ls | 2025-09-06 00:57 | 00:00:36 | |
| dc-hu-ls | 2025-09-06 01:36 | 00:00:03 | |
| pcs-com-ls | 2025-09-06 01:37 | 00:00:01 | |
| pcs-com-ls | 2025-09-06 01:43 | 00:00:01 | |
| dc-hu-ls | 2025-09-06 01:45 | 00:00:01 | |
| dc-hu-ls | 2025-09-06 02:00 | 00:06:45 | |
| pcs-com-ls | 2025-09-06 02:01 | 00:06:45 | |
| dc-hu-ls | 2025-09-06 09:10 | 00:00:01 | |
| pcs-com-ls | 2025-09-06 09:32 | 00:00:12 | |
| dc-hu-ls | 2025-09-06 20:48 | 00:00:01 | |
| dc-hu-ls | 2025-09-07 16:38 | 00:00:01 | |
| dc-hu-ls | 2025-09-07 17:13 | 00:00:01 | |
| dc-hu-ls | 2025-09-11 20:25 | 00:00:01 | |
| dc-hu-ls | 2025-09-12 00:31 | 00:00:01 | |
| dc-hu-ls | 2025-09-12 00:37 | 00:00:06 | |
| dc-hu-ls | 2025-09-12 00:47 | 00:00:10 | |
| dc-hu-ls | 2025-09-14 01:25 | 00:00:01 | |
| pcs-com-ls | 2025-09-15 10:49 | 00:00:01 | |
| dc-hu-ls | 2025-09-18 00:01 | 00:00:01 | |
| dc-hu-ls | 2025-09-27 13:17 | 00:00:22 | |
| dc-hu-ls | 2025-09-27 14:12 | 00:00:01 | |
| dc-hu-ls | 2025-09-27 16:00 | 00:00:28 | |
| dc-hu-ls | 2025-10-02 22:13 | 00:00:02 | |
| dc-hu-ls | 2025-10-02 22:28 | 00:00:02 | |
| dc-hu-ls | 2025-10-04 22:33 | 00:00:01 | |
| pcs-com-ls | 2025-10-05 16:20 | 00:00:01 | |
| pcs-com-ls | 2025-10-07 08:45 | 00:00:02 | |
| pcs-com-ls | 2025-10-07 08:51 | 00:00:01 | |
| pcs-com-ls | 2025-10-07 11:03 | 00:00:04 | |
| pcs-com-ls | 2025-10-07 18:23 | 00:00:02 | |
| pcs-com-ls | 2025-10-07 18:29 | 00:00:01 | |
| pcs-com-ls | 2025-10-07 19:02 | 00:00:01 | |
| pcs-com-ls | 2025-10-07 19:14 | 00:00:01 | |
| pcs-com-ls | 2025-10-09 09:09 | 00:00:01 | |
| pcs-com-ls | 2025-10-09 12:01 | 00:00:01 | |
| pcs-com-ls | 2025-10-10 00:01 | 00:00:01 | |
| pcs-com-ls | 2025-10-12 09:58 | 00:00:01 | |
| dc-hu-ls | 2025-10-21 11:54 | 00:00:02 | |
| pcs-com-ls | 2025-10-22 09:55 | 00:00:03 | |
| pcs-com-ls | 2025-10-23 03:29 | 00:00:01 | |
| pcs-com-ls | 2025-10-26 11:23 | 00:00:01 | |
| pcs-com-ls | 2025-10-26 15:24 | 00:00:01 | |
| pcs-com-ls | 2025-11-01 14:53 | 00:00:01 | |
| pcs-com-ls | 2025-11-01 16:01 | 00:00:01 | |
| pcs-com-ls | 2025-11-02 14:20 | 00:00:01 | |
| pcs-com-ls | 2025-11-05 10:06 | 00:00:01 | |
| pcs-com-ls | 2025-11-07 23:12 | 00:01:40 | |
| pcs-com-ls | 2025-11-08 10:18 | 00:00:22 | |
| dc-hu-ls | 2025-11-08 14:58 | 00:00:06 | |
| pcs-com-ls | 2025-11-08 15:05 | 00:00:01 | |
| pcs-com-ls | 2025-11-08 16:45 | 00:00:06 | |
| dc-hu-ls | 2025-11-08 18:33 | 00:00:01 | |
| pcs-com-ls | 2025-11-08 18:47 | 00:00:06 | |
| dc-hu-ls | 2025-11-22 02:32 | 00:00:01 | |
| dc-hu-ls | 2025-11-22 03:19 | 00:00:01 | |
| dc-hu-ls | 2025-11-22 04:21 | 00:00:01 | |
| dc-hu-ls | 2025-11-22 04:29 | 00:00:01 | |
| pcs-com-ls | 2025-11-26 12:46 | 00:00:01 | |
| pcs-com-ls | 2025-12-02 14:42 | 00:00:36 |
What is this?
This site is the Down Detector service for our software PointCloudScene. The goal here is to give our users a simple tool which makes it easier to confirm or deny whether the license service is operable.
So whenever PCS drops you an exception message referring to the License Server, you can quickly check if there is a service availability error or something else.
How it is working?
First, for a more seamless experience, we are running the license service redundantly. During daily operations, PCS can switch between license servers without hesitation. That means our users are only in trouble if both services are down.
We are collecting and presenting multiple types of data and applying different metrics during the monitoring of the servers:
- First, we send several pings to each server every minute and record the response times. These provide data for the Past hours chart's curves (Avg. Pings).
- Second, we are initiating direct calls to the services and processing the responses. Based on the response we can determine the status of the servers (Up / Down). These situations are presented on the topmost table (Current availability), and on the chart as a step-diagram on the bottom (Availability).
- Last, but not least we are storing each 'Down' incident for the long term and presenting (if any) them at the last table (Incidents).
About the chart
The chart displays data from the last hour. You can switch off and on each visualized dataset by clicking/tapping on the respective legend field.