#netflow
Live, measured metrics for the hashtag #netflow from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #netflow
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-09-26 13:43 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-09-26 13:43 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-26 13:43 UTCEverything below is measured over the latest 40 public posts (spanning ~20116 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (19) · Russian (14) · German (4) · Arabic (1) · Spanish (1)
Avg boosts / post: 0.5
Top of the latest posts
Yes, You Too Can Be An Evil Network Overlord - On The Cheap With OpenBSD, pflow And nfsen https://nxdomain.no/~peter/yes_you_too_can_be_an_evil_network_verlord.html A story about network metadata and #openbsd, originally from 2014, good for
Detect sudden NetFlow traffic spikes with nfdump. Aggregate 5-min windows from a collector, filter flows over 10 MB, group by source/dest IPs, and sort results. Nfdump reads binary records, applies BPF filters, and computes aggregates on th
Wrote up the full story behind flowsimulator-go — why random NetFlow tuples fail everything after the parser, how ordered session chains work, and what the tool deliberately does NOT do: https://dev.to/stefan_sabolowitsch_3bd10/stop-testing
What “netflow” means
WikipediaNetFlow is a feature that was introduced on Cisco routers around 1996 that provides the ability to collect IP network traffic as it enters or exits an interface. By analyzing the data provided by NetFlow, a network administrator can determine things such as the source and destination traffic, class of service, and the causes of congestion. A typical flow monitoring setup consists of three main components:Flow exporter: aggregates packets into flows and exports flow records towards one or more fl
“NetFlow” on Wikipedia (CC BY-SA) →#netflow across platforms
every network with a public tag surfaceFollow #netflow 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/netflow