bgpreport

Network · data from 2026-11-12

AS28172 PROJESOM INTERNET LTDA

Registry name: AS28172 - PROJESOM INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28172, 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:20c::/34 Valid Nonecovered by 2804:20c::/32 632 99% 67
2804:20c:4000::/34 Valid Nonecovered by 2804:20c::/32 632 99% 67
2804:20c:8000::/34 Valid Nonecovered by 2804:20c::/32 632 99% 67
2804:20c:c000::/34 Valid Nonecovered by 2804:20c::/32 632 99% 67
189.84.192.0/20 Valid Other IRR onlyRADB, TC 668 99% 67
189.84.196.0/22 Valid Other IRR onlyRADB 668 99% 67
189.84.204.0/22 Valid Other IRR onlyRADB 668 99% 67
189.84.192.0/22 Valid Other IRR onlyRADB 667 99% 67
2804:20c::/32 Valid Other IRR onlyNTTCOM, RADB, TC 632 99% 67
189.84.200.0/22 Valid Other IRR onlyRADB 3 0%low visibility 3

AS-SET

AS28172'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 10 are in fix.csv.

  • Route object: none4
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none2804:20c::/34No route object for it. A route object for 2804:20c::/32 with origin AS28172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28172 in the RIR database for the space.632 of 636
Route object: none2804:20c:4000::/34No route object for it. A route object for 2804:20c::/32 with origin AS28172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28172 in the RIR database for the space.632 of 636
Route object: none2804:20c:8000::/34No route object for it. A route object for 2804:20c::/32 with origin AS28172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28172 in the RIR database for the space.632 of 636
Route object: none2804:20c:c000::/34No route object for it. A route object for 2804:20c::/32 with origin AS28172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28172 in the RIR database for the space.632 of 636
Route object: RIR189.84.192.0/20Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR189.84.196.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR189.84.204.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR189.84.192.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:20c::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR189.84.200.0/22Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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