Network · data from 2026-11-12

AS273991 FIBRACOL E.A.S. UNIPERSONAL

Registry name: AS273991 - FIBRACOL E.A.S. UNIPERSONAL, PY · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object

3IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS273991, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273991, 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.79.40.0/24	Valid	Other IRR onlyALTDB	667 99%	67
38.79.41.0/24	Valid	Other IRR onlyALTDB	667 99%	67
38.79.42.0/24	Valid	Other IRR onlyALTDB	667 99%	67
38.79.43.0/24	Valid	Other IRR onlyALTDB	667 99%	67
38.79.40.0/22	Valid	RIR databaseARIN	669 99%	67
2803:98d0::/32	Valid	RIR databaseLACNIC, RADB	631 99%	67
2803:98d0::/33	Valid	RIR databaseLACNIC	631 99%	67
2803:98d0:8000::/33	Valid	RIR databaseLACNIC	631 99%	67

AS-SET

PeeringDB's irr_as_set for AS273991: LACNIC::AS273991. 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 (AS273991 isn't in the set, or no route object for AS273991 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.

Name	Database	ASNs	Sets	Route objects	AS273991 in it	Not covered
LACNIC::AS273991	A single AS number, not a set: AS273991 (this network), 8 route objects.

Name

Database

ASNs

Sets

Route objects

AS273991 in it

Not covered

LACNIC::AS273991

A single AS number, not a set: AS273991 (this network), 8 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.

Route object: RIR4

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	38.79.40.0/24	Route object only in ALTDB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	38.79.41.0/24	Route object only in ALTDB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	38.79.42.0/24	Route object only in ALTDB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	38.79.43.0/24	Route object only in ALTDB. Add it in the RIR database for the space.	667 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

38.79.40.0/24

Route object only in ALTDB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

38.79.41.0/24

Route object only in ALTDB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

38.79.42.0/24

Route object only in ALTDB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

38.79.43.0/24

Route object only in ALTDB. Add it in the RIR database for the space.

667 of 673

Route objects not announced

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