bgpreport

Network · data from 2026-11-12

AS267847 COPESNA

Registry name: AS267847 - COPESNA LTDA., AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267847, 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.
186.38.29.0/24 Invalid: origin None 1 0%low visibility 2
45.174.49.0/24 Valid Nonecovered by 45.174.48.0/22 671 100% 66
45.174.50.0/24 Valid Nonecovered by 45.174.48.0/22 671 100% 66
45.174.51.0/24 Valid Nonecovered by 45.174.48.0/22 671 100% 66
45.174.48.0/24 Valid Nonecovered by 45.174.48.0/22 670 100% 67
45.174.48.0/22 Valid RIR databaseLACNIC 672 100% 66
2803:2c60::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

AS267847'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 6 are in fix.csv.

  • ROA: origin1
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: origin186.38.29.0/24ROAs covering it name AS22927, not AS267847. If AS267847 should announce it, add a ROA for AS267847.1 of 673
Route object: none186.38.29.0/24No route object for it. Add a route object with origin AS267847 in the RIR database for the space.1 of 673
Route object: none45.174.49.0/24No route object for it. A route object for 45.174.48.0/22 with origin AS267847 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267847 in the RIR database for the space.671 of 673
Route object: none45.174.50.0/24No route object for it. A route object for 45.174.48.0/22 with origin AS267847 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267847 in the RIR database for the space.671 of 673
Route object: none45.174.51.0/24No route object for it. A route object for 45.174.48.0/22 with origin AS267847 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267847 in the RIR database for the space.671 of 673
Route object: none45.174.48.0/24No route object for it. A route object for 45.174.48.0/22 with origin AS267847 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267847 in the RIR database for the space.670 of 673

Route objects not announced

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