Skip to main content

AS328889

ORG-MCSC1-AFRINIC

MODEM COMPUTER SERVICES (PTY) LTD

Registry

Authoritative registration data

AS number
328889
Name
ORG-MCSC1-AFRINIC
Organisation
MODEM COMPUTER SERVICES (PTY) LTD
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS328889
102.201.108.0/24 IPv4 /24 not checked
102.201.109.0/24 IPv4 /24 not checked
102.219.29.0/24 IPv4 /24 not checked
2c0f:6900:100::/48 IPv6 /48 not checked
2c0f:6900::/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 AS328889
Address families
JINX: JINX Peering 10,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 AS328889 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS328889 in AS paths

Observed upstreams
Families
AS37611 ORG-AS7-AFRINIC 446 1,036
v4 v6
AS328748 ORG-ASPL1-AFRINIC 371 715
v4 v6
AS6939 HURRICANE 20 22
v4
AS37468 ORG-AC4-AFRINIC 2 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS328889 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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