bgpreport

Network · data from 2026-11-12

AS268905 NET COMPARTILHE

Registry name: AS268905 - NET COMPARTILHE, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268905, 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.175.84.0/23 No ROA Other IRR onlyRADB, TC 671 100% 67
45.175.84.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
45.175.85.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
2804:5c60::/32 No ROA Other IRR onlyRADB, TC 635 100% 67
2804:5c60::/34 No ROA Other IRR onlyTC 635 100% 67
2804:5c60:c000::/34 No ROA Other IRR onlyTC 635 100% 67
2804:5c60:8000::/33 No ROA Other IRR onlyRADB, TC 634 100% 67
2804:5c60:8000::/34 No ROA Other IRR onlyTC 634 100% 67

AS-SET

AS268905'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 18 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.175.84.0/23No ROA covers it. Add a ROA for AS268905, maxLength 23.671 of 673
Route object: RIR45.175.84.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none45.175.84.0/24No ROA covers it. Add a ROA for AS268905, maxLength 24.668 of 673
Route object: RIR45.175.84.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none45.175.85.0/24No ROA covers it. Add a ROA for AS268905, maxLength 24.668 of 673
Route object: RIR45.175.85.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:5c60::/32No ROA covers it. Add a ROA for AS268905, maxLength 32.635 of 636
Route object: RIR2804:5c60::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:5c60::/34No ROA covers it. Add a ROA for AS268905, maxLength 34.635 of 636
Route object: RIR2804:5c60::/34Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:5c60:c000::/34No ROA covers it. Add a ROA for AS268905, maxLength 34.635 of 636
Route object: RIR2804:5c60:c000::/34Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:5c60:8000::/33No ROA covers it. Add a ROA for AS268905, maxLength 33.634 of 636
Route object: RIR2804:5c60:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:5c60:8000::/34No ROA covers it. Add a ROA for AS268905, maxLength 34.634 of 636
Route object: RIR2804:5c60:8000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2804:5c60::/33RADB, TCNo ROA
2804:5c60:4000::/34TCNo 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.