All Systems Operational

Uptime over the past 90 days. View historical uptime.
Platform Status Operational
90 days ago
100.0 % uptime
Today
Frontend Operational
90 days ago
100.0 % uptime
Today
Device Hub Operational
90 days ago
100.0 % uptime
Today
Remote Access Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Retirement of Legacy VPN Solution Mar 6, 2026 09:00-09:30 CET

As notified in September 2025, our legacy VPN solution will be retired on March 6, 2026.

Impact Summary
-----------------

Remote Access will no longer be available for devices running qbee-agent versions older than 2024.09.

Configuration management, monitoring, and inventory functionality will remain operational on these older agent versions.

To maintain remote access capabilities, please ensure your devices are updated to version 2024.09 or newer.

Should you have any questions or require assistance, please reach out to support@qbee.io
Posted on Mar 04, 2026 - 13:08 CET
Mar 4, 2026
March Release
Completed - The scheduled maintenance has been completed.
Mar 4, 09:30 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 4, 09:00 CET
Scheduled - New Features
--------------

1. Commit API now accepts a list of changes directly in the request payload, committing them without needing the Change API. These changes are committed in isolation, meaning any existing uncommitted changes will not be included. This improves workflows where parallel processes need to commit configuration changes independently.

2. Updated the look and feel of the REST API documentation.

3. Improved tracking of expected releases—the inventory API now returns a new property, config_status, with one of three values:

- queued – the device hasn't received the new config yet.
- processing – the device has received the config but hasn't applied it yet.
- applied – the device has successfully applied the current config.

The expected configuration commit ID will change when any of the following occur:

- Configuration changes (on the device, its ancestors, or tags).
- Device tree structure changes (tags changed, device moved to another group).
- File changes (for files referenced by the current device configuration).


Fixes
-----

1. Resolved a file streaming issue during RAUC updates for accounts created in February 2026 and those using Bring-Your-Own-CA.


Maintenance
-------------

1. Performed regular system patching and infrastructure updates.
Mar 3, 08:47 CET
Mar 3, 2026

No incidents reported.

Mar 2, 2026

No incidents reported.

Mar 1, 2026

No incidents reported.

Feb 28, 2026

No incidents reported.

Feb 27, 2026

No incidents reported.

Feb 26, 2026

No incidents reported.

Feb 25, 2026

No incidents reported.

Feb 24, 2026

No incidents reported.

Feb 23, 2026

No incidents reported.

Feb 22, 2026

No incidents reported.

Feb 21, 2026

No incidents reported.

Feb 20, 2026

No incidents reported.

Feb 19, 2026

No incidents reported.

Feb 18, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage