#fortibleed
Live, measured metrics for the hashtag #fortibleed from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fortibleed
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-30 10:54 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-30 10:54 UTCNo related tags with measured usage found for #fortibleed.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 10:54 UTCEverything below is measured over the latest 40 public posts (spanning ~364 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (24) · German (6) · Italian (5) · Polish (2) · Dutch (2) · Spanish (1)
Avg boosts / post: 2.2
Top of the latest posts
Fortinet appear to be telling press the #Fortibleed breach is made up of prior breaches and brute forcing.. but I’ve seen the breach data and it includes many passwords not in prior dumps, and I’ve worked with impacted orgs and they report
Some kind #FortiBleed victims got me to look at their situations. Some IOCs performing remote config dumps: 193.8.186.7 80.75.212.113 213.21.239.65 Look for inbound TCP traffic to Fortigate devices. If seen log into the devices and look for
#GAYINT list of impacted #FortiBleed domains (this is basically email addresses of admin accounts on the device btw) https://blog.gayint.org/intel/fortibleed.txt
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/fortibleed