Network · data from 2026-11-12

AS263524 Ciabrasnet - Central Brasileira de Internet Ltda

Registry name: AS263524 - Ciabrasnet - Central Brasileira de Internet Ltda, BR · PeeringDB

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

7Route objects not announced registered with origin AS263524, seen from no peer

Announced routes

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


191.253.26.0/23	Valid	Other IRR onlyTC	672 100%	67
191.253.29.0/24	Valid	Other IRR onlyTC	672 100%	67
191.253.24.0/21	Valid	Other IRR onlyTC	671 100%	67
191.253.25.0/24	Valid	Other IRR onlyTC	671 100%	67
191.253.24.0/24	Valid	Other IRR onlyTC	670 100%	67
191.253.26.0/24	Valid	Other IRR onlyTC	670 100%	67
191.253.28.0/23	Valid	Other IRR onlyTC	670 100%	67
191.253.27.0/24	Valid	Other IRR onlyTC	669 99%	67
2804:1340::/32	Valid	Other IRR onlyRADB, TC	636 100%	69
2804:1340:8000::/33	Valid	Other IRR onlyTC	636 100%	67
2804:1340::/33	Valid	Other IRR onlyTC	635 100%	69

AS-SET

PeeringDB's irr_as_set for AS263524: AS-263524. 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 (AS263524 isn't in the set, or no route object for AS263524 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	AS263524 in it	Not covered
AS-263524	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS263524 in it

Not covered

AS-263524

In no IRR database read today.

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

Route object: RIR11
AS-SET: not found1
Route object: not announced7

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	191.253.26.0/23	Route object only in TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	191.253.29.0/24	Route object only in TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	191.253.24.0/21	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	191.253.25.0/24	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	191.253.24.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	191.253.26.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	191.253.28.0/23	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	191.253.27.0/24	Route object only in TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2804:1340::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	636 of 636
Route object: RIR	2804:1340:8000::/33	Route object only in TC. Add it in the RIR database for the space.	636 of 636
Route object: RIR	2804:1340::/33	Route object only in TC. Add it in the RIR database for the space.	635 of 636
AS-SET: not found	AS-263524	PeeringDB names AS-263524; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

191.253.26.0/23

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

672 of 673

Route object: RIR

191.253.29.0/24

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

672 of 673

Route object: RIR

191.253.24.0/21

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

671 of 673

Route object: RIR

191.253.25.0/24

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

671 of 673

Route object: RIR

191.253.24.0/24

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

670 of 673

Route object: RIR

191.253.26.0/24

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

670 of 673

Route object: RIR

191.253.28.0/23

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

670 of 673

Route object: RIR

191.253.27.0/24

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

669 of 673

Route object: RIR

2804:1340::/32

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

636 of 636

Route object: RIR

2804:1340:8000::/33

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

636 of 636

Route object: RIR

2804:1340::/33

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

635 of 636

AS-SET: not found

AS-263524

PeeringDB names AS-263524; no IRR database read has it.

Route objects not announced

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


191.253.24.0/22	TC	Valid
191.253.24.0/23	TC	Valid
191.253.28.0/22	RADB, TC	Valid
191.253.28.0/24	TC	Valid
191.253.30.0/23	TC	Valid
191.253.30.0/24	TC	Valid
191.253.31.0/24	TC	Valid

191.253.24.0/22

Valid

191.253.24.0/23

Valid

191.253.28.0/22

RADB, TC

Valid

191.253.28.0/24

Valid

191.253.30.0/23

Valid

191.253.30.0/24

Valid

191.253.31.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.