Skip to main content

AS37199

ORG-FPCc1-AFRINIC

Vanilla

Registry

Authoritative registration data

AS number
37199
Name
ORG-FPCc1-AFRINIC
Organisation
Vanilla
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

1

Total announced

10

Announced prefixes

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

Prefixes announced by AS37199
45.221.128.0/18 IPv4 /18 not checked
197.155.0.0/19 IPv4 /19 not checked
45.221.128.0/19 IPv4 /19 RPKI valid
45.221.160.0/19 IPv4 /19 not checked
197.155.0.0/20 IPv4 /20 not checked
197.155.16.0/20 IPv4 /20 not checked
41.76.128.0/21 IPv4 /21 RPKI valid
41.76.128.0/22 IPv4 /22 not checked
41.76.132.0/22 IPv4 /22 RPKI valid
2c0f:fb18::/32 IPv6 /32 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 AS37199
Address families
CINX: CINX Peering 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Cape Town 30,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 AS37199 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS37199 in AS paths

Observed upstreams
Families
AS36874 ORG-CA2-AFRINIC 350 1,215
v4 v6
AS5713 ORG-TSL2-AFRINIC 5 9
v4 v6
AS3741 ORG-DD1-AFRINIC 1 6
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS37199 in AS paths

Observed downstreams
Families
AS329644 ORG-HSAL1-AFRINIC 148 172
v4

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.