Digital Realty: colocation, private connectivity and ServiceFabric controls

Digital Realty provides the premises and connections on which financial applications can run. Its financial-services offering combines colocation, workload placement and private data exchange. A trading system still needs its own application, venue access and operational design; the infrastructure contract does not itself supply execution or brokerage services.[1]

ServiceFabric provides the virtual interconnection layer across this estate and partner networks. Its advertised reach of more than 800 connected data centers and 350 cloud on-ramps is network coverage, not a count of properties owned by Digital Realty. A multi-service port can support connections to several clouds, partners and services.[3]

The REST API uses a portal-generated key and secret to obtain an access token; the secret is displayed only once. Organisation identifiers scope resource requests. The interface can create, inspect and change network resources, so API access is an operational permission, not simply a reporting login.[10]

Digital Realty also advertises ServiceFabric MCP for AI agents to discover, provision and manage connections through policy-driven controls. That is a capability of the infrastructure control layer. The inspected product page does not publish a complete approval policy or establish which actions a particular customer’s agent may perform.[3]

The public Pricing Estimator describes a configuration-based quote: choose services and quantities, inspect each service or group total, select a currency and export a PDF. It does not publish a universal tariff in the inspected documentation. A colocation lease and its power, cross-connect, virtual-network, Internet and onsite-service requirements therefore need to be scoped as separate cost components.[11][2]

The ServiceFabric agreement normally bills monthly in arrears. Payment is due within 30 days of invoice date; fee disputes within 90 days after invoice date or charge. Taxes and regulatory fees are additional. After the initial term, services renew monthly unless one month’s non-renewal notice is given. Early convenience termination of a fixed-term port costs the lesser of remaining fees or three monthly recurring charges; a monthly port owes the current month’s balance.[12]

A Global Administrator arranges access. Customers enter through the applicable portal and accept the ServiceFabric terms on first use. The email used for a Magic Link must match the associated MarketPlace or EMEA account; an identity mismatch goes to the account team. Account access is consequently a prerequisite to configuring the network.[13]

For bare metal, server provisioning and network attachment are separate steps. Zenlayer’s documented workflow creates the server and associated networking before the Layer 2 link; existing Hivelocity servers can require network-bond changes before they attach. The integration does not remove the server provider’s prerequisites or the need to configure the workload itself.[8]

Remote Hands is available 24/7/365 for physical operational work. Published tasks include power cycling, cable patching, equipment moves, KVM access, loopback checks, rack inventory and installation support. Work can be scheduled or requested as needed. These are onsite tasks; the service description does not establish that a broker’s trading application is administered by Digital Realty.[17]

ServiceFabric support runs through the Global Command Centre and the relevant customer portal. The documentation distinguishes high-priority outage tickets from lower-priority general questions, with a separate Remote Hands route for facility work. It does not publish one numerical incident-response or restoration target covering every support request.[18]

Port availability targets are 100% for defined redundant configurations and 99.9% otherwise; redundancy needs diverse ports and active dual paths. Links, connections and virtual routers separately target 100%, with credits limited to the A-end owner. Customer equipment, third-party faults and other excused downtime are excluded. Claims are due within 30 calendar days after the charging period; credits offset service fees, not cash. Overdue charges prevent claims.[12]

The ServiceFabric counterparty is the affiliated entity identified at registration, on the order or for the relevant facility. The terms also require customers to encrypt traffic; private connectivity alone does not establish encryption.[12]

The certification catalogue can be filtered by site, region and standard, including ISO 27001, SOC reports and PCI DSS. It should be read at that scope: listing a standard in the catalogue does not demonstrate that every building or service has the same certificate. These infrastructure assurances also do not grant a customer permission to conduct regulated financial business.[19]

Digital Realty Trust, Inc. was incorporated in Maryland in March 2004 and listed on the NYSE as DLR following its October 2004 IPO. Its headquarters are in Austin, Texas. The company is the general partner of Digital Realty Trust, L.P.; the group structure should be distinguished from the entity named on a customer’s service order.[21]

The group completed its Telx acquisition on 9 October 2015 and its Interxion combination on 12 March 2020. These completed transactions help explain the legacy brands and portal references still present in connection-ordering documentation.[23][24][15]

In results published 23 July 2026, Digital Realty reported second-quarter revenue of US$1.9 billion. This is group revenue across its business, not revenue from FX brokers or a pricing measure for colocation.[22]

A 30 September 2026 announcement describes Blackfuel’s inference deployment at BCN1 in Barcelona, combining liquid-cooled Dell infrastructure, AMD GPUs and private ServiceFabric access. It illustrates how the interconnection platform can expose a partner’s compute service. The announcement does not establish that every connected facility has the same AI capacity or that an individual broker’s latency has been measured.[25]

Operator

Digital Realty Trust, Inc. group; service-order entity varies by location

Service scope

Colocation, data-center infrastructure and private interconnection for financial and enterprise workloads.

Customer types

Financial institutions; Trading and financial-technology firms; Cloud and network providers; Enterprise technology teams

Delivery

Hosted; API; Hybrid

Pricing publication

Quote only

Headquarters

Austin, Texas, United States

Platforms

PlatformDIGITAL; ServiceFabric

Integrations

Layer 2 links; Layer 3 connections; ServiceFabric API; Zenlayer; Hivelocity

Implementation

Account access, port and physical connection, then configured virtual services and customer applications.

Support

Global Command Centre and regional portals; Remote Hands supplies onsite tasks around the clock.

Permissions and regulatory scope

Infrastructure provision. Site certifications and access controls do not confer financial-service permissions on a customer.

Provider metadata checked 21 Oct 2026Source 21Source 1Source 4Source 11Source 14Source 18Source 19Source 23Source 24Source 3Source 8Source 10Source 12Source 17

Port groups can restrict over-provisioning through a configurable rate. That control is distinct from application demand: limiting how much virtual service capacity can be allocated does not measure whether a trading application meets its own latency or throughput requirements. Purchase-order labels and network inventory provide useful operational records, while workload performance still needs application-level observation.[14]