bgpreport

Network · data from 2026-11-12

AS266602 ODATA

Registry name: AS266602 - ODATA S.A., BR · PeeringDB

7IPv4 routes 85.7% RPKI valid · 42.9% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS266602, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266602, 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.7.232.0/22 No ROA Other IRR onlyRADB 671 100% 67
2804:3e84:a::/48 No ROA Other IRR onlyRADB 636 100% 67
2804:3e84::/32 No ROA Other IRR onlyRADB 635 100% 67
149.78.212.0/23 Valid Nonecovered by 149.78.208.0/20 672 100% 67
149.78.209.0/24 Valid Nonecovered by 149.78.208.0/23 671 100% 67
149.78.214.0/23 Valid Nonecovered by 149.78.208.0/20 671 100% 67
149.78.219.0/24 Valid Nonecovered by 149.78.208.0/20 670 100% 67
149.78.208.0/20 Valid Other IRR onlyRADB 671 100% 67
149.78.208.0/23 Valid Other IRR onlyRADB 671 100% 66

AS-SET

AS266602'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 12 are in fix.csv.

  • ROA: none3
  • Route object: none4
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none45.7.232.0/22No ROA covers it. Add a ROA for AS266602, maxLength 22.671 of 673
Route object: RIR45.7.232.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:3e84:a::/48No ROA covers it. Add a ROA for AS266602, maxLength 48.636 of 636
Route object: RIR2804:3e84:a::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:3e84::/32No ROA covers it. Add a ROA for AS266602, maxLength 32.635 of 636
Route object: RIR2804:3e84::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none149.78.212.0/23No route object for it. A route object for 149.78.208.0/20 with origin AS266602 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266602 in the RIR database for the space.672 of 673
Route object: none149.78.209.0/24No route object for it. A route object for 149.78.208.0/23 with origin AS266602 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266602 in the RIR database for the space.671 of 673
Route object: none149.78.214.0/23No route object for it. A route object for 149.78.208.0/20 with origin AS266602 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266602 in the RIR database for the space.671 of 673
Route object: none149.78.219.0/24No route object for it. A route object for 149.78.208.0/20 with origin AS266602 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266602 in the RIR database for the space.670 of 673
Route object: RIR149.78.208.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR149.78.208.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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