octoja Availability & Status

What to do when octoja is unreachable or a page does not load

How to check whether octoja is available

Current status: Check status.octoja.de for the current status of octoja.

If you are having trouble logging in or a page is not loading, work through the following checks before escalating the issue.

Refresh the page and wait 30 seconds.
Check your internet connection by opening another website.
Try a different browser, for example Chrome or Edge. Both are Chromium-based, which is what octoja is tested against.
Clear the browser cache and sign in again.
Contact your IT provider if the issue continues. Include what you were doing, what you saw, and when it started.

Common signs of a problem:

The page does not load after 30 seconds
You see a blank screen after logging in
Devices appear offline unexpectedly
A check that should fire does not produce a result

Platform behavior and requirements

The following sections describe how octoja behaves in specific situations and which technical requirements apply.

Connection and availability

Agent requires an active connection	Terminal sessions, live performance data, and service/process management are only available while the device is connected to the platform
Offline check results are discarded	The agent continues running checks while disconnected and reconnects automatically, retrying with a short backoff (a few seconds, up to about every 30 seconds). However, check results collected while the platform is unreachable are not queued — they are discarded. Monitoring resumes normally once the connection is restored, but there will be a gap in results for the disconnected period
Short drops do not mark a device offline	A device that is back within 30 seconds keeps its previous status, so a brief network blip or an agent update does not turn the Device online check critical. After octoja itself restarts, the same hold lasts about five minutes — an outage that begins in that window can be reported a few minutes late
No local relay or proxy	octoja agents connect directly to the web service over HTTPS. There is no local relay, broker, or proxy between the agent and the platform

Data and history

Live telemetry is not stored	Live telemetry (CPU, memory, disk charts) shows the current state in real time and is not kept as a performance trend. Check results are a different matter: they are kept for 30 days by default and feed the per-check history on the Checks tab and the report widgets built on it — Check Status History, Check Status Timeline, Availability and the SLA figures (Service Uptime, Mean Time to Resolve, SLA Incidents)
Where device events are recorded	Open Activities on the device detail page and pick Logs; the same data is also available through the Asset Logs API. Hardware and software changes are listed under Activities → Inventory History
Real-time telemetry update interval	Live performance data updates every 2 seconds while you are viewing a device. Check results run on their own configured interval (typically minutes to hours)

Live telemetry is not stored

Live telemetry (CPU, memory, disk charts) shows the current state in real time and is not kept as a performance trend. Check results are a different matter: they are kept for 30 days by default and feed the per-check history on the Checks tab and the report widgets built on it — Check Status History, Check Status Timeline, Availability and the SLA figures (Service Uptime, Mean Time to Resolve, SLA Incidents)

Where device events are recorded

Open Activities on the device detail page and pick Logs; the same data is also available through the Asset Logs API. Hardware and software changes are listed under Activities → Inventory History

Real-time telemetry update interval

Live performance data updates every 2 seconds while you are viewing a device. Check results run on their own configured interval (typically minutes to hours)

Platform requirements

Agent installation	Requires administrator rights on the target device
Browser support	A current stable release of a Chromium-based browser — Chrome (recommended), Edge, and the rest of the Chromium family. Firefox and Safari show an Unsupported browser notice at sign-in that you acknowledge with I understand — continue anyway. See Supported Browsers for the full picture
Operating system support	Windows 10 or Windows Server 2016 and newer, macOS 12 (Monterey) and newer, and current Ubuntu and Debian releases. See the deployment articles for Windows, macOS, and Linux for the platform-specific requirements
S.M.A.R.T. checks	Read their attributes from the physical drive. A virtual disk does not pass those attributes through, so the check finds no readable S.M.A.R.T. data there; on Windows it falls back to the health status Windows itself reports for the disk

If something still does not work

Repeat the failed action once to confirm the issue.
Check whether the problem is limited to one browser or device.
Collect any error text or screenshots — see Gather logs for a support case for what to attach.
Send that information to your IT provider.

Related articles: Supported Browsers

Was this helpful?

Still need help? Ask the team