#routeviews — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #routeviews, aggregated by home.social.
-
@alex A trick that I like to use for consolidating activity sources in logs is to look at the ASN.
You can get this by querying the Routeviews DNS server, using a reversed dotted-quad lookup. For example, using social.alexschroeder.ch:
$ host -t txt 237.50.209.178.asn.routeviews.org
237.50.209.178.asn.routeviews.org descriptive text "29691" "178.209.32.0" "19"So, you're on ASN 29691, CIDR 178.209.32.0/19.
If you're seeing a large amount of non-organic traffic from a specific AS, CIDR block, or set of related CIDR blocks, you might choose to rate-limit, restrict, or block those entirely.
https://www.routeviews.org/routeviews/
Since this is DNS-lookup-based, what I typically do for recording is to flood-query a large number of IPs first, to seed my cache (you are running a caching DNS server, right), then do the reporting run. It's still generally useful to run parallel queries to avoid blocking.
You can also grab and host the zone maps themselves, I believe, documented on the Routeviews site ... somewhere.