Network · data from 2026-11-12

AS272467 HI-MAX TELECOM

Registry name: AS272467 - HI-MAX TELECOM, BR · PeeringDB

0IPv4 routes

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

4Route objects not announced registered with origin AS272467, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272467, 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:81a4::/32	Valid	Other IRR onlyALTDB, RADB	631 99%	67
2804:81a4::/33	Valid	Other IRR onlyALTDB	629 99%	67
2804:81a4:8000::/33	Valid	Other IRR onlyALTDB	629 99%	67

AS-SET

PeeringDB's irr_as_set for AS272467: AS-HIMAXTELECOM. 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 (AS272467 isn't in the set, or no route object for AS272467 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	AS272467 in it	Not covered
AS-HIMAXTELECOM	ALTDB	6	1	1,892	Yes	0

Name

Database

ASNs

Sets

Route objects

AS272467 in it

Not covered

AS-HIMAXTELECOM

ALTDB

1,892

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

Route object: RIR3
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	2804:81a4::/32	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	631 of 636
Route object: RIR	2804:81a4::/33	Route object only in ALTDB. Add it in the RIR database for the space.	629 of 636
Route object: RIR	2804:81a4:8000::/33	Route object only in ALTDB. Add it in the RIR database for the space.	629 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

2804:81a4::/32

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

631 of 636

Route object: RIR

2804:81a4::/33

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

629 of 636

Route object: RIR

2804:81a4:8000::/33

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

629 of 636

Route objects not announced

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


2804:81a4::/34	ALTDB	Valid
2804:81a4:4000::/34	ALTDB	Valid
2804:81a4:8000::/34	ALTDB	Valid
2804:81a4:c000::/34	ALTDB	Valid

2804:81a4::/34

ALTDB

Valid

2804:81a4:4000::/34

ALTDB

Valid

2804:81a4:8000::/34

ALTDB

Valid

2804:81a4:c000::/34

ALTDB

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.