Skip to main content

AS203222

jarosz-as

Adam Jarosz trading as Zaklad Elektroniczny P.A. Jarosz s.c.

Registry

Authoritative registration data

AS number
203222
Name
jarosz-as
Organisation
Adam Jarosz trading as Zaklad Elektroniczny P.A. Jarosz s.c.
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 AS203222
185.253.164.0/22 IPv4 /22 not checked
45.131.204.0/22 IPv4 /22 not checked
91.214.32.0/22 IPv4 /22 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 AS203222
Address families
EPIX.Katowice 10,000 Mbps IPv4 · IPv6
TPIX PL 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 AS203222 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS203222 in AS paths

Observed upstreams
Families
AS174 COGENT-174 183 726
v4
AS6939 HURRICANE 37 123
v4
AS5617 21 78
v4
AS201054 EPIX-PolMix 10 33
v4
AS6204 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS203222 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 33
v4
AS49544 i3Dnet 1 6
v4
AS28917 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.