bgpreport

Network · data from 2026-11-12

AS31615 Odido AS31615

Registry name: Odido Odido Netherlands B.V., NL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS31615, 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.
84.241.248.0/24 Valid Nonecovered by 84.241.224.0/19 5 1%low visibility 4
178.227.7.0/24 Valid Nonecovered by 178.227.0.0/16 5 1%low visibility 3
178.225.246.0/24 Valid Nonecovered by 178.225.0.0/16 1 0%low visibility 1
178.227.126.0/24 Valid Nonecovered by 178.227.0.0/16 1 0%low visibility 1
178.230.38.0/24 Valid Nonecovered by 178.230.0.0/16 1 0%low visibility 1
84.241.192.0/18 Valid RIR databaseRIPE 673 100% 67
89.205.128.0/17 Valid RIR databaseRIPE 673 100% 67
91.141.128.0/17 Valid RIR databaseRIPE 673 100% 67
178.225.0.0/16 Valid RIR databaseRIPE 673 100% 67
178.227.0.0/16 Valid RIR databaseRIPE 673 100% 67
178.228.0.0/16 Valid RIR databaseRIPE 673 100% 67
178.229.0.0/16 Valid RIR databaseRIPE 673 100% 67
178.230.0.0/16 Valid RIR databaseRIPE 673 100% 67
178.231.0.0/16 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS31615's PeeringDB record names no AS-SET.

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 27 are in fix.csv.

  • Route object: none5
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
Route object: none84.241.248.0/24No route object for it. A route object for 84.241.224.0/19 with origin AS31615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31615 in the RIR database for the space.5 of 673
Route object: none178.227.7.0/24No route object for it. A route object for 178.227.0.0/16 with origin AS31615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31615 in the RIR database for the space.5 of 673
Route object: none178.225.246.0/24No route object for it. A route object for 178.225.0.0/16 with origin AS31615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31615 in the RIR database for the space.1 of 673
Route object: none178.227.126.0/24No route object for it. A route object for 178.227.0.0/16 with origin AS31615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31615 in the RIR database for the space.1 of 673
Route object: none178.230.38.0/24No route object for it. A route object for 178.230.0.0/16 with origin AS31615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31615 in the RIR database for the space.1 of 673

Route objects not announced

Route objects with origin AS31615 whose prefix no peer sees AS31615 announce. Many are kept on purpose (backup routes, space announced only in some places).

84.241.192.0/19RIPEValid
84.241.224.0/19RIPEValid
89.205.128.0/18RIPEValid
89.205.192.0/18RIPEValid
91.141.128.0/18RIPEValid
91.141.192.0/18RIPEValid
95.98.0.0/15RIPEValid
95.98.0.0/16RIPEValid
95.99.0.0/16RIPEValid
109.232.164.0/24RIPENo ROA
109.232.165.0/24RIPENo ROA
109.232.166.0/23RIPENo ROA
178.224.0.0/13RIPEValid
178.224.0.0/14RIPEValid
178.228.0.0/14RIPEValid
188.88.0.0/14RIPEValid
188.88.0.0/15RIPEValid
188.90.0.0/15RIPEValid
2a02:498::/29RIPENo ROA
2a02:498::/32RIPENo ROA
2a02:499::/32RIPENo ROA
2a02:49a::/32RIPENo ROA

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.