Skip to main content

AS60246

PG-19

*****************************************************

Registry

Authoritative registration data

AS number
60246
Name
PG-19
Organisation
*****************************************************
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

29

IPv6 prefixes

10

Total announced

39

Announced prefixes

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

Prefixes announced by AS60246
95.174.96.0/20 IPv4 /20 not checked
95.174.116.0/22 IPv4 /22 not checked
95.174.124.0/22 IPv4 /22 not checked
151.0.48.0/23 IPv4 /23 not checked
178.248.2.0/23 IPv4 /23 not checked
178.248.4.0/23 IPv4 /23 not checked
178.248.6.0/23 IPv4 /23 not checked
185.230.240.0/23 IPv4 /23 not checked
80.72.24.0/23 IPv4 /23 not checked
92.118.72.0/23 IPv4 /23 not checked
95.174.114.0/23 IPv4 /23 not checked
151.0.50.0/24 IPv4 /24 not checked
151.0.51.0/24 IPv4 /24 not checked
178.212.139.0/24 IPv4 /24 not checked
178.248.0.0/24 IPv4 /24 not checked
178.248.1.0/24 IPv4 /24 not checked
185.230.241.0/24 IPv4 /24 not checked
185.230.242.0/24 IPv4 /24 not checked
185.9.184.0/24 IPv4 /24 not checked
185.9.186.0/24 IPv4 /24 not checked
185.9.187.0/24 IPv4 /24 not checked
80.72.20.0/24 IPv4 /24 not checked
80.72.21.0/24 IPv4 /24 not checked
85.198.120.0/24 IPv4 /24 not checked
95.174.112.0/24 IPv4 /24 not checked
95.174.113.0/24 IPv4 /24 not checked
95.174.120.0/24 IPv4 /24 not checked
95.174.121.0/24 IPv4 /24 not checked
95.174.123.0/24 IPv4 /24 not checked
2a00:8740:10::/44 IPv6 /44 not checked
2a00:8740:20::/44 IPv6 /44 not checked
2a00:8740:30::/44 IPv6 /44 not checked
2a00:8740::/46 IPv6 /46 RPKI valid
2a00:8740:110::/47 IPv6 /47 RPKI valid
2a00:8740:100::/48 IPv6 /48 RPKI valid
2a00:8740:112::/48 IPv6 /48 RPKI valid
2a00:8740:113::/48 IPv6 /48 not checked
2a00:8740:80::/48 IPv6 /48 not checked
2a00:8740:ff00::/48 IPv6 /48 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 AS60246
Address families
MSK-IX Moscow: MSK-IX peering network 20,000 Mbps IPv4 · IPv6
MSK-IX Rostov-on-Don 10,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 100,000 Mbps IPv4
PITER-IX Helsinki 100,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 100,000 Mbps IPv4 · IPv6
PITER-IX Riga: RIX_PEERING_VLAN 100,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 100,000 Mbps IPv4 · IPv6
PITER-IX Tallinn: TLL_PEERING VLAN 100,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 AS60246 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS60246 in AS paths

Observed upstreams
Families
AS35598 INETCOM 502 6,973
v4 v6
AS57304 RETNRU-AS 210 4,105
v4 v6
AS62255 BEMYLINK 95 611
v4 v6
AS25091 IP-Max 9 202
v4 v6
AS41327 FIBERTELECOM-AS 3 41
v4 v6
AS9198 KAZTELECOM-AS 2 40
v4 v6
AS137409 GSLNETWORKS-AS-AP 2 30
v4
AS6939 HURRICANE 22 23
v4
AS9002 RETN-AS 1 15
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS60246 in AS paths

Observed downstreams
Families
AS204435 NCTRADE 258 317
v4

No rows match “”.

Showing – of

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 202
v4 v6
AS28917 Fiord-AS 2 50
v4 v6
AS36236 NETACTUATE 2 40
v4 v6
AS41722 MIRAN-AS 2 40
v4 v6
AS37721 ORG-VTS1-AFRINIC 2 30
v4
AS49434 FBWNETWORKS 2 30
v4
AS49544 i3Dnet 2 30
v4
AS49673 TRUENETWORK 2 30
v4
AS205112 PHILUNET 2 30
v4
AS28910 INTAL-ASN 1 10
v6
AS34927 iFog-GmbH 1 1
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.