Skip to main content

AS204394

CORTEX

Cortex, a.s.

Registry

Authoritative registration data

AS number
204394
Name
CORTEX
Organisation
Cortex, a.s.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS204394
185.250.100.0/22 IPv4 /22 not checked
2a0e:e580::/29 IPv6 /29 not checked

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

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS204394 in AS paths

Observed upstreams
Families
AS6855 SK-TELEKOM 184 314
v4 v6
AS6939 HURRICANE 95 139
v4 v6
AS8218 NEO-ASN 6 22
v4 v6
AS1764 NEXTLAYER-AS 3 10
v4 v6
AS14840 ASN14840 2 10
v4 v6
AS22356 ASN22356 5 6
v4 v6
AS4455 BSO 2 4
v4 v6
AS6204 ZET-NET 1 1
v4
AS6663 TTI-NET 1 1
v4
AS44306 Omonia 1 1
v4
AS263444 ASN263444 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS204394 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 18
v4 v6
AS51184 FONIRA 1 4
v4 v6
AS6881 NIXCZ 1 2
v4 v6
AS29504 LBCFREE 1 2
v4 v6
AS36236 NETACTUATE 1 2
v4 v6
AS40994 Alwyzon 1 2
v4 v6
AS49544 i3Dnet 1 2
v4 v6
AS198150 SIACOM-AS 1 2
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.