HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ipverse
as-ip-blocks
Systems & Infrastructure2025–2025
ipverse / as-ip-blocks

as-ip-blocks

Download IP block lists by ASN - network provider addresses, updated daily

2Distinct people
2Mentions
0Explicit recommenders
535GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Download IP block lists by ASN - network provider addresses, updated daily

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2025-12-22 14:37:00 UTC to 2025-12-22 15:54:56 UTC.

012025-12-22 14:00:00 UTC to 2025-12-22 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 22, 14:002025-12-22 15:00:00 UTC to 2025-12-22 16:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 22, 15:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 22, 14:002025-12-22 14:00:00 UTC2025-12-22 15:00:00 UTC101
Dec 22, 15:002025-12-22 15:00:00 UTC2025-12-22 16:00:00 UTC101

What Hacker News says

2 sources
Yeah, this is where I landed a while ago. What problem am I _really_ trying to solve? For some people it's an ideological one--we don't want AI vacuuming up all of our content. For those, "is this an AI user?" is a useful question to answer. However it's a hard one. For many the problem is simply "there are a class of users that are putting way too much load on the system and it's causing problems". Initially I was playing wack-a-mole with this and dealing with alerts firing on a regular basis because of Meta crawling our site very aggressively, not backing off when errors were returned, etc. I looked at rate limiting but the work involved in distributed rate limiting versus the number of offenders involved made the effort look a little silly, so I moved towards a "nuke it from orbit" strategy: Requests are bucketed by class C subnet (31.
Read the rest
13.80.36 -> 31.13.80.x) and request rate is tracked over 30 minute windows. If the request rate over that window exceeds a very generous threshold I've only seen a few very obvious and poorly behaved crawlers exceed it fires an alert. The alert kicks off a flow where we look up the ASN covering every IP in that range, look up every range associated with those ASNs, and throw an alert in Slack with a big red "Block" button attached. When approved, the entire ASN is blocked at the edge. It's never triggered on anything we weren't willing to block (e.g., a local consumer ISP). We've dropped a handful of foreign providers, some "budget" VPS providers, some more reputable cloud providers, and Facebook. It didn't take long before the alerts stopped--both for high request rates and our application monitoring seeing excessive loads. If anyone's interested in trying to implement something similar, there's a regularly updated database of ASN <-> IP ranges announced here: https://github.com/ipverse/asn-ip
In How I protect my Forgejo instance from AI web crawlers

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.