Skip to main content

AS212754

SI-PL-AS

Jacek Kowalski trading as SI.pl

Registry

Authoritative registration data

AS number
212754
Name
SI-PL-AS
Organisation
Jacek Kowalski trading as SI.pl
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

2

Total announced

4

Announced prefixes

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

Prefixes announced by AS212754
193.19.248.0/23 IPv4 /23 not checked
193.19.250.0/24 IPv4 /24 not checked
2a0a:2300::/32 IPv6 /32 not checked
2a0a:2301::/32 IPv6 /32 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 AS212754
Address families
EPIX.Katowice 1,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 AS212754 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS212754 in AS paths

Observed upstreams
Families
AS50607 537 786
v4 v6
AS207668 374 703
v4 v6
AS201054 EPIX-PolMix 118 168
v4 v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS212754 in AS paths

Observed downstreams
Families
AS198067 188 251
v4

No rows match “”.

Showing of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 16
v4 v6
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.