bgpreport

Network · data from 2026-11-12

AS6083 Posix Systems

Registry name: Posix Systems (Pty) Ltd - Posix Systems (Pty) Ltd, ZA · PeeringDB

11IPv4 routes 90.9% 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
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS6083, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS6083, 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.

192.96.24.0/21 No ROA Other IRR onlyRIPE-NONAUTH 673 100% 66
192.94.246.0/24 Valid RIR databaseAFRINIC 673 100% 66
192.96.24.0/24 Valid RIR databaseAFRINIC 670 100% 66
192.96.177.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 670 100% 66
2001:42a0::/32 Valid RIR databaseAFRINIC, RIPE-NONAUTH 632 99% 69
192.96.25.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 157 23% 44
192.96.26.0/24 Valid RIR databaseAFRINIC 157 23% 44
192.96.27.0/24 Valid RIR databaseAFRINIC 157 23% 44
192.96.28.0/24 Valid RIR databaseAFRINIC 157 23% 44
192.96.29.0/24 Valid RIR databaseAFRINIC 157 23% 44
192.96.30.0/24 Valid RIR databaseAFRINIC 157 23% 44
192.96.31.0/24 Valid RIR databaseAFRINIC 157 23% 44

AS-SET

PeeringDB's irr_as_set for AS6083: AFRINIC::AS-POSIX. 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 (AS6083 isn't in the set, or no route object for AS6083 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 objectsAS6083 in itNot covered
AFRINIC::AS-POSIX AFRINIC 2114 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 3 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none192.96.24.0/21No ROA covers it. Add a ROA for AS6083, maxLength 21.673 of 673
Route object: RIR192.96.24.0/21Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

160.124.0.0/16AFRINICInvalid: origin

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.