Skip to main content

AS205160

DZP

----------------------------------------------------------

Registry

Authoritative registration data

AS number
205160
Name
DZP
Organisation
----------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS205160
185.237.167.0/24 IPv4 /24 not checked
2a11:9940::/32 IPv6 /32 RPKI valid

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 AS205160
Address families
THINX Warsaw 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 AS205160 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS205160 in AS paths

Observed upstreams
Families
AS9141 AS9141 185 220
v4 v6
AS6939 HURRICANE 114 159
v4 v6
AS15694 ATMAN-ISP-AS 116 144
v4
AS24748 THINX_Poland 6 16
v4 v6
AS14840 ASN14840 2 5
v6
AS22356 ASN22356 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS205160 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS198150 SIACOM-AS 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.