#relays
Live, measured metrics for the hashtag #relays from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #relays
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 05:23 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 05:23 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:23 UTCEverything below is measured over the latest 40 public posts (spanning ~13353 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (29) · German (5) · Portuguese (2) · Danish (1) · Chinese (1)
Avg boosts / post: 2
Top of the latest posts
When you're a Very Important user on the #Fediverse, and you spend 3+ hours writing dozens of responses about how something is opt-in actually (it isn't), and that you understand consent (after-the-fact), maybe you should take the next 3 ho
Folks self-hosting on the fediverse: I am setting up a #GoToSocial instance for myself only. It looks like #relays are the answer for populating timelines and making sure your own posts find their way beyond your bubble. But I am wondering
tags.pub has unsubscribed from all open relays. Evan recognises there's a mismatch of expectations on what Relay 2 relay, R2R connections should be like. It should not have taken as long as it did but it's done. However this is ultimately a
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/relays