Network · data from 2026-11-12

AS265173 AS265173 - MEGAMAX TELECOM LTDA - ME

Registry name: AS265173 - MEGAMAX TELECOM LTDA - ME, BR · not in PeeringDB

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

2IPv6 routes 100.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

1Route objects not announced registered with origin AS265173, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265173, 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:2bc0::/35	Valid	Nonecovered by 2804:2bc0::/32	634 100%	67
167.249.244.0/24	Valid	Other IRR onlyRADB	670 100%	67
167.249.245.0/24	Valid	Other IRR onlyRADB	670 100%	67
167.249.246.0/24	Valid	Other IRR onlyRADB	667 99%	67
167.249.247.0/24	Valid	Other IRR onlyRADB	667 99%	67
2804:2bc0::/32	Valid	Other IRR onlyRADB, TC	631 99%	67
167.249.244.0/23	Valid	Other IRR onlyRADB	105 16%	39

AS-SET

AS265173 isn't in PeeringDB, where networks name their 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 8 are in fix.csv.

Route object: none1
Route object: RIR6
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:2bc0::/35	No route object for it. A route object for 2804:2bc0::/32 with origin AS265173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265173 in the RIR database for the space.	634 of 636
Route object: RIR	167.249.244.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	167.249.245.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	167.249.246.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	167.249.247.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	2804:2bc0::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	631 of 636
Route object: RIR	167.249.244.0/23	Route object only in RADB. Add it in the RIR database for the space.	105 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:2bc0::/35

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

634 of 636

Route object: RIR

167.249.244.0/24

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

670 of 673

Route object: RIR

167.249.245.0/24

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

670 of 673

Route object: RIR

167.249.246.0/24

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

667 of 673

Route object: RIR

167.249.247.0/24

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

667 of 673

Route object: RIR

2804:2bc0::/32

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

631 of 636

Route object: RIR

167.249.244.0/23

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

105 of 673

Route objects not announced

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


167.249.244.0/22	RADB, TC	No ROA

167.249.244.0/22

RADB, TC

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.