Skip to main content

AS200081

SIM-Networks

Netversor GmbH

Registry

Authoritative registration data

AS number
200081
Name
SIM-Networks
Organisation
Netversor GmbH
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

26

IPv6 prefixes

6

Total announced

32

Announced prefixes

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

Prefixes announced by AS200081
188.244.104.0/22 IPv4 /22 RPKI not found
156.67.52.0/24 IPv4 /24 RPKI not found
156.67.53.0/24 IPv4 /24 not checked
156.67.54.0/24 IPv4 /24 RPKI not found
156.67.55.0/24 IPv4 /24 RPKI not found
185.222.64.0/24 IPv4 /24 RPKI not found
185.222.65.0/24 IPv4 /24 not checked
185.222.66.0/24 IPv4 /24 not checked
185.222.67.0/24 IPv4 /24 RPKI not found
185.31.208.0/24 IPv4 /24 RPKI not found
185.31.209.0/24 IPv4 /24 not checked
185.31.210.0/24 IPv4 /24 not checked
185.31.211.0/24 IPv4 /24 RPKI not found
185.59.100.0/24 IPv4 /24 RPKI not found
185.59.101.0/24 IPv4 /24 not checked
185.59.102.0/24 IPv4 /24 not checked
185.59.103.0/24 IPv4 /24 not checked
185.75.134.0/24 IPv4 /24 not checked
188.244.106.0/24 IPv4 /24 RPKI not found
188.244.107.0/24 IPv4 /24 RPKI not found
217.11.168.0/24 IPv4 /24 RPKI not found
217.11.169.0/24 IPv4 /24 RPKI not found
45.140.124.0/24 IPv4 /24 RPKI not found
45.140.125.0/24 IPv4 /24 RPKI not found
45.140.126.0/24 IPv4 /24 not checked
45.140.127.0/24 IPv4 /24 not checked
2a02:6aa0::/32 IPv6 /32 RPKI not found
2a04:5340:1::/48 IPv6 /48 RPKI not found
2a04:5340:2::/48 IPv6 /48 RPKI not found
2a04:5340:4::/48 IPv6 /48 RPKI not found
2a04:5340:5::/48 IPv6 /48 RPKI not found
2a04:5340::/48 IPv6 /48 RPKI not found

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

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS200081 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 162 5,005
v4 v6
AS3356 LEVEL3 131 3,712
v4 v6
AS6939 HURRICANE 77 959
v4 v6
AS24482 SGGS-AS-AP 2 344
v4 v6
AS14840 ASN14840 2 130
v4
AS3223 VOXILITY 77 110
v4
AS6663 TTI-NET 1 26
v4
AS29632 NASSIST-AS 3 18
v6
AS48648 KYIVLINK 1 6
v6
AS22356 ASN22356 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS200081 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 64
v4 v6
AS212483 level86 1 52
v4
AS48919 UA-CITY-AS 1 32
v4 v6
AS209823 ENKI-AS 1 31
v4 v6
AS198150 SIACOM-AS 1 26
v4
AS59514 DARNYTSIA-NET 1 25
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.