Skip to main content

AS57255

PLATKOM-AS

Piotr Platek trading as Platkom Tele-Informatyka

Registry

Authoritative registration data

AS number
57255
Name
PLATKOM-AS
Organisation
Piotr Platek trading as Platkom Tele-Informatyka
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS57255
213.177.184.0/24 IPv4 /24 not checked
45.88.4.0/24 IPv4 /24 not checked
91.230.156.0/24 IPv4 /24 not checked
2a0e:f300::/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 AS57255
Address families
EPIX.Warszawa 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 AS57255 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS57255 in AS paths

Observed upstreams
Families
AS62081 EPIX-WAW-GlobalMix 247 655
v4 v6
AS201054 EPIX-PolMix 48 89
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS57255 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 10
v4 v6
AS49544 i3Dnet 1 4
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.