bgpreport

Network · data from 2026-11-12

AS13127 Odido AS13127

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

26IPv4 routes 96.2% RPKI valid · 88.5% with a route object
11IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 3 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
35Route objects not announced registered with origin AS13127, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13127, 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.

91.234.50.0/24 No ROA RIR databaseRIPE 673 100% 67
82.173.0.0/17 Valid Nonecovered by 82.173.0.0/16 673 100% 67
82.173.224.0/19 Valid Nonecovered by 82.173.0.0/16 673 100% 67
87.213.94.0/24 Valid Nonecovered by 87.213.0.0/16 3 0%low visibility 2
62.58.0.0/15 Valid RIR databaseRIPE 673 100% 67
62.58.93.0/24 Valid RIR databaseRIPE 673 100% 67
62.166.0.0/17 Valid RIR databaseRIPE 673 100% 67
81.58.0.0/16 Valid RIR databaseRIPE 673 100% 67
81.59.128.0/17 Valid RIR databaseRIPE 673 100% 67
82.172.128.0/17 Valid RIR databaseRIPE 673 100% 67
82.175.0.0/16 Valid RIR databaseRIPE 673 100% 67
87.213.0.0/16 Valid RIR databaseRIPE 673 100% 67
87.215.0.0/16 Valid RIR databaseRIPE 673 100% 67
145.83.1.0/24 Valid RIR databaseRIPE 673 100% 67
145.83.2.0/24 Valid RIR databaseRIPE 673 100% 67
176.117.57.0/24 Valid RIR databaseRIPE 673 100% 67
185.222.232.0/24 Valid RIR databaseRIPE 673 100% 67
193.176.208.0/24 Valid RIR databaseRIPE 673 100% 67
194.53.33.0/24 Valid RIR databaseRIPE 673 100% 67
194.53.36.0/24 Valid RIR databaseRIPE 673 100% 67
37.220.148.0/24 Valid RIR databaseRIPE 672 100% 67
37.220.150.0/24 Valid RIR databaseRIPE 672 100% 67
2001:67c:17ec::/48 Valid RIR databaseRIPE 636 100% 69
2a01:380::/32 Valid RIR databaseRIPE 636 100% 70
2001:67c:14b0::/48 Valid RIR databaseRIPE 634 100% 68
2a04:9a00:1118::/48 Valid RIR databaseRIPE 634 100% 68
2a07:3501:1080::/48 Valid RIR databaseRIPE 634 100% 68
2a07:3501:1081::/48 Valid RIR databaseRIPE 634 100% 68
2a07:3502:1190::/48 Valid RIR databaseRIPE 634 100% 68
2a07:3502:1192::/48 Valid RIR databaseRIPE 634 100% 68
2a07:3502:1193::/48 Valid RIR databaseRIPE 634 100% 68
2a0c:9180::/48 Valid RIR databaseRIPE 634 100% 68
2a0c:9180:1::/48 Valid RIR databaseRIPE 634 100% 68
91.209.137.0/24 Valid RIR databaseRIPE 377 56% 62
82.173.128.0/18 Valid RIR databaseRIPE 2 0%low visibility 2
82.173.192.0/19 Valid RIR databaseRIPE 2 0%low visibility 2
143.176.0.0/16 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS13127'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 39 are in fix.csv.

  • ROA: none1
  • Route object: none3
  • Route object: not announced35
ChangePrefix or setDetailFull-table peers
ROA: none91.234.50.0/24No ROA covers it. Add a ROA for AS13127, maxLength 24.673 of 673
Route object: none82.173.0.0/17No route object for it. A route object for 82.173.0.0/16 with origin AS13127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13127 in the RIR database for the space.673 of 673
Route object: none82.173.224.0/19No route object for it. A route object for 82.173.0.0/16 with origin AS13127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13127 in the RIR database for the space.673 of 673
Route object: none87.213.94.0/24No route object for it. A route object for 87.213.0.0/16 with origin AS13127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13127 in the RIR database for the space.3 of 673

Route objects not announced

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

37.220.147.0/24RIPEValid
37.220.149.0/24RIPEValid
62.58.82.0/24RIPEValid
81.58.0.0/15RIPEValid
82.173.0.0/16RIPEValid
82.173.81.0/24RIPEValid
87.211.0.0/16RIPEValid
87.213.43.0/24RIPEValid
87.213.81.0/24RIPEValid
87.213.100.0/24RIPEValid
87.213.101.0/24RIPEValid
87.213.114.0/24RIPEValid
87.213.115.0/24RIPEValid
87.213.239.0/24RIPEValid
87.213.242.0/24RIPEValid
87.214.0.0/15RIPEValid
87.214.0.0/16RIPEValid
87.215.4.0/24RIPEValid
87.215.7.0/24RIPEValid
87.215.38.0/24RIPEValid
87.215.40.0/24RIPEValid
87.215.45.0/24RIPEValid
87.215.64.0/24RIPEValid
87.215.98.0/24RIPEValid
91.234.50.0/23RIPENo ROA
141.197.32.0/20RIPE-NONAUTHNo ROA
159.46.0.0/16RIPENo ROA
159.46.0.0/17RIPENo ROA
185.166.48.0/22RIPEInvalid: origin
193.177.186.0/23RIPENo ROA
194.13.191.0/24RIPENo ROA
194.53.35.0/24RIPEValid
194.53.47.0/24RIPENo ROA
195.42.134.0/23RIPENo ROA
217.16.32.0/20RIPENo 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.