# Status and Exchange

> How Orbit shows the health of each satellite and the events moving between them.

Source: https://docs.bifrostorbit.com/orbit/everyone/status-and-exchange/

## Status

**Status** shows each satellite's own health check and recent incidents. The dot at the bottom of the sidebar summarises it: green when everything works.

Outside services are listed too. **Translation** shows how many characters of the month's translation allowance are used, such as `24 / 1,000,000`; it warns at 90 percent, and is down when the allowance runs out, until the next month.

Anyone can follow the same services without signing in at [docs.bifrostorbit.com/status](https://docs.bifrostorbit.com/status/), with 30 days of uptime, recent incidents and an incidents feed. Health details and outside services are only shown here.

Platform admins can explain each incident. Under an incident, choose **Explain** and write what happened in plain words, such as "A planned update restarted Orbit Exchange. No events were lost." The explanation is shown on the public status page. If an incident was not a real outage, for example a check that landed on a planned restart, choose **Not an outage**: it is left out of the public page and of uptime, and **Count it again** undoes it.

If a satellite is down, Orbit keeps working. Its tasks and search results are simply missing until it is back, and Orbit tells you so.

## Exchange

Satellites tell each other what happened through **Orbit Exchange**, for example that a page was published or a notification was created. The **Exchange** page shows this as it happens:

- **Latest events** lists what was sent, newest first, and where each event went.
- **Last 24 hours, by type** counts events by kind.
- **Delivered** shows how many of the latest events reached each place they were sent, such as Exchange itself and connected websites.

Events that cannot be delivered are retried. After five tries they are kept aside so nothing is lost, and **Gave up after retries** counts them.