bgpreport

Network · data from 2026-11-12

AS328942 Imvula iTech

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328942, 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.218.40.0/23 No ROA RIR databaseAFRINIC 669 99% 66
102.218.40.0/24 No ROA RIR databaseAFRINIC 104 15% 38
102.218.41.0/24 No ROA RIR databaseAFRINIC 104 15% 38

AS-SET

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

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

  • ROA: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none102.218.40.0/23No ROA covers it. Add a ROA for AS328942, maxLength 23.669 of 673
ROA: none102.218.40.0/24No ROA covers it. Add a ROA for AS328942, maxLength 24.104 of 673
ROA: none102.218.41.0/24No ROA covers it. Add a ROA for AS328942, maxLength 24.104 of 673

Route objects not announced

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

102.218.40.0/22AFRINICNo ROA
2c0f:7d00::/32AFRINICNo 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.