bgpreport

Network · data from 2026-11-12

AS43366 OSSO

Registry name: OSSO OSSO B.V., NL · PeeringDB

9IPv4 routes 88.9% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS43366, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS43366, 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.
195.88.160.0/23 No ROA RIR databaseRIPE 673 100% 67
91.194.224.0/23 Valid RIR databaseRIPE 673 100% 67
185.12.144.0/22 Valid RIR databaseRIPE 673 100% 67
185.37.124.0/22 Valid RIR databaseRIPE 673 100% 67
185.79.8.0/22 Valid RIR databaseRIPE 673 100% 67
185.159.136.0/22 Valid RIR databaseRIPE 673 100% 67
195.28.22.0/23 Valid RIR databaseRIPE 673 100% 67
217.21.192.0/20 Valid RIR databaseRIPE 673 100% 67
217.21.206.0/24 Valid RIR databaseRIPE 673 100% 67
2a00:8080::/32 Valid RIR databaseRIPE 635 100% 67
2a05:6c80::/29 Valid RIR databaseRIPE 634 100% 67
2a07:b440::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS43366: RIPE::AS-OSSO. 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 (AS43366 isn't in the set, or no route object for AS43366 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 objectsAS43366 in itNot covered
RIPE::AS-OSSO RIPE 161165 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 1 are in fix.csv.

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none195.88.160.0/23No ROA covers it. Add a ROA for AS43366, maxLength 23.673 of 673

Route objects not announced

Every route object with origin AS43366 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.