Regional availability
Every checking location measures independently. The location and its incident remain visible in the notification.
For hosting providers
Is the service unreachable in one region, or is the host itself the problem?
Uptimo connects checks from several locations with measurements from Linux and Windows hosts.
The hosted service operates the external checking locations; the optional agent provides the internal view. Routing, DNS, TLS, a full disk, and a stopped container initially look the same to a customer: the service is unavailable.
Availability alone does not explain the cause
An external check shows the customer's view. An agent shows CPU, memory, filesystems, network, sensors, GPUs, and optional Docker data inside the affected host.
Uptimo does not turn these signals into a fabricated automatic root cause. It presents them in the same operational context so a person can decide faster.
Signals that belong together
Host state
Per-core CPU, memory, swap, load, filesystems, inodes, block devices, and network show internal state.
Container state
With Docker collection enabled, state, health, restarts, image, CPU, memory, and network appear per container.
Customer communication
Status pages group components and keep incidents or maintenance in a continuing timeline.
From the first error to a defensible update
Every step remains inspectable. A silent checking location must not look like a customer outage.
Use the right check
HTTP, ping, TCP, DNS, or TLS tests what must actually be reachable for that service.
Keep locations separate
Every location keeps its own status, failure count, and incident. A regional issue remains visibly regional.
Place host metrics beside it
The outbound agent provides internal state without opening an inbound port.
Trigger alerting and communication
Confirmed states go to the right channel and can be accompanied by a written status update.
Clearly bounded
Important limits
Uptimo operates the checking locations
The countries actually available at launch are not invented in advance or promised as fixed coverage.
Docker remains a deliberate permission
The Docker socket is highly privileged. Container data and container rules are therefore opt-in.
Virtualisation is detection, not API integration
QEMU, KVM, Proxmox, or VMware can appear as a reported environment. Uptimo does not control the hypervisor.
FAQ
Hosting-provider questions
Can one monitor run from several checking locations?
Yes. Locations are assigned per monitor. Each one keeps its own schedule, status, failure count, and incident.
What happens if a checking location itself goes silent?
A location that reports nothing for 90 seconds is removed from the aggregate status. A platform problem should not appear as an outage of the customer's service.
Does the server agent open a port?
No. The agent sends outbound to Uptimo and accepts no inbound connections.
Can Uptimo monitor Docker containers?
Yes. You enable Docker socket access and container rules per server; both remain off by default.
Inspect the measurement path for your hosts.
The platform page separates actual support, recognised environments, and deliberate security boundaries.