Skip to main content

AS208732

AIZON-AS

ABDUL PATRYK trading as "ANETCONNECT ABDUL PATRYK SPOLKA KOMANDYTOWA"

Registry

Authoritative registration data

AS number
208732
Name
AIZON-AS
Organisation
ABDUL PATRYK trading as "ANETCONNECT ABDUL PATRYK SPOLKA KOMANDYTOWA"
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS208732
45.87.32.0/22 IPv4 /22 not checked
2a0e:ef80::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS208732 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS208732 in AS paths

Observed upstreams
Families
AS62081 323 695
v4
AS8308 416 572
v4 v6
AS20804 ASN-TELENERGO 179 295
v4 v6
AS50607 51 95
v4
AS201054 EPIX-PolMix 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS208732 in AS paths

Observed downstreams
Families
AS210301 SQS-AS 137 543
v4
AS198880 284 372
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 6
v4 v6
AS24482 SGGS-AS-AP 2 3
v4 v6
AS36236 NETACTUATE 2 3
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.