bgpreport

Network · data from 2026-11-12

AS21232 GGA Maur

Registry name: GGAMAUR Genossenschaft GGA Maur, CH · PeeringDB

19IPv4 routes 94.7% RPKI valid · 94.7% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS21232, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21232, 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.
185.64.184.0/22 Invalid: origin Other origin only 3 0%low visibility 3
62.32.0.0/19 Valid RIR databaseRIPE 673 100% 67
77.74.56.0/21 Valid RIR databaseRIPE 673 100% 67
79.142.128.0/20 Valid RIR databaseRIPE 673 100% 67
82.192.224.0/19 Valid RIR databaseRIPE 673 100% 67
93.184.16.0/20 Valid RIR databaseRIPE 673 100% 67
185.31.248.0/22 Valid RIR databaseRIPE 673 100% 67
185.41.132.0/22 Valid RIR databaseRIPE 673 100% 67
185.45.236.0/22 Valid RIR databaseRIPE 673 100% 67
185.110.72.0/22 Valid RIR databaseRIPE 673 100% 67
185.110.88.0/22 Valid RIR databaseRIPE 673 100% 67
185.110.184.0/22 Valid RIR databaseRIPE 673 100% 67
185.119.36.0/22 Valid RIR databaseRIPE 673 100% 67
185.132.16.0/22 Valid RIR databaseRIPE 673 100% 67
185.193.224.0/22 Valid RIR databaseRIPE 673 100% 67
194.147.113.0/24 Valid RIR databaseRIPE 673 100% 67
195.216.64.0/19 Valid RIR databaseRIPE 673 100% 67
213.160.32.0/19 Valid RIR databaseRIPE 673 100% 67
213.188.32.0/19 Valid RIR databaseRIPE 673 100% 67
2a02:5c0::/32 Valid RIR databaseRIPE 636 100% 67
2a14:5300::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS21232: AS-GGAMAUR. 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 (AS21232 isn't in the set, or no route object for AS21232 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.

NameDatabaseASNsSets Route objectsAS21232 in itNot covered
AS-GGAMAUR RIPE 1120 Yes 1

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: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin185.64.184.0/22ROAs covering it name AS1299, AS47176, not AS21232. If AS21232 should announce it, add a ROA for AS21232.3 of 673
Route object: none185.64.184.0/22Route objects for it name AS47176. Add a route object with origin AS21232 in the RIR database for the space.3 of 673

Route objects not announced

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