bgpreport

Network · data from 2026-11-12

AS267434 AS267434 - Xingu Assessoria em Redes Ltda ME

Registry name: AS267434 - Xingu Assessoria em Redes Ltda ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267434, 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.
181.191.180.0/22 No ROA Other IRR onlyALTDB, RADB 672 100% 67
181.191.180.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
181.191.181.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
181.191.183.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
181.191.182.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
2804:4174::/32 No ROA Other IRR onlyALTDB, RADB 634 100% 67

AS-SET

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

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none181.191.180.0/22No ROA covers it. Add a ROA for AS267434, maxLength 22.672 of 673
Route object: RIR181.191.180.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none181.191.180.0/24No ROA covers it. Add a ROA for AS267434, maxLength 24.672 of 673
Route object: RIR181.191.180.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none181.191.181.0/24No ROA covers it. Add a ROA for AS267434, maxLength 24.672 of 673
Route object: RIR181.191.181.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none181.191.183.0/24No ROA covers it. Add a ROA for AS267434, maxLength 24.672 of 673
Route object: RIR181.191.183.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none181.191.182.0/24No ROA covers it. Add a ROA for AS267434, maxLength 24.670 of 673
Route object: RIR181.191.182.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:4174::/32No ROA covers it. Add a ROA for AS267434, maxLength 32.634 of 636
Route object: RIR2804:4174::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

181.191.180.0/23RADBNo ROA
181.191.182.0/23RADBNo ROA
2804:7e8c::/32RADBNo 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.