Skip to main content

AS212344

AS_FORLAN

SPOLKA 4LAN BOGDANOW, KARKOS, OPARA, SZUMNY, WOJCIECHOWSKI SPOLKA JAWNA

Registry

Authoritative registration data

AS number
212344
Name
AS_FORLAN
Organisation
SPOLKA 4LAN BOGDANOW, KARKOS, OPARA, SZUMNY, WOJCIECHOWSKI SPOLKA JAWNA
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS212344
45.85.186.0/24 IPv4 /24 not checked
45.85.187.0/24 IPv4 /24 not checked
5.183.162.0/24 IPv4 /24 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 AS212344
Address families
EPIX.Katowice — 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 AS212344 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS212344 in AS paths

Observed upstreams
Families
AS29535 MIX2_OpenPeering 316 566
v4
AS50607 EPIX-KTW-GlobalMix 15 16
v4
AS201054 EPIX-PolMix 2 4
v4
AS6204 ZET-NET 2 3
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS212344 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v4
AS49544 i3Dnet 1 3
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.