bgpreport

Network · data from 2026-11-12

AS328628 Wanderport Swaziland

Registry name: Wanderport Swaziland - Wanderport Swaziland, SZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328628, 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:4620::/32 Valid None 634 100% 67
102.67.144.0/22 Valid RIR databaseAFRINIC 672 100% 66
102.67.145.0/24 Valid RIR databaseAFRINIC 672 100% 66
102.67.147.0/24 Valid RIR databaseAFRINIC 672 100% 66
102.67.146.0/24 Valid RIR databaseAFRINIC 670 100% 67
102.67.144.0/23 Valid RIR databaseAFRINIC 669 99% 68

AS-SET

PeeringDB's irr_as_set for AS328628: AS-WS2. 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 (AS328628 isn't in the set, or no route object for AS328628 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 objectsAS328628 in itNot covered
AS-WS2 AFRINIClists itself further down 2118 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 3 are in fix.csv.

  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2c0f:4620::/32No route object for it. Add a route object with origin AS328628 in the RIR database for the space.634 of 636

Route objects not announced

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

102.67.144.0/24AFRINICValid
102.67.146.0/23AFRINICValid

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.