Skip to main content

AS206579

HTK-AS

----- UPSTREAMS -----

Registry

Authoritative registration data

AS number
206579
Name
HTK-AS
Organisation
----- UPSTREAMS -----
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS206579
185.172.208.0/22 IPv4 /22 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 AS206579
Address families
EPIX.Warszawa 40,000 Mbps IPv4
Equinix Warsaw 10,000 Mbps IPv4
TPIX PL 40,000 Mbps IPv4
WRIX: WRIX 10,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS206579 in AS paths

Observed upstreams
Families
AS29535 389 572
v4
AS35179 154 457
v4
AS24115 ASN-EQIX-MLPE 4 4
v4
AS6204 2 2
v4
AS137409 GSLNETWORKS-AS-AP 2 2
v4
AS5617 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS206579 in AS paths

Observed downstreams
Families
AS50648 58 415
v4
AS203742 216 276
v4
AS49715 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 4
v4
AS24482 SGGS-AS-AP 2 2
v4
AS28917 2 2
v4
AS36236 NETACTUATE 2 2
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.