Skip to main content

AS201949

SEEDTECHNOLOGIES

Seed Technologies LTD.

Registry

Authoritative registration data

AS number
201949
Name
SEEDTECHNOLOGIES
Organisation
Seed Technologies LTD.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

3

Total announced

6

Announced prefixes

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

Prefixes announced by AS201949
45.11.187.0/24 IPv4 /24 not checked
45.88.8.0/24 IPv4 /24 not checked
87.229.100.0/24 IPv4 /24 not checked
2a0c:9a40:86c0::/48 IPv6 /48 not checked
2a0c:9a40:86cf::/48 IPv6 /48 not checked
2a12:5343:6::/48 IPv6 /48 RPKI invalid

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 AS201949
Address families
ERA-IX Amsterdam 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 AS201949 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS201949 in AS paths

Observed upstreams
Families
AS24875 NOVOSERVE-AS 237 334
v4 v6
AS50917 DIEDERIK-AS 115 272
v4
AS35133 ERANIUM 128 164
v6
AS6939 HURRICANE 18 36
v4
AS50304 BLIX 2 6
v4 v6
AS50629 LWLCOM 2 3
v4 v6
AS6204 ZET-NET 1 2
v4
AS6663 TTI-NET 1 2
v4
AS12859 NL-BIT 1 2
v4
AS20764 RASCOM-AS 1 2
v4
AS56655 GIGAHOST 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS201949 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 11
v4 v6
AS3399 OBE-NET 1 3
v4 v6
AS24961 MYLOC-AS 1 3
v4 v6

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.