Skip to main content

AS205119

TELEKS-MK

===== U =====

Registry

Authoritative registration data

AS number
205119
Name
TELEKS-MK
Organisation
===== U =====
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

3

Total announced

8

Announced prefixes

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

Prefixes announced by AS205119
185.233.208.0/22 IPv4 /22 not checked
185.225.28.0/24 IPv4 /24 not checked
185.225.29.0/24 IPv4 /24 not checked
185.225.30.0/24 IPv4 /24 not checked
185.225.31.0/24 IPv4 /24 not checked
2a0d:4500::/29 IPv6 /29 RPKI not found
2a0d:6280::/29 IPv6 /29 not checked
2a0d:6880::/29 IPv6 /29 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 AS205119 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS205119 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS205119 in AS paths

Observed downstreams
Families
AS213683 host-al-asn 1,279 3,030
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 4 18
v4
AS13004 SOX 4 9
v4
AS44901 belcloud 4 9
v4
AS208972 gibirnet-tr 4 9
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.