On 17/09/2026 21:03, Matin Baloochestani via NANOG wrote: Nice tool and well thought out. The red link is described as "Most Observed AS-PATH" yet I have a /24 that has only 11 peer count (with all other paths having larger peer counts) yet is marked as red: https://bgpmap.net/s/vpjmtb8tig Or am I missing something? Thanks, Hank

Hi all,

Wanted to share a small side project: bgpmap.net, a free BGP looking glass with a visual AS-path map. Data comes from RIPE RIS via RIPEstat, shown from multiple vantage points in one view. No signup, free to use.

Honest disclaimer: this is my first website and a learning project, so keep expectations modest. Not trying to replace bgp.tools or anything close to it. I built it because I wanted a cleaner way to compare AS paths across vantage points.

If anyone has a minute to try it, I'd appreciate feedback on anything that looks wrong in the data, features you'd actually use, or rough edges in the UI.

Thanks, Matin https://bgpmap.net _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/3IBZTYUU...

Hi Hank, Thanks, and fair question. Those two numbers measure different things. "Most Observed AS-PATH" counts exact full paths -- here "24482 35280 378", seen by 11 peers. The edge labels count how many peers cross that edge. The 25 peers on AS1299 -> AS35280 are split across several different full paths ("6830 1299 35280 378", "3491 1299 35280 378", ...), which is why that 25 never turns into a single winning path. Each peer reports the path as it saw it, so the leftmost ASN varies from peer to peer -- 259 unique paths from 349 peers in this snapshot. But you're right that the red highlight oversells it. Painting a 3% path red next to edges showing 25/18/15 makes it look like the "main" path, which it isn't. That's a display problem on my side. The computation stays as-is; I'll rework the presentation early next week -- most likely only highlighting when the top path actually has a meaningful share, and labeling the rest more honestly. I'll share what I come up with here. If you have a preference for how it should read when the winner's share is this small, I'd appreciate your take. Thanks again, Matin

Not to discourage you, but this largely duplicates HE's AS route propagation graph. On Thu, Sep 17, 2026 at 2:26 PM Matin Baloochestani via NANOG < nanog@lists.nanog.org> wrote:

Hi all,

Wanted to share a small side project: bgpmap.net, a free BGP looking glass with a visual AS-path map. Data comes from RIPE RIS via RIPEstat, shown from multiple vantage points in one view. No signup, free to use.

Honest disclaimer: this is my first website and a learning project, so keep expectations modest. Not trying to replace bgp.tools or anything close to it. I built it because I wanted a cleaner way to compare AS paths across vantage points.

If anyone has a minute to try it, I'd appreciate feedback on anything that looks wrong in the data, features you'd actually use, or rough edges in the UI.

Thanks, Matin https://bgpmap.net _______________________________________________ NANOG mailing list

https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/3IBZTYUU...

Yes it does. Personally, I don't find a single prefix visualization helpful, as it will mostly duplicate the general AS propagation graph. It might be interesting if it could do "compare AS graphs for prefix FOO and BAR" or something like that, but generally you are going to do that muh quicker on a CLI or with grep/awk fu. On Fri, Sep 18, 2026 at 11:12 AM Jon Lewis via NANOG <nanog@lists.nanog.org> wrote:

On Fri, 18 Sep 2026, Tom Beecher via NANOG wrote:

...

Not to discourage you, but this largely duplicates HE's AS route propagation graph.

On Thu, Sep 17, 2026 at 2:26 PM Matin Baloochestani via NANOG < nanog@lists.nanog.org> wrote:

...

Thanks, Matin https://bgpmap.net

One difference though is, bgp.he.net has the "Graph v4" and "Graph v6" tabs, but does this by ASN. Matin's tool does the graphing by prefix. It might be nice to include in the output, when the lookup was done using an IP with no mask, the prefix that was found that matched the supplied IP.

---------------------------------------------------------------------- Jon Lewis, MCP :) | I route Blue Stream Fiber, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ _______________________________________________ NANOG mailing list

https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/R7LQ3XIU...

Hi Jon, You're completely right, and that's very good feedback. I'll add the matched prefix to the output in the next update. Matin

On 20 September 2026 09:18:15 CEST, Matin via NANOG <nanog@lists.nanog.org> wrote:

Hi Jon,

You're completely right, and that's very good feedback. I'll add the matched prefix to the output in the next update.

Matin _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/GDSG527Z...

Please don't connect Claude directly to the NANOG meeting list.

On Fri, Sep 18, 2026 at 11:11:16AM -0000, Matin via NANOG <nanog@lists.nanog.org> wrote a message of 28 lines which said:

"Most Observed AS-PATH" counts exact full paths -- here "24482 35280 378", seen by 11 peers. The edge labels count how many peers cross that edge. The 25 peers on AS1299 -> AS35280 are split across several different full paths ("6830 1299 35280 378", "3491 1299 35280 378", ...), which is why that 25 never turns into a single winning path.

Then <https://bgpmap.net/s/5j6fybd3dg> is not clear. "24482 12322" has 11 RIS peers, but "6939 3356 12322" has 33. Why isn't it in red?