bgpreport

Network · data from 2026-11-12

AS263289 Palmasnet Informatica

Registry name: AS263289 - Palmasnet Informatica LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263289, 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.

168.196.128.0/22 No ROA Other IRR onlyALTDB, RADB, TC 671 100% 66
168.196.128.0/23 No ROA Other IRR onlyALTDB 671 100% 66
177.190.64.0/23 Valid Nonecovered by 177.190.64.0/22 672 100% 67
177.190.66.0/23 Valid Nonecovered by 177.190.64.0/22 672 100% 67
177.190.65.0/24 Valid Nonecovered by 177.190.64.0/22 671 100% 66
177.190.66.0/24 Valid Nonecovered by 177.190.64.0/22 671 100% 66
177.190.64.0/24 Valid Nonecovered by 177.190.64.0/22 670 100% 66
2804:1680:4000::/34 Valid Nonecovered by 2804:1680::/32 636 100% 67
177.190.64.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 67
177.190.67.0/24 Valid Other IRR onlyRADB 672 100% 67
177.190.68.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 66
177.190.68.0/23 Valid Other IRR onlyALTDB 672 100% 66
168.196.129.0/24 Valid Other IRR onlyALTDB 671 100% 67
168.196.130.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 66
177.190.70.0/23 Valid Other IRR onlyALTDB 671 100% 66
2804:1680::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS263289: AS-263289. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS263289 isn't in the set, or no route object for AS263289 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS263289 in itNot covered
AS-263289 ALTDB 4244 Yes 0

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

  • ROA: none2
  • Route object: none6
  • Route object: RIR10
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none168.196.128.0/22No ROA covers it. Add a ROA for AS263289, maxLength 22.671 of 673
Route object: RIR168.196.128.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none168.196.128.0/23No ROA covers it. Add a ROA for AS263289, maxLength 23.671 of 673
Route object: RIR168.196.128.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: none177.190.64.0/23No route object for it. A route object for 177.190.64.0/22 with origin AS263289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263289 in the RIR database for the space.672 of 673
Route object: none177.190.66.0/23No route object for it. A route object for 177.190.64.0/22 with origin AS263289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263289 in the RIR database for the space.672 of 673
Route object: none177.190.65.0/24No route object for it. A route object for 177.190.64.0/22 with origin AS263289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263289 in the RIR database for the space.671 of 673
Route object: none177.190.66.0/24No route object for it. A route object for 177.190.64.0/22 with origin AS263289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263289 in the RIR database for the space.671 of 673
Route object: none177.190.64.0/24No route object for it. A route object for 177.190.64.0/22 with origin AS263289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263289 in the RIR database for the space.670 of 673
Route object: none2804:1680:4000::/34No route object for it. A route object for 2804:1680::/32 with origin AS263289 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263289 in the RIR database for the space.636 of 636
Route object: RIR177.190.64.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.190.67.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.190.68.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.190.68.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.196.129.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.196.130.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.190.70.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:1680::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

168.196.128.0/24ALTDBValid
168.196.130.0/23ALTDBNo ROA
168.196.131.0/24ALTDBValid
177.190.64.0/21ALTDB, RADB, TCNo ROA
2804:8810::/32ALTDBNo 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.