Skip to main content

AS39839

DK-PUNKTUM

The .DK TLD Registry

Registry

Authoritative registration data

AS number
39839
Name
DK-PUNKTUM
Organisation
The .DK TLD Registry
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS39839
95.130.208.0/21 IPv4 /21 not checked
185.153.252.0/22 IPv4 /22 not checked
193.163.102.0/24 IPv4 /24 not checked
2a01:630::/32 IPv6 /32 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 AS39839
Address families
AMS-IX 100 Mbps IPv4 · IPv6
DIX: DIX LAN 1,000 Mbps IPv4 · IPv6
Netnod Copenhagen BLUE -- MTU9K: 9K-BLUE 100 Mbps IPv4 · IPv6
Netnod Copenhagen GREEN -- MTU9K: 9K-GREEN 100 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 AS39839 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

28 networks seen before AS39839 in AS paths

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS39839 in AS paths

Observed downstreams
Families
AS197938 DK-TLD-ANY-1 255 343
v4 v6
AS202218 INTERNETSTIFTELSEN_ANYCAST 142 195
v4 v6
AS52234 52234 148 182
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

23 adjacencies that may be an artefact of collector peering

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.