Network · data from 2026-11-12

AS265680 HNTELCO

Registry name: AS265680 - HNTELCO S.A, HN · PeeringDB

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

1IPv6 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

1Route objects not announced registered with origin AS265680, seen from no peer

Announced routes

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


45.5.76.0/24	Valid	RIR databaseALTDB, LACNIC	672 100%	67
45.5.77.0/24	Valid	RIR databaseALTDB, LACNIC	672 100%	67
45.5.78.0/24	Valid	RIR databaseALTDB, LACNIC	672 100%	67
45.5.79.0/24	Valid	RIR databaseALTDB, LACNIC	671 100%	67
2803:21c0::/32	Valid	RIR databaseALTDB, LACNIC, RIPE-NONAUTH	635 100%	68

AS-SET

PeeringDB's irr_as_set for AS265680: AS-HNTELCO. 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 (AS265680 isn't in the set, or no route object for AS265680 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	AS265680 in it	Not covered
AS-HNTELCO	RIPElists itself further down3 member sets in no database: AS-GUP42, AS-GUT15, AS-TES37	24	11	113	Yes	0

Name

Database

ASNs

Sets

Route objects

AS265680 in it

Not covered

AS-HNTELCO

RIPElists itself further down3 member sets in no database: AS-GUP42, AS-GUT15, AS-TES37

113

Yes

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.

AS-SET: missing member3
Route object: not announced1

Change	Prefix or set	Detail
AS-SET: missing member	AS-HNTELCO	AS-HNTELCO (RIPE) lists AS-GUP42; no IRR database read has it.
AS-SET: missing member	AS-HNTELCO	AS-HNTELCO (RIPE) lists AS-GUT15; no IRR database read has it.
AS-SET: missing member	AS-HNTELCO	AS-HNTELCO (RIPE) lists AS-TES37; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

AS-SET: missing member

AS-HNTELCO

AS-HNTELCO (RIPE) lists AS-GUP42; no IRR database read has it.

AS-SET: missing member

AS-HNTELCO

AS-HNTELCO (RIPE) lists AS-GUT15; no IRR database read has it.

AS-SET: missing member

AS-HNTELCO

AS-HNTELCO (RIPE) lists AS-TES37; no IRR database read has it.

Route objects not announced

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


45.5.76.0/22	ALTDB, RIPE-NONAUTH	No ROA

45.5.76.0/22

ALTDB, RIPE-NONAUTH

No ROA

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.