A monitor is one Starlink site in your organization. While the dish is connected, Orbimon Edge samples about once per second; your organization upload interval sets how often each Edge sends a batch to Orbimon. The dashboard turns that stream into charts, maps, and events.
See Upload interval for how cadence affects charts, alerts, and offline detection. On Billing, the same value is listed per monitor.
Monitor status
Orbimon computes one status per monitor in the API (apps/api/src/lib/monitor-health.ts). The dashboard and public list endpoints return the same value.
| Status | Meaning |
|---|---|
| Online | Telemetry arrived within the offline window and the link looks healthy. |
| Degraded | Telemetry is recent, but an Orbimon Alert is active, link quality is poor, or ingest cadence has gaps. |
| Outage | Telemetry is recent, but Starlink reports the dish down (disconnected state, sustained total packet loss with no throughput, or an explicit outage flag). |
| Offline | No telemetry within max(5 minutes, 2× the org upload interval + 1 minute). |
| Status unknown | The latest read failed temporarily. Historical charts may still load. |
Degraded quality thresholds on the latest sample: obstruction at or above 10%, latency at or above 80 ms, packet loss at or above 5% (below the outage cutoff), non connected dish states such as ATTEMPTING or OBSTRUCTED, or any Starlink dish alert code on the sample.
Outage uses packet loss at or above 99% with negligible throughput, DISCONNECTED state, or an outage alert on the sample.
The same rules apply to Orbimon Edge and Starlink Enterprise API monitors. Demo fleet monitors use the same logic; is_demo only controls the Demo data badge.
Charts on monitor detail
Choose a time range from 15m, 1h, 6h, 24h, 2d, 7d, or 30d.
| Chart / panel | What it shows |
|---|---|
| Throughput | Download and upload in Mbps |
| Latency | Round-trip latency to the Starlink point of presence |
| Power | Dish power draw in watts when samples include it |
| Obstruction (side panel) | Sky map, obstruction percentage, and uptime from the dish |
| Events and outages | Edge, dish, and Starlink events on a timeline |
Shaded bands on the throughput, latency, and power charts mark outages and disconnects. Micro-outages are short drops that may appear in the timeline and in the daily digest without triggering a long-outage alert.
Speed tests
Speed tests are optional per monitor (off by default for new monitors). Organization owners, admins, and staff with monitor-management access turn them on in Monitor settings and choose an interval of every 6, 12, or 24 hours (never faster than the organization minimum). All members can see whether speed tests are on and view historical results. When speed tests are off, the monitor detail page omits the Speed tests block entirely (including public shares and Snapshot).
When enabled, the Edge runs scheduled Cloudflare throughput tests on that interval and results appear under Speed tests. Each test uses a small amount of Starlink data.
How long Orbimon keeps data
Retention is the same for every organization:
| Data | Retention |
|---|---|
| Per-second samples | 30 days |
| 1 minute rollups | 90 days |
| Hourly rollups | 365 days |
| Daily rollups | Kept indefinitely |
| Dish events and speed tests | 365 days |
| Obstruction maps | 180 days |
The dashboard chart picker shows recent windows; older history uses coarser rollups. The HTTP API also limits how wide a range you can request per resolution (for example raw metrics up to 12 hours). See Monitors API.
Offline buffering on the Edge
If the Edge loses internet, it keeps collecting readings locally and uploads them when the link returns. Orbimon Edge holds about 7 days of compressed data on the SD card before the oldest buffered points are dropped.
Micro-outages
Micro-outages are brief Starlink drops shorter than your Starlink outage alert threshold. They still appear in the events timeline. When the daily digest is enabled, they can be included in the summary email with dish restarts and firmware updates.
API access
Integrations use a monitor token or organization token to read the same metrics programmatically. See Monitors API.
Where Orbimon stores your data
Your data is stored in the European Union, in Germany, and every reading is copied to a fallback region, also in Germany. If the main region has trouble, Orbimon keeps serving your charts and the API from the fallback region. While that happens, status.orbimon.com shows it and recent charts may update with a short delay. See How we keep your data safe.