bgpreport

Network · data from 2026-11-12

AS52950 AS52950 - Fund. de Apoio a Pesq. C&T do Est. de SC - FAPESC

Registry name: AS52950 - Fund. de Apoio a Pesq. C&T do Est. de SC - FAPESC, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52950, 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.
189.8.128.0/18 No ROA Nonecovered by 189.8.128.0/17 672 100% 67
189.8.192.0/18 No ROA Nonecovered by 189.8.128.0/17 672 100% 67
189.8.255.0/24 No ROA Nonecovered by 189.8.128.0/17 672 100% 67
2804:1f12::/33 No ROA Nonecovered by 2804:1f12::/32 636 100% 67
2804:1f12:8000::/33 No ROA Nonecovered by 2804:1f12::/32 636 100% 67
189.8.128.0/17 No ROA Other IRR onlyRADB 672 100% 68
2804:1f12::/32 No ROA Other IRR onlyRADB 636 100% 70

AS-SET

AS52950 isn't in PeeringDB, where networks name their 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none5
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none189.8.128.0/18No ROA covers it. Add a ROA for AS52950, maxLength 18.672 of 673
Route object: none189.8.128.0/18No route object for it. A route object for 189.8.128.0/17 with origin AS52950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52950 in the RIR database for the space.672 of 673
ROA: none189.8.192.0/18No ROA covers it. Add a ROA for AS52950, maxLength 18.672 of 673
Route object: none189.8.192.0/18No route object for it. A route object for 189.8.128.0/17 with origin AS52950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52950 in the RIR database for the space.672 of 673
ROA: none189.8.255.0/24No ROA covers it. Add a ROA for AS52950, maxLength 24.672 of 673
Route object: none189.8.255.0/24No route object for it. A route object for 189.8.128.0/17 with origin AS52950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52950 in the RIR database for the space.672 of 673
ROA: none2804:1f12::/33No ROA covers it. Add a ROA for AS52950, maxLength 33.636 of 636
Route object: none2804:1f12::/33No route object for it. A route object for 2804:1f12::/32 with origin AS52950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52950 in the RIR database for the space.636 of 636
ROA: none2804:1f12:8000::/33No ROA covers it. Add a ROA for AS52950, maxLength 33.636 of 636
Route object: none2804:1f12:8000::/33No route object for it. A route object for 2804:1f12::/32 with origin AS52950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52950 in the RIR database for the space.636 of 636
ROA: none189.8.128.0/17No ROA covers it. Add a ROA for AS52950, maxLength 17.672 of 673
Route object: RIR189.8.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:1f12::/32No ROA covers it. Add a ROA for AS52950, maxLength 32.636 of 636
Route object: RIR2804:1f12::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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