Skip to main content

AS51579

CORP-PARTNER-AS

Korporatvniy partner Ltd

Registry

Authoritative registration data

AS number
51579
Name
CORP-PARTNER-AS
Organisation
Korporatvniy partner Ltd
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

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

Prefixes announced by AS51579
178.213.112.0/21 IPv4 /21 RPKI valid
178.213.112.0/22 IPv4 /22 not checked
178.213.116.0/22 IPv4 /22 RPKI valid
45.143.236.0/23 IPv4 /23 not checked
193.26.133.0/24 IPv4 /24 RPKI valid
193.26.208.0/24 IPv4 /24 RPKI valid
2a0e:e6c0:2000::/36 IPv6 /36 RPKI valid

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 AS51579
Address families
GNM-IX 100,000 Mbps IPv4 · IPv6
Global-IX 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 AS51579 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS51579 in AS paths

Observed upstreams
Families
AS8641 NAUKANET-AS 192 1,310
v4 v6
AS48347 MTW-AS 152 987
v4 v6
AS34123 NETORN-AS 267 571
v4 v6
AS47692 NESSUS 4 64
v4 v6
AS50673 Serverius-as 4 26
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS51579 in AS paths

Observed downstreams
Families
AS49863 LITE-TELECOM-AS 350 1,698
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 32
v4 v6
AS37721 ORG-VTS1-AFRINIC 2 14
v4
AS200612 GulfBridgeInternational 2 14
v4
AS208972 2 14
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.