Skip to main content

AS29097

HOSTPOINT-AS

TRANSIT

Registry

Authoritative registration data

AS number
29097
Name
HOSTPOINT-AS
Organisation
TRANSIT
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS29097
217.26.48.0/20 IPv4 /20 not checked
185.206.0.0/22 IPv4 /22 not checked
185.208.28.0/22 IPv4 /22 not checked
2a00:d70::/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 AS29097
Address families
SwissIX: 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 AS29097 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS29097 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 187 843
v4 v6
AS13030 INIT7 88 414
v4 v6
AS174 COGENT-174 38 127
v4 v6
AS6730 SUNRISE 8 29
v4 v6
AS8758 IWAY 3 7
v4 v6
AS9044 SOLNET 1 6
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS29097 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS62167 Tismi 1 8
v4 v6
AS8298 IPNG 1 4
v4 v6
AS15623 CYBERLINK 1 4
v4 v6
AS21232 GGAMAUR 1 4
v4 v6
AS34177 CELESTE-AS 1 4
v4 v6
AS51873 AS-ARCADE 1 4
v4 v6
AS59891 FSIT 1 4
v4 v6
AS29691 NINE 1 3
v4

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.