Skip to main content

AS47438

PSKOVLINE-AS

Pskovline Ltd.

Registry

Authoritative registration data

AS number
47438
Name
PSKOVLINE-AS
Organisation
Pskovline Ltd.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

1

Total announced

11

Announced prefixes

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

Prefixes announced by AS47438
176.113.0.0/19 IPv4 /19 not checked
31.132.96.0/19 IPv4 /19 not checked
109.207.176.0/20 IPv4 /20 not checked
89.23.16.0/20 IPv4 /20 not checked
176.113.32.0/21 IPv4 /21 not checked
89.23.0.0/21 IPv4 /21 not checked
89.23.8.0/21 IPv4 /21 not checked
188.130.240.0/22 IPv4 /22 not checked
91.204.136.0/22 IPv4 /22 not checked
91.237.148.0/24 IPv4 /24 not checked
2001:67c:233c::/48 IPv6 /48 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 AS47438
Address families
GNM-IX 100,000 Mbps IPv4 · IPv6
Global-IX 100,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 30,000 Mbps IPv4
PITER-IX Helsinki 30,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 30,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 30,000 Mbps IPv4 · IPv6
PITER-IX Tallinn: TLL_PEERING VLAN 30,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 AS47438 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

20 networks seen before AS47438 in AS paths

Observed upstreams
Families
AS31500 365 2,362
v4
AS28917 247 518
v4 v6
AS50509 84 415
v4 v6
AS6939 HURRICANE 35 181
v4
AS8218 NEO-ASN 10 126
v4 v6
AS25091 IP-Max 7 73
v4 v6
AS47692 5 49
v4 v6
AS49434 6 26
v4 v6
AS41327 FIBERTELECOM-AS 4 23
v4 v6
AS39351 ESAB-AS 3 22
v4 v6
AS9198 3 13
v4 v6
AS60171 3 13
v4 v6
AS6204 3 12
v4
AS15958 3 12
v4
AS6663 2 12
v4 v6
AS56655 GIGAHOST 2 12
v4 v6
AS42295 TBISS-AS 2 11
v4
AS62000 2 11
v4
AS137409 GSLNETWORKS-AS-AP 2 10
v4
AS33891 CORE-BACKBONE 3 3
v4

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS47438 in AS paths

Observed downstreams
Families
AS210416 181 220
v4
AS56613 80 96
v4

No rows match “”.

Showing of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 100
v4 v6
AS3170 3 13
v4 v6
AS205112 PHILUNET 3 13
v4 v6
AS208972 3 13
v4 v6
AS13004 3 12
v4
AS29049 3 12
v4
AS35598 3 12
v4
AS41722 3 12
v4 v6
AS44901 3 12
v4
AS49673 TRUENETWORK 3 12
v4
AS200612 GulfBridgeInternational 3 12
v4
AS209823 2 12
v4 v6
AS37721 ORG-VTS1-AFRINIC 2 11
v4
AS51185 MAINSTREAMING-AS 2 11
v4
AS50629 LWLCOM 1 10
v4
AS199524 GCORE 1 10
v4
AS28910 2 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.