Skip to main content

AS207335

i-Community

i-Community AG

Registry

Authoritative registration data

AS number
207335
Name
i-Community
Organisation
i-Community AG
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 AS207335
185.243.64.0/22 IPv4 /22 not checked
185.106.133.0/24 IPv4 /24 not checked
2a10:1380::/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 AS207335
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 AS207335 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS207335 in AS paths

Observed upstreams
Families
AS12387 TON 177 362
v4 v6
AS13030 INIT7 101 303
v4 v6
AS6939 HURRICANE 17 34
v4
AS6730 SUNRISE 10 20
v4
AS34019 HIVANE 4 15
v4 v6
AS24961 MYLOC-AS 2 5
v4 v6
AS5405 INTERDOTLINK 2 4
v4 v6
AS1764 NEXTLAYER-AS 1 3
v4 v6
AS39351 ESAB-AS 1 2
v4
AS1836 GREEN 1 1
v6
AS34927 iFog-GmbH 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS207335 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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