Network · data from 2026-11-12

AS273421 MAZA Telecom

Registry name: AS273421 - MAZA Telecom, BR · PeeringDB

0IPv4 routes

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

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273421, 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:8e64::/32	Valid	Other IRR onlyRADB, TC	370 58%	65

2804:8e64::/32

Valid

Other IRR onlyRADB, TC

370 58%

AS-SET

PeeringDB's irr_as_set for AS273421: AS273421:AS-MAZA. 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 (AS273421 isn't in the set, or no route object for AS273421 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	AS273421 in it	Not covered
AS273421:AS-MAZA	TClists itself further down1 member set in no database: AS267484:AS-CUSTOMERS	2,791	71	390,068	Yes	0

Name

Database

ASNs

Sets

Route objects

AS273421 in it

Not covered

AS273421:AS-MAZA

TClists itself further down1 member set in no database: AS267484:AS-CUSTOMERS

2,791

390,068

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

Route object: RIR1
AS-SET: missing member1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	2804:8e64::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	370 of 636
AS-SET: missing member	AS273421:AS-MAZA	AS273421:AS-MAZA (TC) lists AS267484:AS-CUSTOMERS; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

2804:8e64::/32

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

370 of 636

AS-SET: missing member

AS273421:AS-MAZA

AS273421:AS-MAZA (TC) lists AS267484:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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