bgpreport

Network · data from 2026-11-12

AS269308 TELECOM ORBI

Registry name: AS269308 - ORBI SERVICOS E INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269308, 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.
2804:62a0:10::/48 No ROA Nonecovered by 2804:62a0::/36 628 99% 67
45.184.16.0/22 No ROA Other IRR onlyRADB, TC 668 99% 66
45.184.16.0/23 No ROA Other IRR onlyRADB 668 99% 66
45.184.18.0/23 No ROA Other IRR onlyRADB 668 99% 66
45.184.18.0/24 No ROA Other IRR onlyRADB 668 99% 66
2804:62a0::/32 No ROA Other IRR onlyRADB, TC 629 99% 67

AS-SET

AS269308'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 45 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
ROA: none2804:62a0:10::/48No ROA covers it. Add a ROA for AS269308, maxLength 48.628 of 636
Route object: none2804:62a0:10::/48No route object for it. A route object for 2804:62a0::/36 with origin AS269308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269308 in the RIR database for the space.628 of 636
ROA: none45.184.16.0/22No ROA covers it. Add a ROA for AS269308, maxLength 22.668 of 673
Route object: RIR45.184.16.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none45.184.16.0/23No ROA covers it. Add a ROA for AS269308, maxLength 23.668 of 673
Route object: RIR45.184.16.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.184.18.0/23No ROA covers it. Add a ROA for AS269308, maxLength 23.668 of 673
Route object: RIR45.184.18.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.184.18.0/24No ROA covers it. Add a ROA for AS269308, maxLength 24.668 of 673
Route object: RIR45.184.18.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:62a0::/32No ROA covers it. Add a ROA for AS269308, maxLength 32.629 of 636
Route object: RIR2804:62a0::/32Route object only in RADB, TC. Add it in the RIR database for the space.629 of 636

Route objects not announced

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

45.184.16.0/24RADBNo ROA
45.184.17.0/24RADBNo ROA
45.184.19.0/24RADBNo ROA
2804:62a0::/33RADBNo ROA
2804:62a0::/34RADBNo ROA
2804:62a0::/35RADBNo ROA
2804:62a0::/36RADBNo ROA
2804:62a0:1000::/36RADBNo ROA
2804:62a0:2000::/35RADBNo ROA
2804:62a0:2000::/36RADBNo ROA
2804:62a0:3000::/36RADBNo ROA
2804:62a0:4000::/34RADBNo ROA
2804:62a0:4000::/35RADBNo ROA
2804:62a0:4000::/36RADBNo ROA
2804:62a0:5000::/36RADBNo ROA
2804:62a0:6000::/35RADBNo ROA
2804:62a0:6000::/36RADBNo ROA
2804:62a0:7000::/36RADBNo ROA
2804:62a0:8000::/33RADBNo ROA
2804:62a0:8000::/34RADBNo ROA
2804:62a0:8000::/35RADBNo ROA
2804:62a0:8000::/36RADBNo ROA
2804:62a0:9000::/36RADBNo ROA
2804:62a0:a000::/35RADBNo ROA
2804:62a0:a000::/36RADBNo ROA
2804:62a0:b000::/36RADBNo ROA
2804:62a0:c000::/34RADBNo ROA
2804:62a0:c000::/35RADBNo ROA
2804:62a0:c000::/36RADBNo ROA
2804:62a0:d000::/36RADBNo ROA
2804:62a0:e000::/35RADBNo ROA
2804:62a0:e000::/36RADBNo ROA
2804:62a0:f000::/36RADBNo 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.