bgpreport

Network · data from 2026-11-12

AS328870 SynBurst (Pty) Ltd

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

6IPv4 routes 83.3% RPKI valid · 100.0% with a route object
5IPv6 routes 100.0% RPKI valid · 40.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 3 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS328870, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328870, 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.
44.30.186.0/24 No ROA Other IRR onlyRADB 673 100% 66
2c0f:4900:100::/40 Valid Nonecovered by 2c0f:4900::/32 636 100% 67
2c0f:4900:100::/41 Valid Nonecovered by 2c0f:4900::/32 32 5%low visibility 19
2c0f:4900:180::/41 Valid Nonecovered by 2c0f:4900::/32 32 5%low visibility 19
102.219.108.0/22 Valid RIR databaseAFRINIC 673 100% 66
102.219.110.0/23 Valid RIR databaseAFRINIC 673 100% 66
2c0f:4900::/32 Valid RIR databaseAFRINIC 636 100% 67
102.219.108.0/23 Valid RIR databaseAFRINIC 71 11% 24
102.219.110.0/24 Valid RIR databaseAFRINIC 54 8%low visibility 22
102.219.111.0/24 Valid RIR databaseAFRINIC 54 8%low visibility 22
2c0f:4900::/48 Valid RIR databaseAFRINIC 45 7%low visibility 19

AS-SET

PeeringDB's irr_as_set for AS328870: AS-SYNBURST. 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 (AS328870 isn't in the set, or no route object for AS328870 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 objectsAS328870 in itNot covered
AS-SYNBURST AFRINIC 3145 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 5 are in fix.csv.

  • ROA: none1
  • Route object: none3
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none44.30.186.0/24No ROA covers it. Add a ROA for AS328870, maxLength 24.673 of 673
Route object: RIR44.30.186.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none2c0f:4900:100::/40No route object for it. A route object for 2c0f:4900::/32 with origin AS328870 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328870 in the RIR database for the space.636 of 636
Route object: none2c0f:4900:100::/41No route object for it. A route object for 2c0f:4900::/32 with origin AS328870 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328870 in the RIR database for the space.32 of 636
Route object: none2c0f:4900:180::/41No route object for it. A route object for 2c0f:4900::/32 with origin AS328870 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328870 in the RIR database for the space.32 of 636

Route objects not announced

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