Skip to main content

AS202936

satpol-as

Satpol Plus Sp. z o.o.

Registry

Authoritative registration data

AS number
202936
Name
satpol-as
Organisation
Satpol Plus Sp. z o.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS202936
185.148.64.0/22 IPv4 /22 not checked
185.241.232.0/22 IPv4 /22 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 AS202936
Address families
EPIX.Katowice 10,000 Mbps IPv4
EPIX.Warszawa 20,000 Mbps IPv4
TPIX PL 10,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 AS202936 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS202936 in AS paths

Observed upstreams
Families
AS62081 EPIX-WAW-GlobalMix 155 189
v4
AS29535 MIX2_OpenPeering 144 172
v4
AS201054 EPIX-PolMix 12 14
v4
AS50607 EPIX-KTW-GlobalMix 12 13
v4
AS33891 CORE-BACKBONE 2 4
v4
AS6204 ZET-NET 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS202936 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 4
v4
AS49544 i3Dnet 1 2
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.