Skip to main content

AS328512

ORG-BTL6-AFRINIC

Backspace Technologies (Pty) Ltd

Registry

Authoritative registration data

AS number
328512
Name
ORG-BTL6-AFRINIC
Organisation
Backspace Technologies (Pty) Ltd
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

2

Total announced

11

Announced prefixes

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

Prefixes announced by AS328512
102.64.16.0/20 IPv4 /20 not checked
102.64.16.0/21 IPv4 /21 not checked
102.64.24.0/21 IPv4 /21 not checked
102.202.172.0/22 IPv4 /22 not checked
102.205.116.0/22 IPv4 /22 not checked
102.64.20.0/22 IPv4 /22 not checked
102.64.28.0/22 IPv4 /22 not checked
102.64.18.0/24 IPv4 /24 not checked
102.64.28.0/24 IPv4 /24 not checked
2c0f:edf8::/32 IPv6 /32 RPKI valid
2c0f:edf8:c000::/35 IPv6 /35 not checked

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 AS328512
Address families
CINX: CINX Peering 1,000 Mbps IPv4 · IPv6
DINX: DINX Peering 10,000 Mbps IPv4 · IPv6
JINX Voice: JINX Voice 10,000 Mbps IPv4
JINX: JINX Peering 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Cape Town 20,000 Mbps IPv4 · IPv6
NAPAfrica IX Durban 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 AS328512 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS328512 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS328512 in AS paths

Observed downstreams
Families
AS329248 ORG-SI7-AFRINIC 533 1,147
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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