bgpreport

Network · data from 2026-11-12

AS328015 Sombha Solutions Store

Registry name: Sombha Solutions Store Limited - Sombha Solutions Store Limited, UG · PeeringDB

9IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
9No 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 AS328015, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328015, 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.68.172.0/24 No ROA RIR databaseAFRINIC 672 100% 66
102.68.173.0/24 No ROA RIR databaseAFRINIC 672 100% 66
102.68.174.0/24 No ROA RIR databaseAFRINIC 672 100% 66
164.160.4.0/24 No ROA RIR databaseAFRINIC, RADB, RIPE-NONAUTH 672 100% 66
164.160.5.0/24 No ROA RIR databaseAFRINIC, RADB, RIPE-NONAUTH 672 100% 66
164.160.6.0/24 No ROA RIR databaseAFRINIC, RADB, RIPE-NONAUTH 672 100% 66
164.160.7.0/24 No ROA RIR databaseAFRINIC, RADB, RIPE-NONAUTH 672 100% 66
164.160.4.0/22 No ROA RIR databaseAFRINIC, RADB, RIPE-NONAUTH 670 100% 68
102.68.172.0/22 No ROA RIR databaseAFRINIC 669 99% 68

AS-SET

PeeringDB's irr_as_set for AS328015: AFRINIC::AS328015. 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 (AS328015 isn't in the set, or no route object for AS328015 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 objectsAS328015 in itNot covered
AFRINIC::AS328015 A single AS number, not a set: AS328015 (this network), 11 route objects.

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

  • ROA: none9
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none102.68.172.0/24No ROA covers it. Add a ROA for AS328015, maxLength 24.672 of 673
ROA: none102.68.173.0/24No ROA covers it. Add a ROA for AS328015, maxLength 24.672 of 673
ROA: none102.68.174.0/24No ROA covers it. Add a ROA for AS328015, maxLength 24.672 of 673
ROA: none164.160.4.0/24No ROA covers it. Add a ROA for AS328015, maxLength 24.672 of 673
ROA: none164.160.5.0/24No ROA covers it. Add a ROA for AS328015, maxLength 24.672 of 673
ROA: none164.160.6.0/24No ROA covers it. Add a ROA for AS328015, maxLength 24.672 of 673
ROA: none164.160.7.0/24No ROA covers it. Add a ROA for AS328015, maxLength 24.672 of 673
ROA: none164.160.4.0/22No ROA covers it. Add a ROA for AS328015, maxLength 22.670 of 673
ROA: none102.68.172.0/22No ROA covers it. Add a ROA for AS328015, maxLength 22.669 of 673

Route objects not announced

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

102.68.175.0/24AFRINICNo ROA
2c0f:f200::/32AFRINIC, RIPE-NONAUTHNo 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.