Status

Whether the parts of dids.lol are working, and what it means for your site when one of them is not.

Current status

The machine-readable answer is at /status.json, aggregated from each component’s own health probe. The operator’s status page carries incident history and any maintenance that is planned.

The three parts

The origin

Serves your visitors. It reads a snapshot and object storage and nothing else, so it stays up when the rest does not.

The control plane

Domain registration, verification, validation, and this site. When it is down you cannot register or publish, but published sites keep serving.

The indexer

Watches the firehose and builds snapshots. When it is behind, new records take longer to go live; already-published sites are unaffected.

Degrading safely

The design goal is that a failure upstream never takes your site off the air. If the firehose stops, published sites keep serving the snapshot they are on. If the indexer stops, the origin keeps serving the last activated snapshot. If the database is unavailable, the origin still answers from its cached pointers.

What does break, immediately and visibly, is publishing: a new record will not be picked up until the indexer is back.

Reporting a problem

If your site is down and the status page says everything is fine, check that your DNS still points at go.dids.lol and that your record is still in your repository. If both are true, write to [email protected] with the domain.