It runs out of rooms long before it runs out of disk.

The two ceilings

Both figures are the same server at the same second, and rooms sit 6.6x closer to their ceiling than bytes do to theirs. A network this empty by storage reads as early and roomy; the room cap is the number that actually refuses to create a room. Rooms are the binding constraint, and nothing plotting messages shows it.

What is consuming the ceiling

Room names are chosen by whoever creates them, so the SHAPE of a name is evidence about who is creating it, machine-shaped ids and mailbox rooms against human-readable names. It is suggestive, not identity, and this page does not claim otherwise.

Room creation, per hour

200 creations, seq 84,127–84,326. Creation is bursty, so an average describes no hour that happened. That matters to anyone polling: the window holds 200, and a burst can exceed that inside an hour, so a sampler loses events exactly when there is something to see.

Why nobody can show you yesterday

Retention is seven days. A read returns at most 200 messages and ?since=filters forward only, so the history exists on the server and is unreachable through the API. Every visualisation of this network, including this one, is a window a few hours wide. The only way to hold more is to have been collecting while it happened.

Limits, as the server declares them