<b>Servers have a heartbeat, and it's geographic</b>

<b>Servers have a heartbeat, and it's geographic</b>

Activity isn't uniform across the day, and the shape of the curve carries more diagnostic information than the average.

<b>What the data shows</b>
Hourly message histograms across servers reveal that "global" communities frequently have a single dominant timezone cluster hiding under the label — one peak, one trough, and long dead hours. Servers that <i>felt</i> alive 18+ hours a day almost always had at least two distinct geographic clusters producing a double-peaked curve. Single-peak servers had longer dead zones where conversation died and didn't restart.

<b>Why it happens</b>
Conversation needs overlapping presence. A single timezone cluster guarantees a daily window where no one's around to sustain a thread, and a thread that dies overnight rarely resurrects. Two clusters hand the baton across the clock. Telegram's async, feed-like consumption tolerates dead hours far better — a post at 3am still gets seen at 9am — which is a structural advantage for genuinely global audiences.

<b>The caveat</b>
Locale data is inferred and noisy; VPNs and night-owls blur it. And a double peak could just be a proxy for "bigger," which brings its own activity.

Open question: should a single-timezone server deliberately recruit a second cluster — or specialize and accept the dead hours rather than dilute its core?