Skip to main content

AS201695

ALARMADI-AS

ALARMADI Adrian Dobrogowski

Registry

Authoritative registration data

AS number
201695
Name
ALARMADI-AS
Organisation
ALARMADI Adrian Dobrogowski
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS201695
82.160.134.0/24 IPv4 /24 not checked
94.40.87.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 AS201695
Address families
EPIX.Katowice 10,000 Mbps IPv4
EPIX.Warszawa 10,000 Mbps IPv4 · IPv6
TPIX PL 10,000 Mbps 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 AS201695 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS201695 in AS paths

Observed upstreams
Families
AS62081 217 580
v4
AS50607 49 120
v4
AS201054 EPIX-PolMix 11 26
v4
AS6204 6 16
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS201695 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 1 14
v4
AS49544 i3Dnet 1 4
v4
AS28917 1 2
v4
AS36236 NETACTUATE 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.