Skip to main content

AS328870

ORG-SL85-AFRINIC

SynBurst (Pty) Ltd

Registry

Authoritative registration data

AS number
328870
Name
ORG-SL85-AFRINIC
Organisation
SynBurst (Pty) Ltd
Country
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

3

Total announced

9

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS328870
102.219.108.0/22 IPv4 /22 not checked
102.219.108.0/23 IPv4 /23 not checked
102.219.110.0/23 IPv4 /23 not checked
102.219.110.0/24 IPv4 /24 not checked
102.219.111.0/24 IPv4 /24 not checked
44.30.186.0/24 IPv4 /24 not checked
2c0f:4900::/32 IPv6 /32 not checked
2c0f:4900:100::/40 IPv6 /40 not checked
2c0f:4900::/48 IPv6 /48 RPKI valid

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS328870
Address families
NAPAfrica IX Cape Town 20,000 Mbps IPv4 · IPv6
NAPAfrica IX Johannesburg: Peering 20,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS328870 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS328870 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS328870 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

13 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.