Skip to main content

AS59415

HAKER

Mateusz Dymitruk trading as PPHU Haker

Registry

Authoritative registration data

AS number
59415
Name
HAKER
Organisation
Mateusz Dymitruk trading as PPHU Haker
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS59415
195.140.128.0/22 IPv4 /22 not checked
91.216.194.0/24 IPv4 /24 not checked
91.234.49.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 AS59415
Address families
EPIX.Katowice 10,000 Mbps IPv4
EPIX.Warszawa 10,000 Mbps IPv4
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 AS59415 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS59415 in AS paths

Observed upstreams
Families
AS29535 MIX2_OpenPeering 207 805
v4
AS20804 ASN-TELENERGO 85 326
v4
AS6204 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS59415 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
AS49544 i3Dnet 1 6
v4
AS24482 SGGS-AS-AP 1 3
v4
AS28917 Fiord-AS 1 3
v4
AS36236 NETACTUATE 1 3
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.