Skip to main content

AS16138

INTERIAPL

Interia.pl Sp z.o.o.

Registry

Authoritative registration data

AS number
16138
Name
INTERIAPL
Organisation
Interia.pl Sp z.o.o.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

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

Prefixes announced by AS16138
185.69.192.0/22 IPv4 /22 not checked
217.74.64.0/22 IPv4 /22 not checked
217.74.68.0/22 IPv4 /22 not checked
217.74.72.0/22 IPv4 /22 not checked
217.74.76.0/22 IPv4 /22 not checked
2a00:1308::/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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS16138 in AS paths

Observed upstreams
Families
AS29535 379 1,155
v4 v6
AS8323 CYFRONET-AS2 154 1,025
v4
AS12741 19 105
v4
AS5617 15 28
v4 v6
AS201054 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS16138 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
AS49544 i3Dnet 1 2
v6
AS24482 SGGS-AS-AP 1 1
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.