Skip to main content

AS39716

VIP-LUBLIN-PL-AS

VIP-NET, Lublin, Poland

Registry

Authoritative registration data

AS number
39716
Name
VIP-LUBLIN-PL-AS
Organisation
VIP-NET, Lublin, Poland
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

13

IPv6 prefixes

1

Total announced

14

Announced prefixes

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

Prefixes announced by AS39716
89.186.24.0/22 IPv4 /22 not checked
89.186.4.0/22 IPv4 /22 not checked
89.186.8.0/22 IPv4 /22 not checked
89.186.0.0/23 IPv4 /23 not checked
89.186.12.0/23 IPv4 /23 not checked
89.186.30.0/23 IPv4 /23 not checked
195.242.124.0/24 IPv4 /24 not checked
195.242.125.0/24 IPv4 /24 not checked
89.186.15.0/24 IPv4 /24 not checked
89.186.16.0/24 IPv4 /24 not checked
89.186.17.0/24 IPv4 /24 not checked
89.186.21.0/24 IPv4 /24 not checked
89.186.22.0/24 IPv4 /24 not checked
2a0b:2940::/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

Internet Exchange memberships listed for AS39716
Address families
EPIX.Katowice 10,000 Mbps IPv4 · IPv6
TPIX PL 10,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 AS39716 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS39716 in AS paths

Observed upstreams
Families
AS29535 MIX2_OpenPeering 241 3,645
v4 v6
AS42667 InterEvo-PL-AS 23 312
v4
AS6939 HURRICANE 188 258
v6
AS201054 EPIX-PolMix 10 131
v4 v6
AS33891 CORE-BACKBONE 2 52
v4
AS174 COGENT-174 1 13
v4
AS6204 ZET-NET 1 13
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS39716 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 17
v4 v6
AS28917 Fiord-AS 1 15
v4 v6
AS49544 i3Dnet 1 14
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.