Skip to main content

AS15874

INTERKAM

INTERKAM sp. z o.o.

Registry

Authoritative registration data

AS number
15874
Name
INTERKAM
Organisation
INTERKAM sp. z o.o.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

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

Prefixes announced by AS15874
37.130.0.0/18 IPv4 /18 not checked
37.130.49.0/24 IPv4 /24 not checked
91.231.24.0/24 IPv4 /24 not checked
91.231.25.0/24 IPv4 /24 not checked
91.231.26.0/24 IPv4 /24 not checked
91.231.27.0/24 IPv4 /24 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 AS15874
Address families
EPIX.Warszawa 10,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 AS15874 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS15874 in AS paths

Observed upstreams
Families
AS29535 MIX2_OpenPeering 292 1,901
v4
AS6204 ZET-NET 1 5
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS15874 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 16
v4
AS49544 i3Dnet 2 12
v4
AS28917 Fiord-AS 1 5
v4
AS36236 NETACTUATE 1 5
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.