Skip to main content

AS39889

DCS-Networks-AS

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

Registry

Authoritative registration data

AS number
39889
Name
DCS-Networks-AS
Organisation
-----------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS39889
193.234.32.0/21 IPv4 /21 not checked
195.189.182.0/23 IPv4 /23 RPKI not found
193.104.214.0/24 IPv4 /24 RPKI valid
193.234.15.0/24 IPv4 /24 RPKI not found
2a00:1c20::/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 AS39889
Address families
AMS-IX 50,000 Mbps IPv4 · IPv6
FIXO 10,000 Mbps IPv4 · IPv6
KeFF-IX 100,000 Mbps IPv4 · IPv6
Netnod Stockholm BLUE -- MTU1500: STH-B -- MTU1500 50,000 Mbps IPv4 · IPv6
Netnod Stockholm BLUE -- MTU4470: STH-B -- MTU4470 50,000 Mbps IPv4 · IPv6
Netnod Stockholm GREEN -- MTU1500: STH-A -- MTU1500 50,000 Mbps IPv4 · IPv6
Netnod Stockholm GREEN -- MTU4470: STH-A -- MTU4470 50,000 Mbps IPv4 · IPv6
SONIX Stockholm 100,000 Mbps IPv4 · IPv6
STHIX - Stockholm: STH Peering 100,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 AS39889 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

53 networks seen before AS39889 in AS paths

Observed upstreams
Families
AS3399 OBE-NET 1,713 5,124
v4 v6
AS50989 DCS-Networks-AS 320 810
v4 v6
AS6939 HURRICANE 555 774
v4 v6
AS25091 IP-Max 42 265
v4 v6
AS14840 ASN14840 30 190
v4
AS5405 INTERDOTLINK 70 177
v4 v6
AS47147 AS-ANX 31 171
v4
AS12779 ITGATE 31 168
v4 v6
AS48362 TKSWF-AS 30 156
v4 v6
AS35280 F5 60 149
v4 v6
AS34019 HIVANE 48 136
v4 v6
AS34177 CELESTE-AS 32 84
v4 v6
AS37497 ORG-NPL3-AFRINIC 32 82
v4
AS8298 IPNG 30 80
v4 v6
AS6057 6057 30 78
v4
AS22356 ASN22356 30 76
v4
AS6797 GLOBALCONNECT-NET 15 76
v4 v6
AS24961 MYLOC-AS 26 73
v4 v6
AS6777 AMS-IX-RS 36 69
v4 v6
AS37468 ORG-AC4-AFRINIC 26 67
v4 v6
AS20764 RASCOM-AS 24 64
v4 v6
AS15576 NTS 34 61
v4 v6
AS3303 SWISSCOM 37 55
v4 v6
AS29632 NASSIST-AS 28 54
v6
AS9044 SOLNET 10 54
v4
AS20485 TRANSTELECOM 21 51
v4
AS29075 IELO 21 47
v4 v6
AS7195 7195 20 43
v4 v6
AS37100 ORG-SL75-AFRINIC 19 41
v4
AS1267 ASN-WINDTRE 16 40
v4
AS15802 DU-AS1 16 40
v4
AS30844 LIQUID-AS 15 39
v4
AS4455 BSO 15 38
v4 v6
AS55850 MERCURYNZ-AS-AP 15 38
v4
AS20766 GITOYEN-MAIN-AS 15 36
v4
AS50304 BLIX 14 34
v4
AS42303 FiberDirekt 29 32
v4
AS41327 FIBERTELECOM-AS 22 30
v4
AS9002 RETN-AS 16 29
v6
AS50673 Serverius-as 11 19
v4
AS6204 ZET-NET 11 15
v4
AS15958 CETIN_doo_AS 10 14
v4
AS20562 OPEN-PEERING-AS 5 13
v4
AS2603 NORDUNET 8 10
v4 v6
AS50629 LWLCOM 6 8
v6
AS1764 NEXTLAYER-AS 6 7
v4
AS6663 TTI-NET 6 7
v4
AS13194 BITE 6 7
v4
AS17557 PKTELECOM-AS-PK 6 7
v4
AS20473 AS-VULTR 3 3
v6
AS4230 ASN4230 1 1
v6
AS56655 GIGAHOST 1 1
v4
AS262761 ASN262761 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

7 networks seen after AS39889 in AS paths

Observed downstreams
Families
AS30893 NOACKHOSTING-AS 1,754 6,314
v4 v6
AS30880 SPACEDUMP-AS 614 1,864
v4 v6
AS33837 PRQ-AS 389 566
v4 v6
AS205966 CLEARMINDS 244 407
v4 v6
AS50683 SITABINFRA-GLOBAL-AS 215 291
v6
AS48116 highsec-as 225 273
v4
AS208686 Nordic-Servers 225 273
v4

No rows match “”.

Showing – of

Uncertain adjacencies

42 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.