bgpreport

Network · data from 2026-11-12

AS31736 senseLAN

Registry name: SENSELAN-AS senseLAN GmbH, CH · PeeringDB

19IPv4 routes 100.0% RPKI valid · 100.0% with a route object
9IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS31736, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS31736, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
45.8.240.0/22 Valid RIR databaseRIPE 673 100% 67
83.222.128.0/19 Valid RIR databaseRIPE 673 100% 67
171.33.243.0/24 Valid RIR databaseRIPE 673 100% 67
185.5.32.0/22 Valid RIR databaseRIPE 673 100% 67
185.20.144.0/22 Valid RIR databaseRIPE 673 100% 67
185.64.116.0/22 Valid RIR databaseRIPE 673 100% 67
185.77.92.0/23 Valid RIR databaseRIPE 673 100% 67
185.77.94.0/24 Valid RIR databaseRIPE 673 100% 67
185.77.95.0/24 Valid RIR databaseRIPE 673 100% 67
185.78.188.0/22 Valid RIR databaseRIPE 673 100% 67
185.82.60.0/22 Valid RIR databaseRIPE 673 100% 67
185.86.28.0/22 Valid RIR databaseRIPE 673 100% 67
185.230.116.0/22 Valid RIR databaseRIPE 673 100% 67
193.135.30.0/24 Valid RIR databaseRIPE 673 100% 67
194.153.188.0/23 Valid RIR databaseRIPE 673 100% 67
195.144.30.0/24 Valid RIR databaseRIPE 673 100% 67
203.16.207.0/24 Valid RIR databaseRIPE 673 100% 67
212.108.104.0/24 Valid RIR databaseRIPE 673 100% 67
77.37.8.0/24 Valid RIR databaseRIPE 672 100% 67
2001:67c:7d4::/48 Valid RIR databaseRIPE 636 100% 67
2a02:3b0::/32 Valid RIR databaseRIPE 636 100% 67
2a03:1360::/32 Valid RIR databaseRIPE 636 100% 67
2a03:53a0::/32 Valid RIR databaseRIPE 636 100% 67
2a03:59e0::/32 Valid RIR databaseRIPE 636 100% 67
2a03:75a0::/32 Valid RIR databaseRIPE 636 100% 67
2a09:c2c0::/29 Valid RIR databaseRIPE 635 100% 67
2a0e:9e00::/29 Valid RIR databaseRIPE 635 100% 67
2a12:44c0::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS31736: AS31736:AS-SENSELAN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS31736 isn't in the set, or no route object for AS31736 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS31736 in itNot covered
AS31736:AS-SENSELAN RIPE 4147 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS31736 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.