bgpreport

Network · data from 2026-11-12

AS262653 PORTALMAIL INFORMATICA LTDA

Registry name: AS262653 - PORTALMAIL INFORMATICA LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262653, 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:784::/34 Invalid: maxLength Nonecovered by 2804:784::/32 35 6%low visibility 23
2804:784:4000::/34 Invalid: maxLength Nonecovered by 2804:784::/32 35 6%low visibility 23
2804:784:c000::/34 Invalid: maxLength Nonecovered by 2804:784::/32 35 6%low visibility 23
177.105.215.0/24 Valid Other IRR onlyRADB 672 100% 67
177.105.216.0/24 Valid Other IRR onlyRADB 672 100% 67
177.105.218.0/24 Valid Other IRR onlyRADB 672 100% 67
177.105.208.0/20 Valid Other IRR onlyRADB, TC 668 99% 66
177.105.208.0/21 Valid Other IRR onlyRADB 668 99% 66
177.105.208.0/22 Valid Other IRR onlyRADB 668 99% 66
177.105.212.0/22 Valid Other IRR onlyRADB 668 99% 66
177.105.216.0/21 Valid Other IRR onlyRADB 668 99% 66
177.105.220.0/22 Valid Other IRR onlyRADB 668 99% 66
2804:784::/32 Valid Other IRR onlyRADB, TC 629 99% 67
177.105.208.0/24 Valid Other IRR onlyRADB 205 30% 54
177.105.209.0/24 Valid Other IRR onlyRADB 205 30% 54
177.105.210.0/24 Valid Other IRR onlyRADB 205 30% 54
177.105.212.0/24 Valid Other IRR onlyRADB 205 30% 54
177.105.213.0/24 Valid Other IRR onlyRADB 205 30% 54
177.105.214.0/24 Valid Other IRR onlyRADB 205 30% 54
177.105.217.0/24 Valid Other IRR onlyRADB 205 30% 54
177.105.219.0/24 Valid Other IRR onlyRADB 205 30% 54
177.105.221.0/24 Valid Other IRR onlyRADB 205 30% 54
177.105.222.0/24 Valid Other IRR onlyRADB 205 30% 54
177.105.223.0/24 Valid Other IRR onlyRADB 205 30% 54

AS-SET

AS262653'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 27 are in fix.csv.

  • ROA: maxLength3
  • Route object: none3
  • Route object: RIR21
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:784::/34ROA 2804:784::/32 AS262653 has maxLength 32; the route is a /34. Raise the maxLength, or add a ROA for 2804:784::/34.35 of 636
Route object: none2804:784::/34No route object for it. A route object for 2804:784::/32 with origin AS262653 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262653 in the RIR database for the space.35 of 636
ROA: maxLength2804:784:4000::/34ROA 2804:784::/32 AS262653 has maxLength 32; the route is a /34. Raise the maxLength, or add a ROA for 2804:784:4000::/34.35 of 636
Route object: none2804:784:4000::/34No route object for it. A route object for 2804:784::/32 with origin AS262653 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262653 in the RIR database for the space.35 of 636
ROA: maxLength2804:784:c000::/34ROA 2804:784::/32 AS262653 has maxLength 32; the route is a /34. Raise the maxLength, or add a ROA for 2804:784:c000::/34.35 of 636
Route object: none2804:784:c000::/34No route object for it. A route object for 2804:784::/32 with origin AS262653 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262653 in the RIR database for the space.35 of 636
Route object: RIR177.105.215.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.216.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.218.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.105.208.0/20Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.105.208.0/21Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.105.208.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.105.212.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.105.216.0/21Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.105.220.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:784::/32Route object only in RADB, TC. Add it in the RIR database for the space.629 of 636
Route object: RIR177.105.208.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.105.209.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.105.210.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.105.212.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.105.213.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.105.214.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.105.217.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.105.219.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.105.221.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.105.222.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.105.223.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673

Route objects not announced

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