Network · data from 2026-11-12

AS267397 SKYNET ARUJA

Registry name: AS267397 - SKYNET ARUJA TELECOM LTDA, BR · 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 AS267397, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267397, 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.233.204.0/22	Valid	Other IRR onlyRADB, TC	671 100%	67
2804:4cdc::/32	Valid	Other IRR onlyRADB, TC	634 100%	67
2804:4cdc::/33	Valid	Other IRR onlyRADB, TC	348 55%	65
2804:4cdc:8000::/33	Valid	Other IRR onlyRADB, TC	348 55%	65
45.233.205.0/24	Valid	Other IRR onlyTC	226 34%	58
45.233.206.0/24	Valid	Other IRR onlyRADB, TC	225 33%	58
45.233.207.0/24	Valid	Other IRR onlyRADB, TC	225 33%	58
45.233.204.0/24	Valid	Other IRR onlyTC	224 33%	58

AS-SET

PeeringDB's irr_as_set for AS267397: AS267397: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 (AS267397 isn't in the set, or no route object for AS267397 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	AS267397 in it	Not covered
AS267397:AS-ANNOUNCEMENTS	TC	1	2	8	Yes	0

Name

Database

ASNs

Sets

Route objects

AS267397 in it

Not covered

AS267397:AS-ANNOUNCEMENTS

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

Route object: RIR8

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.233.204.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:4cdc::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:4cdc::/33	Route object only in RADB, TC. Add it in the RIR database for the space.	348 of 636
Route object: RIR	2804:4cdc:8000::/33	Route object only in RADB, TC. Add it in the RIR database for the space.	348 of 636
Route object: RIR	45.233.205.0/24	Route object only in TC. Add it in the RIR database for the space.	226 of 673
Route object: RIR	45.233.206.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	225 of 673
Route object: RIR	45.233.207.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	225 of 673
Route object: RIR	45.233.204.0/24	Route object only in TC. Add it in the RIR database for the space.	224 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.233.204.0/22

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

671 of 673

Route object: RIR

2804:4cdc::/32

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

634 of 636

Route object: RIR

2804:4cdc::/33

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

348 of 636

Route object: RIR

2804:4cdc:8000::/33

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

348 of 636

Route object: RIR

45.233.205.0/24

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

226 of 673

Route object: RIR

45.233.206.0/24

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

225 of 673

Route object: RIR

45.233.207.0/24

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

225 of 673

Route object: RIR

45.233.204.0/24

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

224 of 673

Route objects not announced

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