Network · data from 2026-11-12

AS269145 Ciabrasnet Filial

Registry name: AS269145 - WNKBR TELECOM, BR · PeeringDB

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

7IPv6 routes 100.0% RPKI valid · 42.9% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 4 with no route object for this origin

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

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

Announced routes

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


2804:6018::/34	Valid	Nonecovered by 2804:6018::/33	636 100%	67
2804:6018:4000::/34	Valid	Nonecovered by 2804:6018::/33	636 100%	67
2804:6018:8000::/34	Valid	Nonecovered by 2804:6018:8000::/33	636 100%	67
2804:6018:c000::/34	Valid	Nonecovered by 2804:6018:8000::/33	636 100%	67
45.180.184.0/24	Valid	Other IRR onlyTC	671 100%	67
45.180.185.0/24	Valid	Other IRR onlyTC	671 100%	67
45.180.187.0/24	Valid	Other IRR onlyTC	671 100%	67
45.180.184.0/22	Valid	Other IRR onlyRADB, TC	670 100%	66
45.180.184.0/23	Valid	Other IRR onlyTC	670 100%	66
45.180.186.0/23	Valid	Other IRR onlyTC	670 100%	66
45.180.186.0/24	Valid	Other IRR onlyTC	670 100%	67
2804:6018::/32	Valid	Other IRR onlyRADB, TC	636 100%	69
2804:6018::/33	Valid	Other IRR onlyTC	636 100%	69
2804:6018:8000::/33	Valid	Other IRR onlyTC	636 100%	69

AS-SET

AS269145's PeeringDB record names no AS-SET.

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

Route object: none4
Route object: RIR10

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:6018::/34	No route object for it. A route object for 2804:6018::/33 with origin AS269145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269145 in the RIR database for the space.	636 of 636
Route object: none	2804:6018:4000::/34	No route object for it. A route object for 2804:6018::/33 with origin AS269145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269145 in the RIR database for the space.	636 of 636
Route object: none	2804:6018:8000::/34	No route object for it. A route object for 2804:6018:8000::/33 with origin AS269145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269145 in the RIR database for the space.	636 of 636
Route object: none	2804:6018:c000::/34	No route object for it. A route object for 2804:6018:8000::/33 with origin AS269145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269145 in the RIR database for the space.	636 of 636
Route object: RIR	45.180.184.0/24	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.180.185.0/24	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.180.187.0/24	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.180.184.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.180.184.0/23	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.180.186.0/23	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.180.186.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	2804:6018::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	636 of 636
Route object: RIR	2804:6018::/33	Route object only in TC. Add it in the RIR database for the space.	636 of 636
Route object: RIR	2804:6018:8000::/33	Route object only in TC. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:6018::/34

No route object for it. A route object for 2804:6018::/33 with origin AS269145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269145 in the RIR database for the space.

636 of 636

Route object: none

2804:6018:4000::/34

636 of 636

Route object: none

2804:6018:8000::/34

No route object for it. A route object for 2804:6018:8000::/33 with origin AS269145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269145 in the RIR database for the space.

636 of 636

Route object: none

2804:6018:c000::/34

636 of 636

Route object: RIR

45.180.184.0/24

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

671 of 673

Route object: RIR

45.180.185.0/24

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

671 of 673

Route object: RIR

45.180.187.0/24

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

671 of 673

Route object: RIR

45.180.184.0/22

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

670 of 673

Route object: RIR

45.180.184.0/23

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

670 of 673

Route object: RIR

45.180.186.0/23

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

670 of 673

Route object: RIR

45.180.186.0/24

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

670 of 673

Route object: RIR

2804:6018::/32

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

636 of 636

Route object: RIR

2804:6018::/33

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

636 of 636

Route object: RIR

2804:6018:8000::/33

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

636 of 636

Route objects not announced

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