Skip to main content

AS49436

Stadtwerke-Soest

Stadtwerke Soest GmbH

Registry

Authoritative registration data

AS number
49436
Name
Stadtwerke-Soest
Organisation
Stadtwerke Soest GmbH
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

4

Total announced

8

Announced prefixes

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

Prefixes announced by AS49436
185.248.188.0/22 IPv4 /22 not checked
185.250.168.0/22 IPv4 /22 not checked
195.42.158.0/23 IPv4 /23 not checked
195.43.80.0/23 IPv4 /23 not checked
2a0c:f47::/32 IPv6 /32 not checked
2a0e:1b00::/32 IPv6 /32 not checked
2a0e:1b01::/32 IPv6 /32 not checked
2a0e:1b07::/32 IPv6 /32 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 AS49436
Address families
DE-CIX Dusseldorf: DE-CIX Dusseldorf Peering LAN 100,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 100,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 AS49436 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

36 networks seen before AS49436 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS49436 in AS paths

Observed downstreams
Families
AS41451 Schlueter-Server 564 1,041
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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