Skip to main content

AS61109

STWIMST

Stadtgemeinde/Stadtwerke Imst

Registry

Authoritative registration data

AS number
61109
Name
STWIMST
Organisation
Stadtgemeinde/Stadtwerke Imst
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

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

Prefixes announced by AS61109
46.243.104.0/21 IPv4 /21 not checked
185.191.132.0/22 IPv4 /22 not checked
185.7.124.0/22 IPv4 /22 not checked
185.7.16.0/22 IPv4 /22 not checked
185.89.48.0/22 IPv4 /22 not checked
2a02:41c0::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS61109 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS61109 in AS paths

Observed upstreams
Families
AS34347 CITYNET-AT-AS 435 765
v4 v6
AS25447 JM-DATA 173 568
v4
AS31543 MYNET-AS 206 285
v4 v6
AS8412 TMA 61 196
v4
AS48362 TKSWF-AS 2 22
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS61109 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS31510 IKB-AS 1 5
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.