bgpreport

Network · data from 2026-11-12

AS273112 ARAPA TELECOMUNICACIONES E.I.R.L.

Registry name: AS273112 - ARAPA TELECOMUNICACIONES E.I.R.L., PE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273112, 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.
201.234.117.0/25 Invalid: maxLength Nonecovered by 201.234.117.0/24 2 0%low visibility 2
201.234.117.128/25 Invalid: maxLength Nonecovered by 201.234.117.0/24 2 0%low visibility 2
2803:b0e0:7009::/48 Valid None 635 100% 67
201.234.117.0/24 Valid RIR databaseLACNIC 672 100% 66
38.137.205.0/24 Valid RIR databaseARIN, RADB 671 100% 67
2803:a850::/32 Valid RIR databaseLACNIC 636 100% 67
209.45.20.0/24 Valid RIR databaseLACNIC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS273112: AS273112. 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 (AS273112 isn't in the set, or no route object for AS273112 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 objectsAS273112 in itNot covered
AS273112 A single AS number, not a set: AS273112 (this network), 4 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 5 are in fix.csv.

  • ROA: maxLength2
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: maxLength201.234.117.0/25ROA 201.234.117.0/24 AS273112 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 201.234.117.0/25.2 of 673
Route object: none201.234.117.0/25No route object for it. A route object for 201.234.117.0/24 with origin AS273112 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS273112 in the RIR database for the space.2 of 673
ROA: maxLength201.234.117.128/25ROA 201.234.117.0/24 AS273112 has maxLength 24; the route is a /25. Raise the maxLength, or add a ROA for 201.234.117.128/25.2 of 673
Route object: none201.234.117.128/25No route object for it. A route object for 201.234.117.0/24 with origin AS273112 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS273112 in the RIR database for the space.2 of 673
Route object: none2803:b0e0:7009::/48No route object for it. Add a route object with origin AS273112 in the RIR database for the space.635 of 636

Route objects not announced

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