Orbit
Configure PulseHA public egress regions and placement.
Pulse Orbit is PulseHA’s public egress: points of presence (PoPs) grouped into regions that devices can use as exit nodes. Network → Orbit shows which regions your tenant has opted into, Orbit Settings changes that set, and Orbit Routing rules steer specific subjects to a region. Orbit does not replace a private gateway beside an internal application.

The header counts active regions, the map plots every PoP region, and the table marks each one Opted in or Available.
Before you start#
- Viewing Orbit pages needs
policies:view. Changing settings and routing rules needspolicies:update(rules also usepolicies:createandpolicies:delete). Without update rights the settings page reads You can view Orbit settings, but your role cannot change them. - Orbit is unavailable to tenants in the evaluation period. The pages show Pulse Orbit is disabled during the evaluation period. Contact sales to continue. and the control plane rejects opt-ins.
- Not-for-resale lab tenants have a fixed region allowlist set by PulseHA. Their settings page is read only and the console never sends an opt-in or opt-out.
- What you can enable depends on your plan. Core does not include Orbit, and the control plane rejects an opt-in with region is not included in this tenant’s Orbit plan. Business can choose any region, with up to three enabled at a time. Enterprise can enable every region.
Enable Orbit and choose regions#
- Open Network → Orbit and click Settings.
- Under General turn on Enable Orbit.
- Under Allowed Regions select the regions Orbit may route through. On Business, select up to three; the page shows a count such as 2 of 3 regions selected. On Enterprise, leave the list empty to allow any region.
- Click Save Changes. The console shows Orbit settings saved and returns to the Orbit page, where the header reads Active in N of M regions.
- Create or edit an egress policy that permits or prefers Orbit. Orbit appears there as a destination once regions are enabled.
The Regions table on the Orbit page lists Region, Geography and Status (Opted in or Available). The map above it draws the same data.

Settings holds the Enable Orbit switch and the Allowed Regions picker.
Steer placement with routing rules#
Routing rules choose which opted-in region a subject lands in. They do not decide whether Orbit is used; egress policies and Orbit settings do.
- Open Network → Access, switch to Orbit Routing and click Add Routing Rule.
- Under Details enter a Name, optional Description and Priority (lower numbers win when several rules match).
- Under Subjects add one or more rows: Entire Tenant, User, Role, Group or Device, picking the target for each.
- Under Conditions optionally select Source countries. Leave empty to match any location.
- Under Action pick the Target Orbit region and a Selection mode: Require (devices must egress from the target region; refused if it has no capacity), Prefer (try the target, fall back to automatic selection) or Auto (nearest) (use the geo-nearest opted-in region, falling back to the target).
- Click Create Rule.
The control plane requires the target region to be opted in. Otherwise saving fails with the region X is not enabled for your organization. Enable it in Pulse Orbit under Configure, then save this rule again. The table marks a rule whose target falls outside the tenant’s effective regions (opt-ins intersected with the tenant egress policy’s narrowing) with an ineffective chip; such a rule is skipped and devices are placed automatically.

A rule names its subjects, optional source countries, then the target region and selection mode.
Rules are evaluated in priority order; the first match wins. If no rule matches, or rule lookup fails, the device is placed automatically in the geo-closest opted-in region. The Devices column counts devices currently placed by each rule, and each device’s drawer shows Egress region, Placed by and a Converged, Pending or Degraded status.

Rules sort by priority and the Devices column counts devices placed by each rule; a rule whose target region is outside the effective regions is marked ineffective.
Reference#
| Setting | Values |
|---|---|
| Enable Orbit | On or off. Enabled means at least one region is opted in |
| Allowed Regions | Region codes such as eu-west-2 (London), shown with metro labels |
| Pulse Orbit Regions (egress policy) | A compliance bound: devices in that scope may only use these regions |
| Target Orbit region (routing rule) | A preference: where matching devices are placed |
| Selection mode | Require, Prefer, Auto (nearest) |
Narrowing in an egress policy says “may only”; a routing rule says “prefer”. Routing never overrides narrowing.
Troubleshooting#
- “Live region status is unavailable” banner. The control plane could not be reached, so opt-in state may be stale. The settings page disables editing until a reload confirms the current state. Do not infer availability from the map.
- “Orbit is not enabled yet” on the Orbit page. No region is opted in. Open Settings, select regions, save, then add Orbit to an egress policy.
- “No Orbit regions available. Contact support to enable Orbit for your tenant.” The region catalog is empty for this tenant.
- Egress Policies shows “Orbit resolves to no eligible PoPs”. Every opted-in region is excluded by the tenant egress policy’s Pulse Orbit Regions, or the opted-in regions have no active PoP. Widen the narrowing or opt into another region. Agents stand Orbit down in this state.
- “Your plan allows 3 Orbit regions at a time.” Business has three regions enabled already. Remove one, then add the region you want; you can swap regions as often as you need. If you had more than three enabled before the limit applied, you keep them and can remove them, but cannot add another until you are under three.
- “Orbit settings partially saved: N region updates failed.” Some region opt-ins did not apply. Reopen settings, review the list and save again.
- A routing rule shows “ineffective”. Its target region is outside the effective regions. Change the target, opt into the region, or widen the narrowing under Egress Policies.
- A lab tenant cannot change regions. Expected. The allowlist is set by PulseHA; the console cannot opt in or out.
Private application traffic still needs a private gateway, a published service and an access policy.