All Systems Operational
Platform Status
Operational
Frontend
Operational
Device Hub
Operational
Remote Access
Operational
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.
Scheduled Maintenance
June Release Jun 2, 2026 09:00-10:00 CEST
New Features
--------------
1. Enhanced access control for remote access – The system now accepts a new syntax for resource definitions within the remote-access:connect permission. This allows you to restrict permissions to a much more granular level:
- Allowing tunnels only to specific ports (e.g., "*/tunnel(proto=tcp;port=80,443)")
- Controlling access to the remote console (e.g., "*/console")
- Remotely triggering a run of the qbee-agent (e.g., "*/reload")
- Transferring files to and from specific paths on the device (e.g., "*/copy(direction=up,path=/etc/my-app/)")
This provides much finer control over who can utilize remote access and for what purpose.
2. Auto-tagging of devices during bootstrapping – The bootstrap key section now allows you to define a list of tags per bootstrap key. These tags will automatically be applied to any device using that specific bootstrap key to join the fleet.
3. Bootstrap key descriptions – The system now supports defining descriptions for each bootstrap key, making the management of multiple keys much easier.
4. Increased tag limit – Increased the limit of tags per node from 20 to 30.
Fixes
-----
1. Fixed the unassigned devices list link on the dashboard page.
2. Fixed a UI consistency issue when rendering a list of devices with predefined filters.
3. Improved the password reset flow to rate-limit the frequency of requested password resets per email address.
4. Improved the rendering and sorting performance of the device list in the UI.
Maintenance
-------------
1. Performed regular system patching and infrastructure updates.
2. Internal Data Model Optimization – Optimized internal data models to improve the performance of the inventory and node APIs. This change requires a background data migration. Under certain conditions, this may cause inventory data to be temporarily eventually consistent (meaning new changes might appear with a slight delay). The data migration is estimated to take 15–20 minutes, after which data will be fully consistent.
Posted on Jun 01, 2026 - 13:18 CEST
--------------
1. Enhanced access control for remote access – The system now accepts a new syntax for resource definitions within the remote-access:connect permission. This allows you to restrict permissions to a much more granular level:
- Allowing tunnels only to specific ports (e.g., "*/tunnel(proto=tcp;port=80,443)")
- Controlling access to the remote console (e.g., "*/console")
- Remotely triggering a run of the qbee-agent (e.g., "*/reload")
- Transferring files to and from specific paths on the device (e.g., "*/copy(direction=up,path=/etc/my-app/)")
This provides much finer control over who can utilize remote access and for what purpose.
2. Auto-tagging of devices during bootstrapping – The bootstrap key section now allows you to define a list of tags per bootstrap key. These tags will automatically be applied to any device using that specific bootstrap key to join the fleet.
3. Bootstrap key descriptions – The system now supports defining descriptions for each bootstrap key, making the management of multiple keys much easier.
4. Increased tag limit – Increased the limit of tags per node from 20 to 30.
Fixes
-----
1. Fixed the unassigned devices list link on the dashboard page.
2. Fixed a UI consistency issue when rendering a list of devices with predefined filters.
3. Improved the password reset flow to rate-limit the frequency of requested password resets per email address.
4. Improved the rendering and sorting performance of the device list in the UI.
Maintenance
-------------
1. Performed regular system patching and infrastructure updates.
2. Internal Data Model Optimization – Optimized internal data models to improve the performance of the inventory and node APIs. This change requires a background data migration. Under certain conditions, this may cause inventory data to be temporarily eventually consistent (meaning new changes might appear with a slight delay). The data migration is estimated to take 15–20 minutes, after which data will be fully consistent.
Posted on Jun 01, 2026 - 13:18 CEST