Network · data from 2026-11-12

AS22706 MAZA Global Carrier

Registry name: AS22706 - MAZA Global Carrier, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 50.0% with a route object

1IPv6 routes 0.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 2 with no route object for this origin

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

15Route objects not announced registered with origin AS22706, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS22706, 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:9a10::/32	No ROA	Other IRR onlyTC	632 99%	67
200.152.80.0/21	Valid	Nonecovered by 200.152.80.0/20	671 100%	67
200.152.88.0/21	Valid	Nonecovered by 200.152.80.0/20	670 100%	67
200.152.80.0/20	Valid	Other IRR onlyTC	671 100%	67
200.152.93.0/24	Valid	Other IRR onlyTC	670 100%	67

AS-SET

AS22706'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 21 are in fix.csv.

ROA: none1
Route object: none2
Route object: RIR3
Route object: not announced15

Change	Prefix or set	Detail	Full-table peers
ROA: none	2804:9a10::/32	No ROA covers it. Add a ROA for AS22706, maxLength 32.	632 of 636
Route object: RIR	2804:9a10::/32	Route object only in TC. Add it in the RIR database for the space.	632 of 636
Route object: none	200.152.80.0/21	No route object for it. A route object for 200.152.80.0/20 with origin AS22706 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22706 in the RIR database for the space.	671 of 673
Route object: none	200.152.88.0/21	No route object for it. A route object for 200.152.80.0/20 with origin AS22706 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22706 in the RIR database for the space.	670 of 673
Route object: RIR	200.152.80.0/20	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	200.152.93.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

2804:9a10::/32

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

632 of 636

Route object: RIR

2804:9a10::/32

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

632 of 636

Route object: none

200.152.80.0/21

No route object for it. A route object for 200.152.80.0/20 with origin AS22706 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22706 in the RIR database for the space.

671 of 673

Route object: none

200.152.88.0/21

670 of 673

Route object: RIR

200.152.80.0/20

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

671 of 673

Route object: RIR

200.152.93.0/24

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

670 of 673

Route objects not announced

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


200.152.80.0/24	TC	Valid
200.152.81.0/24	TC	Valid
200.152.82.0/24	TC	Valid
200.152.83.0/24	TC	Valid
200.152.84.0/24	TC	Valid
200.152.85.0/24	TC	Valid
200.152.86.0/24	TC	Valid
200.152.87.0/24	TC	Valid
200.152.88.0/24	TC	Valid
200.152.89.0/24	TC	Valid
200.152.90.0/24	TC	Valid
200.152.91.0/24	TC	Valid
200.152.92.0/24	TC	Valid
200.152.94.0/24	TC	Valid
200.152.95.0/24	TC	Valid

200.152.80.0/24

Valid

200.152.81.0/24

Valid

200.152.82.0/24

Valid

200.152.83.0/24

Valid

200.152.84.0/24

Valid

200.152.85.0/24

Valid

200.152.86.0/24

Valid

200.152.87.0/24

Valid

200.152.88.0/24

Valid

200.152.89.0/24

Valid

200.152.90.0/24

Valid

200.152.91.0/24

Valid

200.152.92.0/24

Valid

200.152.94.0/24

Valid

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