Network · data from 2026-11-12

AS272459 CINET TELECOMUNICACOES

Registry name: AS272459 - CINET TELECOMUNICACOES EIRELI, BR · PeeringDB

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

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

4Route objects not announced registered with origin AS272459, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272459, 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.184.204.0/22	Valid	Other IRR onlyTC	671 100%	67
2804:8184::/32	Valid	Other IRR onlyTC	634 100%	67
45.184.204.0/23	Valid	Other IRR onlyTC	2 0%low visibility	2
45.184.206.0/23	Valid	Other IRR onlyTC	2 0%low visibility	2

45.184.204.0/22

Valid

Other IRR onlyTC

671 100%

2804:8184::/32

Valid

Other IRR onlyTC

634 100%

45.184.204.0/23

Valid

Other IRR onlyTC

2 0%low visibility

45.184.206.0/23

Valid

Other IRR onlyTC

2 0%low visibility

AS-SET

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

Name

Database

ASNs

Sets

Route objects

AS272459 in it

Not covered

AS272459:AS-ALL

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: RIR4
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.184.204.0/22	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2804:8184::/32	Route object only in TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	45.184.204.0/23	Route object only in TC. Add it in the RIR database for the space.	2 of 673
Route object: RIR	45.184.206.0/23	Route object only in TC. Add it in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.184.204.0/22

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

671 of 673

Route object: RIR

2804:8184::/32

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

634 of 636

Route object: RIR

45.184.204.0/23

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

2 of 673

Route object: RIR

45.184.206.0/23

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

2 of 673

Route objects not announced

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


45.184.204.0/24	TC	Valid
45.184.205.0/24	TC	Valid
45.184.206.0/24	TC	Valid
45.184.207.0/24	TC	Valid

45.184.204.0/24

Valid

45.184.205.0/24

Valid

45.184.206.0/24

Valid

45.184.207.0/24

Valid

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.