Skip to main content

AS204444

LANTECH-AS

======================[UPSTREAM]===========================

Registry

Authoritative registration data

AS number
204444
Name
LANTECH-AS
Organisation
======================[UPSTREAM]===========================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

1

Total announced

8

Announced prefixes

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

Prefixes announced by AS204444
80.94.28.0/23 IPv4 /23 not checked
194.76.41.0/24 IPv4 /24 not checked
194.76.44.0/24 IPv4 /24 not checked
194.76.53.0/24 IPv4 /24 not checked
212.14.60.0/24 IPv4 /24 not checked
213.155.167.0/24 IPv4 /24 not checked
80.94.27.0/24 IPv4 /24 not checked
2001:67c:2b68::/48 IPv6 /48 not checked

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 AS204444
Address families
EPIX.Katowice 10,000 Mbps IPv4 · IPv6
EPIX.Warszawa 1,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 AS204444 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS204444 in AS paths

Observed upstreams
Families
AS13119 ACI-COM-AS 389 1,536
v4 v6
AS50607 EPIX-KTW-GlobalMix 103 943
v4
AS201054 EPIX-PolMix 26 159
v4 v6
AS1299 TWELVE99 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS204444 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 50
v4 v6
AS49544 i3Dnet 1 14
v4
AS36236 NETACTUATE 1 8
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.