#rootcause
Live, measured metrics for the hashtag #rootcause from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rootcause
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 09:45 UTC0 uses by 0 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 09:45 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:45 UTCEverything below is measured over the latest 40 public posts (spanning ~16071 hours).
Posting hours (UTC) — busiest: 00:00
Languages: English (37) · German (2) · Italian (1)
Avg boosts / post: 0.8
Top of the latest posts
I noticed some time ago that 3 #Mastodon features had stopped working on my blog. Each of them seemed like a separate problem, but they had the same #rootcause. In this blog post, I aim to describe these issues and propose a simple solution
The Scraper-Base-Kit is now Private. After reviewing the velocity of our global ingest, I’ve decided to move the base-kit to the Private Core. The engine is too fast, the footprint too small. This thing is like a shotgun that fires once at
I always appreciate a good write-up of outages and Google had one for their outage on the 12th. They put in new policies around quota handling, but then that had some unexpected side effects. Since they didn't have a feature flag to turn it
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/rootcause