Skip to main content

AS35223

HOI-AS

*************************************************

Registry

Authoritative registration data

AS number
35223
Name
HOI-AS
Organisation
*************************************************
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS35223
82.117.0.0/19 IPv4 /19 not checked
193.168.168.0/22 IPv4 /22 not checked
2a03:5480::/29 IPv6 /29 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 AS35223
Address families
Rheintal IX: Peering-LAN 10,000 Mbps IPv4 · IPv6
SwissIX: 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 AS35223 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS35223 in AS paths

Observed upstreams
Families
AS59890 Kabel-TV-Lampert 331 650
v4 v6
AS33891 CORE-BACKBONE 101 279
v4 v6
AS4455 BSO 129 204
v4 v6
AS12387 TON 70 135
v4 v6
AS34019 HIVANE 4 11
v4 v6
AS43531 IXREACH 6 9
v4 v6
AS1764 NEXTLAYER-AS 2 4
v4 v6
AS31216 BSOCOM 2 3
v4 v6
AS39351 ESAB-AS 2 3
v4 v6
AS1836 GREEN 2 2
v4
AS34927 iFog-GmbH 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS35223 in AS paths

Observed downstreams
Families
AS21113 HILTI-AS 163 207
v4
AS49652 DOMAR-AS 78 102
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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