bgpreport

Network · data from 2026-11-12

AS269938 ADN TELECOM

Registry name: AS269938 - ADN TELECOM S.A.C., PE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269938, 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.

2803:6ae0::/32 No ROA None 636 100% 67
209.45.18.0/24 No ROA Other IRR onlyRADB 673 100% 67
190.83.60.0/23 Valid RIR databaseLACNIC, RADB 671 100% 67
190.83.60.0/24 Valid RIR databaseLACNIC 6 1%low visibility 4
190.83.61.0/24 Valid RIR databaseLACNIC 6 1%low visibility 4

AS-SET

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2803:6ae0::/32No ROA covers it. Add a ROA for AS269938, maxLength 32.636 of 636
Route object: none2803:6ae0::/32No route object for it. Add a route object with origin AS269938 in the RIR database for the space.636 of 636
ROA: none209.45.18.0/24No ROA covers it. Add a ROA for AS269938, maxLength 24.673 of 673
Route object: RIR209.45.18.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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