bgpreport

Network · data from 2026-11-12

AS7582 UMAC-AS-AP - University of Macau

Registry name: UMAC-AS-AP - University of Macau, MO · not in PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.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 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS7582, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS7582, 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.
2001:ff8::/40 No ROA RIR databaseAPNIC 636 100% 67
161.64.0.0/17 Valid RIR databaseAPNIC 673 100% 67
161.64.128.0/17 Valid RIR databaseAPNIC 673 100% 67

AS-SET

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

  • ROA: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2001:ff8::/40No ROA covers it. Add a ROA for AS7582, maxLength 40.636 of 636

Route objects not announced

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

161.64.0.0/16APNIC, NTTCOM, RADBValid
2001:ff8::/32RADBNo ROA
2001:ff8:1::/48RADBNo 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.