All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
PEER.AS: A modern and beautiful BGP/AS/Network Probing toolkit
I'd like to share this brand new BGP/ASN/network insight tool with everyone. It's a completely open-source, (mostly) static, and reproducible project. It's currently available on PEER.AS.
The data on the website comes from publicly available RIPE rrc01/06 MRT Dumps (more collection points planned!) and is provided after processing and weight reduction. Unlike bgp.he.net and bgp.tools, this website has no rate limit because, simply put, it's a full BGP table living in your browser. It uses duckdb+parquet sharding and is served by Cloudflare Pages.
In addition to the core AS/Prefix data, two other well-crafted tools are currently available: IP Probe which probes all your outgoing IPs (similar to browserleaks), and Global Test which provides 2D/3D visualized route tracing via globalping.io global probe points + nexttrace IP data.
Go try it out today and any feedback would be helpful!
Homepage: https://peer.as/
Repo Link: https://github.com/Archeb/peer.as
Comments
First
cool stuff
I know it use AI, but any reason to use parquet and duckdb, who make the decision?
It's beautiful.
I was thinking about using JSONL and custom indexing schema at first, then I asked Claude and it recommended duckdb+parquet, so after some investigation I found this reasonable and went with it.
Looks like it completely ignores prepends. Collection points are definitely too few, no visibility into IXP RS and some transits are not seen.
Scary to go beyond the home page
Damn, okx, coinbase, openai, perplexity...why do you even need it on such a website?
These requests are for IP probing; the vast majority target Cloudflare's diagnostic endpoint (
/cdn-cgi/trace) and do not carry any valid credentials.The relevant code initiating these requests can be found at: https://github.com/Archeb/peer.as/blob/main/ipcollect/web/src/lib/geo.js#L115
I fully understand this concern and will, as soon as possible, restrict this functionality to same-origin requests—limiting them to the domain where the service is deployed—unless the user specifically visits the IP Probe page.
Requests on the home page have been restricted to *.peer.as and necessary RIR RDAP requests.
We have added RIPE RIS rrc03 and RouteViews route-views2 as data sources. AS-path prepending is also displayed correctly now.