bgpreport

Network · data from 2026-11-12

AS266694 FULL TELECOMUNICACIONES S.A

Registry name: AS266694 - FULL TELECOMUNICACIONES S.A, PY · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266694, 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.
38.98.65.0/24 No ROA Other IRR onlyRADB 670 100% 67
38.57.238.0/23 Valid None 669 99% 67
45.229.168.0/22 Valid RIR databaseLACNIC, RADB 669 99% 67
45.229.168.0/23 Valid RIR databaseLACNIC 668 99% 67
45.229.170.0/23 Valid RIR databaseLACNIC 668 99% 67
2803:7520::/32 Valid RIR databaseLACNIC, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS266694: LACNIC::AS266694:AS-ANNOUNCEMENTS. 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 (AS266694 isn't in the set, or no route object for AS266694 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 objectsAS266694 in itNot covered
LACNIC::AS266694:AS-ANNOUNCEMENTS LACNIC 2311 Yes 1

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none38.98.65.0/24No ROA covers it. Add a ROA for AS266694, maxLength 24.670 of 673
Route object: RIR38.98.65.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none38.57.238.0/23No route object for it. Add a route object with origin AS266694 in the RIR database for the space.669 of 673

Route objects not announced

Route objects with origin AS266694 whose prefix no peer sees AS266694 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.229.168.0/24LACNIC, RADBValid
45.229.169.0/24LACNIC, RADBValid
45.229.170.0/24LACNICValid
45.229.171.0/24LACNICValid

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.