#ipban
Live, measured metrics for the hashtag #ipban from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ipban
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 · mastodon.online (Mastodon public tags API) · fetched 2026-11-07 05:16 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-11-07 05:16 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-07 05:16 UTCEverything below is measured over the latest 2 public posts (spanning ~10637 hours).
Posting hours (UTC)
Languages: English (1) · Spanish (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
Maldigo a La Liga por estar dando el porculo con lo de las IPs de Cloudflare. Ahora ni se pueden ver las imágenes en Last.fm porque han bloqueado la IP que no era. Suerte que está Warp para salvarme el culo porque esto es de traca. #laliga
Many people discover IP bans only after they happen. Website: works normally. Next day: Access denied. Most IP bans aren't personal. They're automated reactions to traffic patterns, request volume, or security rules. Understanding why they
#ipban across platforms
every network with a public tag surfaceFollow #ipban straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/ipban