bgpreport

Network · data from 2026-11-12

AS329153 SWDconnect

Registry name: ISWCORP (PTY) LTD - ISWCORP (PTY) LTD, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329153, 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.
102.134.92.0/22 Valid RIR databaseAFRINIC 672 100% 67
102.208.208.0/22 Valid RIR databaseAFRINIC 672 100% 67
102.217.88.0/22 Valid RIR databaseAFRINIC 672 100% 67
102.222.192.0/22 Valid RIR databaseAFRINIC 672 100% 67
2c0f:f80::/32 Valid RIR databaseAFRINIC 634 100% 67
102.134.92.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.134.93.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.134.94.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.134.95.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.208.208.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.208.209.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.208.210.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.208.211.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.217.88.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.217.89.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.217.90.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.217.91.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.222.192.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.222.193.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.222.194.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18
102.222.195.0/24 Valid RIR databaseAFRINIC 43 6%low visibility 18

AS-SET

PeeringDB's irr_as_set for AS329153: AS-SWDCONNECT. 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 (AS329153 isn't in the set, or no route object for AS329153 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 objectsAS329153 in itNot covered
AS-SWDCONNECT AFRINIC 1121 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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