Network · data from 2026-11-12

AS269747 IPCOMS NETWORKS

Registry name: AS269747 - BENTO IVAN GABRIEL(IPCOMS NETWORKS), AR · PeeringDB

5IPv4 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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269747, 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.182.124.0/24	Valid	Other IRR onlyRADB	101 15%	39
45.182.125.0/24	Valid	Other IRR onlyRADB	101 15%	39
45.182.126.0/24	Valid	Other IRR onlyRADB	101 15%	39
45.182.127.0/24	Valid	Other IRR onlyRADB	101 15%	39
45.182.124.0/22	Valid	RIR databaseLACNIC, RADB	671 100%	66
2803:b960::/32	Valid	RIR databaseLACNIC, RADB	634 100%	67

AS-SET

PeeringDB's irr_as_set for AS269747: AS269747 AS266725 AS15169 AS269747. 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 (AS269747 isn't in the set, or no route object for AS269747 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	AS269747 in it	Not covered
AS269747	A single AS number, not a set: AS269747 (this network), 6 route objects.
AS266725	A single AS number, not a set: AS266725, 14 route objects.
AS15169	A single AS number, not a set: AS15169, 2,122 route objects.
AS269747	A single AS number, not a set: AS269747 (this network), 6 route objects.

Name

Database

ASNs

Sets

Route objects

AS269747 in it

Not covered

AS269747

A single AS number, not a set: AS269747 (this network), 6 route objects.

AS266725

A single AS number, not a set: AS266725, 14 route objects.

AS15169

A single AS number, not a set: AS15169, 2,122 route objects.

AS269747

A single AS number, not a set: AS269747 (this network), 6 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	45.182.124.0/24	Route object only in RADB. Add it in the RIR database for the space.	101 of 673
Route object: RIR	45.182.125.0/24	Route object only in RADB. Add it in the RIR database for the space.	101 of 673
Route object: RIR	45.182.126.0/24	Route object only in RADB. Add it in the RIR database for the space.	101 of 673
Route object: RIR	45.182.127.0/24	Route object only in RADB. Add it in the RIR database for the space.	101 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.182.124.0/24

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

101 of 673

Route object: RIR

45.182.125.0/24

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

101 of 673

Route object: RIR

45.182.126.0/24

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

101 of 673

Route object: RIR

45.182.127.0/24

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

101 of 673

Route objects not announced

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