Network · data from 2026-11-12

AS25626 MMB Networks

Registry name: MMB-ASN-01 - MMB Networks, CA · PeeringDB

0IPv4 routes

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

0RPKI invalid 0 origin · 0 maxLength

2No 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 AS25626, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25626, 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.


2602:816:4000::/44	No ROA	RIR databaseARIN	636 100%	67
2602:816:4000::/48	No ROA	RIR databaseARIN	636 100%	67

AS-SET

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

ROA: none2

Change	Prefix or set	Detail	Full-table peers
ROA: none	2602:816:4000::/44	No ROA covers it. Add a ROA for AS25626, maxLength 44.	636 of 636
ROA: none	2602:816:4000::/48	No ROA covers it. Add a ROA for AS25626, maxLength 48.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2602:816:4000::/44

No ROA covers it. Add a ROA for AS25626, maxLength 44.

636 of 636

ROA: none

2602:816:4000::/48

No ROA covers it. Add a ROA for AS25626, maxLength 48.

636 of 636

Route objects not announced

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