bgpreport

Network · data from 2026-11-12

AS327767 Ultimate Linux Solutions

Registry name: Ultimate Linux Solutions (Pty) Ltd - Ultimate Linux Solutions (Pty) Ltd, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS327767, 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.
165.16.206.0/23 Invalid: maxLength RIR databaseAFRINIC 2 0%low visibility 2
165.16.207.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.214.182.0/23 Valid RIR databaseAFRINIC 671 100% 68
102.218.132.0/22 Valid RIR databaseAFRINIC 671 100% 68
154.73.32.0/22 Valid RIR databaseAFRINIC 671 100% 68
165.16.200.0/21 Valid RIR databaseAFRINIC 671 100% 68
2c0f:f720::/32 Valid RIR databaseAFRINIC 636 100% 69
2c0f:f720:1000::/40 Valid RIR databaseAFRINIC 632 99% 67
102.214.182.0/24 Valid RIR databaseAFRINIC 64 10%low visibility 21
102.214.183.0/24 Valid RIR databaseAFRINIC 64 10%low visibility 21
102.218.132.0/23 Valid RIR databaseAFRINIC 64 10%low visibility 21
102.218.134.0/23 Valid RIR databaseAFRINIC 64 10%low visibility 21
154.73.32.0/23 Valid RIR databaseAFRINIC 64 10%low visibility 21
165.16.200.0/22 Valid RIR databaseAFRINIC 64 10%low visibility 21
165.16.204.0/22 Valid RIR databaseAFRINIC 64 10%low visibility 21
154.73.34.0/23 Valid RIR databaseAFRINIC 61 9%low visibility 20
2c0f:f720::/33 Valid RIR databaseAFRINIC 40 6%low visibility 17
2c0f:f720:8000::/33 Valid RIR databaseAFRINIC 40 6%low visibility 17

AS-SET

PeeringDB's irr_as_set for AS327767: AS327767:AS-ULS. 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 (AS327767 isn't in the set, or no route object for AS327767 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 objectsAS327767 in itNot covered
AS327767:AS-ULS AFRINIC 8480 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 1 are in fix.csv.

  • ROA: maxLength1
ChangePrefix or setDetailFull-table peers
ROA: maxLength165.16.206.0/23ROA 165.16.200.0/21 AS327767 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 165.16.206.0/23.2 of 673

Route objects not announced

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