bgpreport

Network · data from 2026-11-12

AS328206 Johannesburg Wireless User Group

Registry name: Johannesburg Area Wireless User Group (JAWUG) - Johannesburg Area Wireless User Group (JAWUG), ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328206, 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.
2c0f:f2a0:1007::/64 Invalid: origin None 1 0%low visibility 2
172.25.245.0/24 bogon No ROA None 0 0%low visibility 1
172.25.246.0/24 bogon No ROA None 0 0%low visibility 1
2c0f:2c40:cc11:e03:1150::/126 No ROA None 1 0%low visibility 2
2001:43f8:360::/48 Valid RIR databaseAFRINIC 634 100% 69
2c0f:2c40:ffff::/48 Valid RIR databaseAFRINIC 1 0%low visibility 2

AS-SET

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

  • ROA: origin1
  • Bogon prefix2
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin2c0f:f2a0:1007::/64ROAs covering it name AS327849, not AS328206. If AS328206 should announce it, add a ROA for AS328206.1 of 636
Route object: none2c0f:f2a0:1007::/64No route object for it. Add a route object with origin AS328206 in the RIR database for the space.1 of 636
Bogon prefix172.25.245.0/24In IANA's special-purpose registry: Private-Use (RFC 1918).0 of 673
Bogon prefix172.25.246.0/24In IANA's special-purpose registry: Private-Use (RFC 1918).0 of 673
ROA: none2c0f:2c40:cc11:e03:1150::/126No ROA covers it. Add a ROA for AS328206, maxLength 126.1 of 636
Route object: none2c0f:2c40:cc11:e03:1150::/126No route object for it. Add a route object with origin AS328206 in the RIR database for the space.1 of 636

Route objects not announced

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