bgpreport

Network · data from 2026-11-12

AS328633 MikroTikSA Networks

Registry name: MikroTikSA Networks CC - MikroTikSA Networks CC, ZA · PeeringDB

21IPv4 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
14Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS328633, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328633, 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.201.228.0/22 Valid RIR databaseAFRINIC 673 100% 67
102.217.184.0/22 Valid RIR databaseAFRINIC 673 100% 66
102.223.104.0/22 Valid RIR databaseAFRINIC 673 100% 66
2c0f:e848::/32 Valid RIR databaseAFRINIC 634 100% 67
102.217.184.0/23 Valid RIR databaseAFRINIC 71 11% 24
102.217.186.0/23 Valid RIR databaseAFRINIC 71 11% 24
102.223.104.0/23 Valid RIR databaseAFRINIC 71 11% 24
102.223.106.0/23 Valid RIR databaseAFRINIC 71 11% 24
102.201.228.0/23 Valid RIR databaseAFRINIC 67 10%low visibility 22
102.201.230.0/23 Valid RIR databaseAFRINIC 67 10%low visibility 22
102.217.184.0/24 Valid RIR databaseAFRINIC 58 9%low visibility 22
102.217.185.0/24 Valid RIR databaseAFRINIC 58 9%low visibility 22
102.217.186.0/24 Valid RIR databaseAFRINIC 58 9%low visibility 22
102.217.187.0/24 Valid RIR databaseAFRINIC 58 9%low visibility 22
102.223.104.0/24 Valid RIR databaseAFRINIC 58 9%low visibility 22
102.223.105.0/24 Valid RIR databaseAFRINIC 58 9%low visibility 22
102.223.106.0/24 Valid RIR databaseAFRINIC 58 9%low visibility 22
102.223.107.0/24 Valid RIR databaseAFRINIC 58 9%low visibility 22
102.201.228.0/24 Valid RIR databaseAFRINIC 52 8%low visibility 18
102.201.229.0/24 Valid RIR databaseAFRINIC 52 8%low visibility 18
102.201.230.0/24 Valid RIR databaseAFRINIC 52 8%low visibility 18
102.201.231.0/24 Valid RIR databaseAFRINIC 52 8%low visibility 18

AS-SET

PeeringDB's irr_as_set for AS328633: AFRINIC::AS-MIKROTIKSA-ALL. 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 (AS328633 isn't in the set, or no route object for AS328633 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 objectsAS328633 in itNot covered
AFRINIC::AS-MIKROTIKSA-ALL AFRINIC 1122 Yes 0

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