bgpreport

Network · data from 2026-11-12

AS273570 AS273570 - IMPACTO SOLUCOES EM INTERNET LTDA

Registry name: AS273570 - IMPACTO SOLUCOES EM INTERNET LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273570, 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:88f0::/34 No ROA Nonecovered by 2804:88f0::/32 634 100% 67
2804:88f0:4000::/34 No ROA Nonecovered by 2804:88f0::/32 634 100% 67
2804:88f0:8000::/34 No ROA Nonecovered by 2804:88f0::/32 634 100% 67
2804:88f0:c000::/34 No ROA Nonecovered by 2804:88f0::/32 634 100% 67
2804:88f0::/32 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

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

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2804:88f0::/34No ROA covers it. Add a ROA for AS273570, maxLength 34.634 of 636
Route object: none2804:88f0::/34No route object for it. A route object for 2804:88f0::/32 with origin AS273570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273570 in the RIR database for the space.634 of 636
ROA: none2804:88f0:4000::/34No ROA covers it. Add a ROA for AS273570, maxLength 34.634 of 636
Route object: none2804:88f0:4000::/34No route object for it. A route object for 2804:88f0::/32 with origin AS273570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273570 in the RIR database for the space.634 of 636
ROA: none2804:88f0:8000::/34No ROA covers it. Add a ROA for AS273570, maxLength 34.634 of 636
Route object: none2804:88f0:8000::/34No route object for it. A route object for 2804:88f0::/32 with origin AS273570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273570 in the RIR database for the space.634 of 636
ROA: none2804:88f0:c000::/34No ROA covers it. Add a ROA for AS273570, maxLength 34.634 of 636
Route object: none2804:88f0:c000::/34No route object for it. A route object for 2804:88f0::/32 with origin AS273570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273570 in the RIR database for the space.634 of 636
ROA: none2804:88f0::/32No ROA covers it. Add a ROA for AS273570, maxLength 32.634 of 636
Route object: RIR2804:88f0::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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