bgpreport

Network · data from 2026-11-12

AS271394 AS271394 - Pedro Ernani Goncalves Mansinho

Registry name: AS271394 - Pedro Ernani Goncalves Mansinho, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271394, 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:7ad4::/40 Invalid: maxLength Nonecovered by 2804:7ad4::/32 40 6%low visibility 24
179.49.80.0/23 Valid Nonecovered by 179.49.80.0/22 671 100% 67
179.49.83.0/24 Valid Nonecovered by 179.49.80.0/22 663 99% 67
179.49.80.0/24 Valid Nonecovered by 179.49.80.0/22 205 30% 56
179.49.81.0/24 Valid Nonecovered by 179.49.80.0/22 205 30% 56
179.49.82.0/24 Valid Other IRR onlyRADB 670 100% 67
2804:7ad4::/32 Valid Other IRR onlyALTDB, RADB, TC 636 100% 70

AS-SET

AS271394 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 9 are in fix.csv.

  • ROA: maxLength1
  • Route object: none5
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:7ad4::/40ROA 2804:7ad4::/32 AS271394 has maxLength 32; the route is a /40. Raise the maxLength, or add a ROA for 2804:7ad4::/40.40 of 636
Route object: none2804:7ad4::/40No route object for it. A route object for 2804:7ad4::/32 with origin AS271394 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271394 in the RIR database for the space.40 of 636
Route object: none179.49.80.0/23No route object for it. A route object for 179.49.80.0/22 with origin AS271394 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271394 in the RIR database for the space.671 of 673
Route object: none179.49.83.0/24No route object for it. A route object for 179.49.80.0/22 with origin AS271394 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271394 in the RIR database for the space.663 of 673
Route object: none179.49.80.0/24No route object for it. A route object for 179.49.80.0/22 with origin AS271394 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271394 in the RIR database for the space.205 of 673
Route object: none179.49.81.0/24No route object for it. A route object for 179.49.80.0/22 with origin AS271394 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271394 in the RIR database for the space.205 of 673
Route object: RIR179.49.82.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:7ad4::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

179.49.80.0/22ALTDB, RADB, TCNo 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.