# Starlink’s 15-second beat.

A dish changes satellites on a fixed beat, and its delay can jump at each change. Fenris finds the beat from the link’s own round trips, and steps calls around each jump.

_Every device · Your server · On by default_ 

One minute on a dish and a 5G link 

The dish’s round trip jumps at seconds 12, 27, 42 and 57 of each minute. Once the beat is learned, a call steps onto the 5G around each jump.

At first Fenris only watches. Three beats in a row, and the pattern is known.

The call steps onto the 5G around each jump. A download stays on the dish, and losses inside a jump do not slow it.

**Fig. 1 · Example** The beat is to scale and comes from published measurements of Starlink (arXiv 2310.09242, RIPE Labs). The jumps’ height and the steps’ width are illustrative.

## What happens

1. Fenris watches each link’s round trips. It goes by what it measures, never by a link’s name or label.
2. Jumps that come every 15 seconds, three beats in a row, are a pattern. From then on Fenris knows when the next one is due.
3. Calls, games and name lookups step onto another link just before each jump, and back just after.
4. A download stays on the dish. Losses inside a jump are not taken for a crowded link, so they do not slow it.
5. Both ends learn the beat. What your server sends back steps around the jumps too.

## What it costs

Every beat, another link carries the call for a moment.

**Data**

Say an hour of voice is 50 MB. The steps put a few megabytes of it on the other link. _Example:_ 

**Delay**

During a step the call takes the other link’s delay, which may be longer than the dish’s between jumps.

**Speed**

Nothing for a download. It stays on the dish through each jump.

## Turn it on

There is nothing to turn on: Fenris finds the beat by itself. These show it at work.

| To                                             | Command line                               | Router UI and app |
| ---------------------------------------------- | ------------------------------------------ | ----------------- |
| Watch each link, redrawn every second          | fenris top                                 | Links, the link   |
| List each path, with its round trip and losses | fenris status \--paths                     | Links             |
| See what Fenris did, and when                  | fenris activity                            | Activity          |
| Keep marked calls off the dish altogether      | fenris rules add \--dscp 46 \--links wwan0 | Rules, Add rule   |

### Where to find it

**Router UI** Home. Each link, with its round trip.

The router’s own page, Home, with example data: connected, two of three links up, the speed over both as one, and each link with its share.

**The app** Home.

The Android app’s Home screen, with example data: protected, two links up, and each link’s share of the traffic.

**The console** A device’s page. Each link’s round trip, its loss and the drops absorbed.

The console’s page for one device, with example data: its state, its throughput, the drops its links absorbed, and each link side by side.

**The product** Three of its own screens, with example data.

## What it keeps

Nothing new. The beat is worked out from round trips that each end measures anyway, and it is held in memory while the session lasts. Your server keeps how each link is doing for 24 hours, in memory.

[Everything your server keeps](https://fenris.network/privacy#kept)

## Where it stops

**Drops off the beat**

A tree, a sail or a mast in the way causes drops that are not on the beat. Those are handled like any link that goes quiet.

**A second link**

A step needs somewhere to go. Without another link that is good for calls, the call stays on the dish through the jump.

**The first beats**

At first Fenris only watches. The pattern is known after three beats in a row.

**Where the beat comes from**

The 15-second beat is from published measurements of Starlink (arXiv 2310.09242, RIPE Labs). Fenris reads it from your own link.

## Related
