Skip to main content

AS2590

DTP-AS

Data Techno Park Sp. z o. o.

Registry

Authoritative registration data

AS number
2590
Name
DTP-AS
Organisation
Data Techno Park Sp. z o. o.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS2590
185.125.124.0/22 IPv4 /22 not checked
78.133.144.0/22 IPv4 /22 not checked
85.219.244.0/22 IPv4 /22 not checked
89.174.32.0/23 IPv4 /23 not checked
85.219.247.0/24 IPv4 /24 not checked
89.174.229.0/24 IPv4 /24 not checked
89.174.33.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 AS2590
Address families
EPIX.Warszawa 20,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 AS2590 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS2590 in AS paths

Observed upstreams
Families
AS197790 266 2,418
v4
AS12912 32 305
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS2590 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 14
v4
AS24482 SGGS-AS-AP 1 7
v4
AS36236 NETACTUATE 1 7
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.