bgpreport

Network · data from 2026-11-12

AS275072 Conectate Comunicaciones del Pacifico

Registry name: AS275072 - GAA73, CO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS275072, 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.
169.40.68.0/24 Invalid: maxLength Nonecovered by 169.40.68.0/22 10 1%low visibility 7
38.191.219.0/24 No ROA Other origin only 669 99% 67
169.40.68.0/22 Valid RIR databaseRADB, RIPE 671 100% 67
2803:a0b0::/32 Valid RIR databaseLACNIC 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS275072: LACNIC::AS275072. 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 (AS275072 isn't in the set, or no route object for AS275072 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 objectsAS275072 in itNot covered
LACNIC::AS275072 A single AS number, not a set: AS275072 (this network), 2 route objects.

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

  • ROA: maxLength1
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: maxLength169.40.68.0/24ROA 169.40.68.0/22 AS275072 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 169.40.68.0/24.10 of 673
Route object: none169.40.68.0/24No route object for it. A route object for 169.40.68.0/22 with origin AS275072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275072 in the RIR database for the space.10 of 673
ROA: none38.191.219.0/24No ROA covers it. Add a ROA for AS275072, maxLength 24.669 of 673
Route object: none38.191.219.0/24Route objects for it name AS273103. Add a route object with origin AS275072 in the RIR database for the space.669 of 673

Route objects not announced

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