bgpreport

Network · data from 2026-11-12

AS327849 RocketNet

Registry name: DIRECTEL COMMUNICATIONS (PTY) LTD - DIRECTEL COMMUNICATIONS (PTY) LTD, ZA · PeeringDB

21IPv4 routes 100.0% RPKI valid · 90.5% with a route object
8IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS327849, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS327849, 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.212.124.0/24 Valid Nonecovered by 102.212.124.0/23 671 100% 67
102.212.125.0/24 Valid Nonecovered by 102.212.124.0/23 671 100% 67
102.207.200.0/24 Valid Other IRR onlyRADB 103 15% 38
102.222.248.0/22 Valid RIR databaseAFRINIC, RADB 673 100% 66
169.255.0.0/22 Valid RIR databaseAFRINIC, RADB 673 100% 66
169.255.3.0/24 Valid RIR databaseAFRINIC 673 100% 66
45.222.0.0/19 Valid RIR databaseAFRINIC, RADB 672 100% 66
45.222.24.0/21 Valid RIR databaseAFRINIC, RADB 672 100% 66
102.207.200.0/22 Valid RIR databaseAFRINIC, RADB 671 100% 67
102.207.202.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
102.207.203.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
102.212.124.0/22 Valid RIR databaseAFRINIC, RADB 671 100% 67
2c0f:f2a0::/32 Valid RIR databaseAFRINIC, RADB 636 100% 67
2c0f:f2a0:2::/48 Valid RIR databaseAFRINIC, RADB 636 100% 67
2c0f:f2a0:2000::/36 Valid RIR databaseAFRINIC, RADB 636 100% 67
2c0f:f2a0:5000::/40 Valid RIR databaseAFRINIC, RADB 636 100% 67
2c0f:f2a0:5000::/38 Valid RIR databaseAFRINIC, RADB 635 100% 67
102.207.200.0/23 Valid RIR databaseAFRINIC, RADB 103 15% 38
2c0f:f2a0::/48 Valid RIR databaseAFRINIC, RADB 90 14% 32
2c0f:f2a0:1000::/36 Valid RIR databaseAFRINIC, RADB 90 14% 32
2c0f:f2a0:3000::/36 Valid RIR databaseAFRINIC, RADB 90 14% 32
45.222.0.0/20 Valid RIR databaseAFRINIC, RADB 71 11% 24
45.222.16.0/20 Valid RIR databaseAFRINIC, RADB 71 11% 24
102.222.248.0/23 Valid RIR databaseAFRINIC, RADB 71 11% 24
102.222.250.0/23 Valid RIR databaseAFRINIC, RADB 71 11% 24
169.255.0.0/23 Valid RIR databaseAFRINIC, RADB 71 11% 24
169.255.2.0/23 Valid RIR databaseAFRINIC, RADB 71 11% 24
45.222.24.0/22 Valid RIR databaseAFRINIC, RADB 58 9%low visibility 22
45.222.28.0/22 Valid RIR databaseAFRINIC, RADB 58 9%low visibility 22

AS-SET

PeeringDB's irr_as_set for AS327849: AS-ROCKETNET. 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 (AS327849 isn't in the set, or no route object for AS327849 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 objectsAS327849 in itNot covered
AS-ROCKETNET AFRINIC 3168 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 9 are in fix.csv.

  • Route object: none2
  • Route object: RIR1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none102.212.124.0/24No route object for it. A route object for 102.212.124.0/23 with origin AS327849 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327849 in the RIR database for the space.671 of 673
Route object: none102.212.125.0/24No route object for it. A route object for 102.212.124.0/23 with origin AS327849 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327849 in the RIR database for the space.671 of 673
Route object: RIR102.207.200.0/24Route object only in RADB. Add it in the RIR database for the space.103 of 673

Route objects not announced

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

102.207.202.0/23AFRINICValid
102.212.124.0/23AFRINIC, RADBValid
102.212.126.0/23AFRINIC, RADBValid
2c0f:f2a0:10::/48AFRINICValid
2c0f:f2a0:5100::/40AFRINICValid
2c0f:f2a0:5200::/40AFRINICValid

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.