Network · data from 2026-11-12

AS272219 GRUPO CARDOSO DE COMUNICACAO

Registry name: AS272219 - GRUPO CARDOSO DE COMUNICACAO, BR · PeeringDB

0IPv4 routes

8IPv6 routes 0.0% RPKI valid · 12.5% with a route object

5RPKI invalid 5 origin · 0 maxLength

3No ROA 7 with no route object for this origin

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

2Route objects not announced registered with origin AS272219, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272219, 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:6038:8200::/40	Invalid: origin	None	49 8%low visibility	30
2804:6038:8300::/40	Invalid: origin	None	49 8%low visibility	30
2804:6038::/32	Invalid: origin	Other origin only	5 1%low visibility	5
2804:6038::/33	Invalid: origin	None	5 1%low visibility	5
2804:6038:8000::/33	Invalid: origin	None	5 1%low visibility	5
2804:83c8:8200::/40	No ROA	Nonecovered by 2804:83c8:8000::/33	635 100%	67
2804:83c8:8300::/40	No ROA	Nonecovered by 2804:83c8:8000::/33	635 100%	67
2804:83c8::/32	No ROA	Other IRR onlyTC	635 100%	67

2804:6038:8200::/40

Invalid: origin

None

49 8%low visibility

2804:6038:8300::/40

Invalid: origin

None

49 8%low visibility

2804:6038::/32

Invalid: origin

Other origin only

5 1%low visibility

2804:6038::/33

Invalid: origin

None

5 1%low visibility

2804:6038:8000::/33

Invalid: origin

None

5 1%low visibility

2804:83c8:8200::/40

No ROA

Nonecovered by 2804:83c8:8000::/33

635 100%

2804:83c8:8300::/40

No ROA

Nonecovered by 2804:83c8:8000::/33

635 100%

2804:83c8::/32

No ROA

Other IRR onlyTC

635 100%

AS-SET

PeeringDB's irr_as_set for AS272219: TC::AS272219:AS-GRUPOCARDOSO. 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 (AS272219 isn't in the set, or no route object for AS272219 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	AS272219 in it	Not covered
TC::AS272219:AS-GRUPOCARDOSO	TC	1	2	3	Yes	5

Name

Database

ASNs

Sets

Route objects

AS272219 in it

Not covered

TC::AS272219:AS-GRUPOCARDOSO

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

ROA: origin5
ROA: none3
Route object: none7
Route object: RIR1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	2804:6038:8200::/40	ROAs covering it name AS269153, not AS272219. If AS272219 should announce it, add a ROA for AS272219.	49 of 636
Route object: none	2804:6038:8200::/40	No route object for it. Add a route object with origin AS272219 in the RIR database for the space.	49 of 636
ROA: origin	2804:6038:8300::/40	ROAs covering it name AS269153, not AS272219. If AS272219 should announce it, add a ROA for AS272219.	49 of 636
Route object: none	2804:6038:8300::/40	No route object for it. Add a route object with origin AS272219 in the RIR database for the space.	49 of 636
ROA: origin	2804:6038::/32	ROAs covering it name AS269153, not AS272219. If AS272219 should announce it, add a ROA for AS272219.	5 of 636
Route object: none	2804:6038::/32	Route objects for it name AS269153. Add a route object with origin AS272219 in the RIR database for the space.	5 of 636
ROA: origin	2804:6038::/33	ROAs covering it name AS269153, not AS272219. If AS272219 should announce it, add a ROA for AS272219.	5 of 636
Route object: none	2804:6038::/33	No route object for it. Add a route object with origin AS272219 in the RIR database for the space.	5 of 636
ROA: origin	2804:6038:8000::/33	ROAs covering it name AS269153, not AS272219. If AS272219 should announce it, add a ROA for AS272219.	5 of 636
Route object: none	2804:6038:8000::/33	No route object for it. Add a route object with origin AS272219 in the RIR database for the space.	5 of 636
ROA: none	2804:83c8:8200::/40	No ROA covers it. Add a ROA for AS272219, maxLength 40.	635 of 636
Route object: none	2804:83c8:8200::/40	No route object for it. A route object for 2804:83c8:8000::/33 with origin AS272219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272219 in the RIR database for the space.	635 of 636
ROA: none	2804:83c8:8300::/40	No ROA covers it. Add a ROA for AS272219, maxLength 40.	635 of 636
Route object: none	2804:83c8:8300::/40	No route object for it. A route object for 2804:83c8:8000::/33 with origin AS272219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272219 in the RIR database for the space.	635 of 636
ROA: none	2804:83c8::/32	No ROA covers it. Add a ROA for AS272219, maxLength 32.	635 of 636
Route object: RIR	2804:83c8::/32	Route object only in TC. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: origin

2804:6038:8200::/40

ROAs covering it name AS269153, not AS272219. If AS272219 should announce it, add a ROA for AS272219.

49 of 636

Route object: none

2804:6038:8200::/40

No route object for it. Add a route object with origin AS272219 in the RIR database for the space.

49 of 636

ROA: origin

2804:6038:8300::/40

ROAs covering it name AS269153, not AS272219. If AS272219 should announce it, add a ROA for AS272219.

49 of 636

Route object: none

2804:6038:8300::/40

No route object for it. Add a route object with origin AS272219 in the RIR database for the space.

49 of 636

ROA: origin

2804:6038::/32

ROAs covering it name AS269153, not AS272219. If AS272219 should announce it, add a ROA for AS272219.

5 of 636

Route object: none

2804:6038::/32

Route objects for it name AS269153. Add a route object with origin AS272219 in the RIR database for the space.

5 of 636

ROA: origin

2804:6038::/33

ROAs covering it name AS269153, not AS272219. If AS272219 should announce it, add a ROA for AS272219.

5 of 636

Route object: none

2804:6038::/33

No route object for it. Add a route object with origin AS272219 in the RIR database for the space.

5 of 636

ROA: origin

2804:6038:8000::/33

ROAs covering it name AS269153, not AS272219. If AS272219 should announce it, add a ROA for AS272219.

5 of 636

Route object: none

2804:6038:8000::/33

No route object for it. Add a route object with origin AS272219 in the RIR database for the space.

5 of 636

ROA: none

2804:83c8:8200::/40

No ROA covers it. Add a ROA for AS272219, maxLength 40.

635 of 636

Route object: none

2804:83c8:8200::/40

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

635 of 636

ROA: none

2804:83c8:8300::/40

No ROA covers it. Add a ROA for AS272219, maxLength 40.

635 of 636

Route object: none

2804:83c8:8300::/40

635 of 636

ROA: none

2804:83c8::/32

No ROA covers it. Add a ROA for AS272219, maxLength 32.

635 of 636

Route object: RIR

2804:83c8::/32

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

635 of 636

Route objects not announced

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


2804:83c8::/33	TC	No ROA
2804:83c8:8000::/33	TC	No ROA

2804:83c8::/33

No ROA

2804:83c8:8000::/33

No ROA

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.