Disaster recovery out of the storm track
Any Central Florida business whose recovery plan has to survive a hurricane.
- The problem
- A second site in Tampa or Jacksonville shares the same weather. A recovery target that a single storm can take out at the same time as production is not a recovery target.
- How it works
- Run production at Colo Solutions in Orlando and replicate over a private DACS-NX Bridge circuit to a recovery site outside Florida. DACS-IX alone has 11 sites in five regions — Atlanta, Northern Virginia, Baltimore, New York, Chicago, Las Vegas and Fremont among them.
- What you get
- Replication that never touches the public internet, to a location outside Florida, from a facility you can drive to.
Microsoft 365, Azure, AWS and Google without the long way round
Businesses and MSPs whose daily work lives in cloud platforms.
- The problem
- Ordinary internet transit carries your traffic through whichever networks are cheapest for the carrier, not shortest for you. Every extra hop adds latency and another place for congestion.
- How it works
- DACS-IX's Peering Fabric route servers peer with 28 named networks — Microsoft / Azure, Amazon Web Services, Google, Cloudflare, Zscaler, Salesforce, Cisco Webex and more — through Equinix IX Ashburn, NYIIX and FCIX. Peering hands traffic to those networks directly instead of buying the route.
- What you get
- Fewer hops to the platforms your staff use all day. Ask us which peers are reachable from an Orlando port — DACS states availability per subscriber.
One private network for every office
Organizations with branch offices across the Southeast or the country.
- The problem
- Site-to-site VPNs that each office manages separately, over whatever internet each office happens to have, are hard to secure and harder to troubleshoot.
- How it works
- Put the hub — servers, firewalls, file and line-of-business systems — in a Colo Solutions cabinet, and connect offices to it with DACS-NX Bridge point-to-multipoint circuits or DACS Tele, a fully managed secure WAN that DACS sets up, monitors and updates.
- What you get
- A hub in an N+1 facility with remote hands, and one provider responsible for the paths between your sites.
Healthcare and financial workloads
Practices, clinics, accounting and financial firms with regulated data.
- The problem
- Regulated data is safest when it travels the shortest, most private path, and lives somewhere with independently examined controls.
- How it works
- Colo Solutions' colocation services hold SOC 2 Type 2 (Security and Availability) and SOC 1 Type 2 reports and a HIPAA Security Rule examination, and Colo Solutions signs BAAs. DACS built its network business out of three decades of delivering financial and healthcare applications over private circuits.
- What you get
- Private paths between your locations and your data, ending in an examined facility. Colo Solutions' attestations cover its own colocation services — DACS services are separate, and are not in their scope.
MSPs and network operators
Managed service providers and anyone running their own network (an ASN).
- The problem
- Paying transit for traffic that could be exchanged directly, and reaching clients in other cities over the public internet.
- How it works
- Host client infrastructure at Colo Solutions, take a DACS-IX port to peer with other networks on the exchange, and use DACS circuits to reach client sites elsewhere.
- What you get
- Lower-latency paths for the traffic you carry, and a national footprint without building one. Colo Solutions' partner program pays a one-time referral payment or an ongoing residual. The partner program →
A second, independent way out
Anyone who cannot afford to be offline.
- The problem
- Two circuits from the same provider share the same failure modes.
- How it works
- Add DACS-NX Dedicated Internet Access as an additional upstream, alongside the nine carriers already in the building and Colo Solutions' own blended internet.
- What you get
- Genuine provider diversity. DACS advertises a 100% uptime service level agreement on its DIA.
