Skip to main content

AS37412

ORG-TPH1-AFRINIC

The Packet Hub

Registry

Authoritative registration data

AS number
37412
Name
ORG-TPH1-AFRINIC
Organisation
The Packet Hub
Country
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS37412
41.79.180.0/24 IPv4 /24 not checked
41.79.181.0/24 IPv4 /24 not checked
41.79.182.0/24 IPv4 /24 not checked
41.79.183.0/24 IPv4 /24 not checked
2c0f:fb30::/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 AS37412
Address families
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 AS37412 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS37412 in AS paths

Observed upstreams
Families
AS327693 ORG-EPL3-AFRINIC 244 1,232
v4
AS6939 HURRICANE 29 132
v4
AS37468 ORG-AC4-AFRINIC 2 6
v4 v6
AS37195 ORG-NA23-AFRINIC 1 1
v6
AS39120 CONVERGENZE-AS 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS37412 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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