Network · data from 2026-11-12

AS328474 Jebo Connect

Registry name: Jebo Connect Pty Ltd - Jebo Connect 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

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS328474, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328474, 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.67.56.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.67.57.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.67.58.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.67.59.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.206.192.0/24	Valid	RIR databaseAFRINIC	671 100%	66
102.206.193.0/24	Valid	RIR databaseAFRINIC	671 100%	66
102.206.194.0/24	Valid	RIR databaseAFRINIC	671 100%	66
102.206.195.0/24	Valid	RIR databaseAFRINIC	671 100%	66
102.209.120.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.209.121.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.209.122.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.209.123.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.214.192.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.214.193.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.214.194.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.214.195.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.221.244.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.221.245.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.221.246.0/24	Valid	RIR databaseAFRINIC	671 100%	68
102.221.247.0/24	Valid	RIR databaseAFRINIC	671 100%	68
2c0f:ed60::/32	Valid	RIR databaseAFRINIC	635 100%	69

AS-SET

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

Name	Database	ASNs	Sets	Route objects	AS328474 in it	Not covered
AS-JEBOCONNECT	AFRINIC	1	1	21	Yes	0

Name

Database

ASNs

Sets

Route objects

AS328474 in it

Not covered

AS-JEBOCONNECT

AFRINIC

Yes

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 AS328474 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.