Hybrid-cloud interconnect design
Architecture sessions with our network team to lay out hybrid topologies between your colo footprint and your cloud accounts.
Real operations
Cabinet space, cross connects, and remote hands inside Atlanta.
We help Southeast businesses and Atlanta-area IT teams placing hardware close to home land hardware in Atlanta — from rack-and-stack day through year-five renewal — without the network surprise stories.
Xilogix Atlanta colocation is now operated by Coloblox Data Centers. Existing Atlanta colocation contracts continue through their original term, and new Atlanta colocation requests across Georgia and the Southeast are handled by the Coloblox team.
What you get by default
Why teams place hardware here
-
01
Operational maturity
We have racked everything from one-off lab boxes to GPU clusters. Your engineers will not be teaching ours how a chassis works.
-
02
Long contract horizons
Three- and five-year terms with predictable annual escalators, plus break clauses that do not require a litigation budget to invoke.
-
03
No metered ‘everything’
Power is metered, bandwidth has burstable and committed options, and the rest is flat. You can model annual spend on a single page.
-
04
Cabinet-level metering
Per-cabinet kW visibility in a portal we built ourselves. Alerts on draw, temperature, and door-open events route to your channels.
-
05
Transparent pricing
Cabinet, kilowatt, cross connect, remote-hands hour. Each line item shows up on the invoice as exactly that — no metered surprises.
What we do
Where we add value
Capabilities most customers buy from us. Anything not on this page can usually be quoted on request.
Compliance evidence support
We provide audit packets — SOC 2, SSAE 18, PCI evidence — and sit in customer audit interviews when the auditor asks for the host facility.
Remote hands
Trained engineers available 24/7 for cabling, swaps, reboots, console access, and structured break/fix work — billed in 15-minute increments.
High-density cabinets
Cabinets pre-engineered for 2–6 kW workloads: contained airflow, blanking panels, and dedicated cooling allocation.
What we do consistently
-
01
Direct line to engineering
After the first 30 days, your operations lead gets the cell phone numbers of our shift engineers. Tickets still get filed; the phone calls happen anyway.
-
02
Carrier-agnostic procurement
Bring your own carrier or pick from our blended transit. Either way, we do not get a kickback that biases the recommendation.
-
03
First-week shadow operations
For new customers, our NOC works in the same channel as yours for the first seven days. After that, we step back to documented escalation paths.
-
04
Maintenance windows that respect your schedule
We propose windows. You confirm. Customer-led abort criteria are baked into every change order, not added on request.
-
05
IPv6-first networking
Dual-stack from day one, with IPv6-only options and route-object filing assistance for customers running their own ASN.
Why this location
Why Atlanta
Latency from Atlanta to AWS us-east-1 in northern Virginia typically lands in the 11–14 ms range over well-engineered transit, which is why so many southeastern teams treat Atlanta as their primary hardware location and keep cloud as a secondary tier.
Our facility sits on a substation feed shared with two municipal customers, which historically correlates with prioritized utility restoration. We document that distinction in the customer onboarding packet — and we do not exaggerate it.
Beyond 56 Marietta Street, the metro's data-center mass has spread north and east — Suwanee, Lithia Springs, Douglasville, and the Northlake corridor all carry serious facilities now. We interconnect to that wider footprint instead of treating downtown as the only address that counts.
24 hour
standard cross-connect turnup commitment
<7 ms
Atlanta to Charlotte, Nashville, and Jacksonville users
5 kW
supported per-cabinet density without escalation
About the acquisition
Why Xilogix joined Coloblox Data Centers
We built Xilogix in Atlanta because the Southeast deserved a colocation operator that answered the phone. Coloblox shares that posture — and brings the floor space, capital, and network footprint to do more of it.
Xilogix has operated Atlanta colocation since the mid-1990s out of a single fiber-dense location inside the metro. The customer roster grew the way good regional operators grow: by word of mouth from one CTO to another, slowly, with very low churn. Customers who started with a quarter cabinet for a backup target ended up running their primary site here.
By 2013 we were turning away requests we could not fill without expanding floor space. Coloblox approached us with a thesis we already believed in: that the Southeast — Atlanta, Charlotte, Nashville, Birmingham, Jacksonville — has been chronically underserved relative to Ashburn and Dallas, and that a regional operator who treats each customer like the only one is the right vehicle to fix that. The financial and operational fit was straightforward; the cultural fit took longer to validate. After two quarters of working alongside their Atlanta team, we were comfortable that the operations standard would survive the transition.
The Xilogix brand is retiring. The floor, the engineers who run it, and the customer relationships are all moving under Coloblox Data Centers. Pricing locks in your contract continue to apply through the original term. The same person who has been answering your tickets will still be answering your tickets — just from a coloblox.com email address.
Transition timeline
What is changing, and when
Cutover is a multi-quarter program, intentionally. Nothing customer-facing happens before you have at least 60 days of notice in writing.
-
Now
Operations integrated, brand parallel
Coloblox engineers are on the Atlanta floor full-time. The Xilogix portal, ticketing system, and on-call escalation paths continue to work exactly as they did. Invoices still come from Xilogix entities under existing MSAs.
-
Q1 — Q2
Portal and ticket consolidation
The Xilogix customer portal will redirect to the Coloblox portal at coloblox.com. Tickets in flight migrate with their full history; portal logins move to SSO. We will publish the exact cutover date 60 days in advance and run a parallel window for two weeks on either side.
-
Q3
Billing entity rollover
Customers under month-to-month or annually-renewing contracts roll onto Coloblox Data Centers MSAs at renewal. Multi-year contracts continue under Xilogix entities until their original expiration. Tax IDs and W-9 paperwork for the Coloblox entity are available on request today.
-
Q4
xilogix.net redirects to coloblox.com
Once the last Xilogix-entity contract has rolled over, this domain begins redirecting to the Atlanta region page on coloblox.com. Email forwarding from @xilogix.net to @coloblox.com remains in place for an additional twelve months for archived correspondence.
Customer transition FAQ
What current customers ask first
Pulled from the questions we have answered most often since the announcement. Anything not covered here, raise the ticket against your existing Xilogix support queue — it routes to the same engineers it always did.
Does my contract pricing change?
No. Pricing on your current Xilogix Atlanta colocation contract continues through the term you signed. Annual escalators, if your contract had them, continue at the same percentage and on the same anniversary. The renewal conversation, when your term ends, happens with Coloblox under a Coloblox MSA — and we will run that conversation by your stated renewal-process timeline.
Will my point of contact change?
Most likely no. The Atlanta engineers, account leads, and NOC staff you have been working with are continuing in their roles under Coloblox. The largest near-term change is that their email addresses migrate from @xilogix.net to @coloblox.com — both addresses will resolve to the same inbox for at least twelve months after cutover.
Does the meet-me-room change?
No. The carriers in the meet-me-room — Zayo, Hurricane Electric, AT&T, Verizon, and the regional providers Xilogix has cross-connected to over the years — remain in place. Existing cross connects continue to be billed at the rate locked into your contract. New cross connect orders submitted after cutover are quoted under the Coloblox rate card, which we have published side-by-side with the Xilogix rate card for comparison.
What happens to my Xilogix portal account?
Your Xilogix portal login continues to work through the portal-consolidation window. About 60 days before the consolidation date, we will email you a one-time link to claim your Coloblox SSO identity, which will then have access to all your existing footprints, tickets, invoices, and asset records. Ticket history, environmental telemetry, and badge-event logs migrate fully; nothing is lost.
Xilogix in Atlanta
A regional operator with a Southeast story
Xilogix was not a national colocation company. We were an Atlanta colocation company that happened to serve customers from across the Southeast. The acquisition does not change that.
The Xilogix floor sits inside a building originally engineered for telecom switching, not retrofitted from a warehouse. Floor loading was specified for telephony-era equipment, which translates directly to the per-cabinet weight tolerances modern storage and GPU footprints need. Ceiling height accommodates contained airflow without compromise. The cooling-to-white-space ratio was set in the original telecom design and remains higher than most converted-warehouse Atlanta facilities advertise.
Our customer base reflects the Southeast economy. We host hardware for regional health systems running HIPAA workloads, fintech firms that took the cloud math seriously and moved their primary site back to a colo footprint, MSPs serving Atlanta-area mid-market customers, and a steady tail of single-server placements that grew over five and ten years into half-cabinet and full-cabinet customers. Many of our customers are headquartered in metros from Charlotte to Birmingham; Atlanta is the inland colo leg of a multi-site disaster-recovery plan for organizations whose primary footprint sits in coastal Florida or the Carolinas.
Coloblox understood from the first conversation that this was the customer relationship being acquired — not just a 1U-per-month revenue line. The transition program reflects that. The Atlanta engineers stay. The contracts stay. The pricing stays. The phone number stays. The brand on top of the door changes; the operations standard underneath does not.
What Coloblox adds
Capabilities expanded under the new ownership
Things customers asked us for and could not get from Xilogix alone. Available to existing customers immediately; available to new customers as standard offerings.
Multi-region disaster recovery
DR target footprints in Coloblox's other regions — including secondary southeastern metros — are now bookable under a single MSA. Replication-ready cabinets are pre-cabled and pre-quoted, with tabletop exercise facilitation included.
Expanded cloud on-ramp footprint
AWS Direct Connect, Azure ExpressRoute, Google Cloud Interconnect, and Oracle FastConnect ports in Atlanta are now provisioned through Coloblox's existing aggregator contracts, which usually beats single-port pricing on volume.
24/7 NOC outside Eastern time zones
Follow-the-sun NOC coverage with engineers in three time zones. Xilogix ran a strong Atlanta-hours operation with on-call for nights; Coloblox carries a staffed seat through every hour of every day.
Engineering services depth
Network engineering, migration cutover support, and BGP/ASN consulting hours are bookable at a published rate. Xilogix used to do this informally; under Coloblox it is a productized line item.
Larger footprint inventory
Half-cage and full-cage builds — 8-, 16-, and 24-cabinet — are now available without a waitlist. Xilogix was capacity-constrained on cage builds in 2024; the Coloblox footprint resolves that constraint immediately.
Sustainability reporting
PUE published quarterly, renewable-source contract disclosures, and embodied-carbon accounting for cabinet builds. Xilogix tracked this internally; Coloblox publishes it to customers as a regular cadence.
Talk to the transition team
Whether you are an existing Xilogix Atlanta colocation customer with a tactical question, an active prospect mid-evaluation when the acquisition was announced, or a Southeast organization looking at regional colocation for the first time — the conversation continues at coloblox.com.
Carrier-neutral
Carriers in the meet-me-room
We do not own the transit. The carriers below land their fiber inside the building, you cross-connect to whichever one fits your routing policy, and the per-circuit fee is flat. We make money on rack space and operations — not on which carrier you pick.
Plus regional fiber providers reachable via documented cross-connect paths inside the Atlanta metro interconnection footprint.
- Zayo National long-haul fiber and Layer-2/3 transport
- Hurricane Electric IPv4/IPv6 transit with one of the largest backbones globally
- AT&T Tier-1 IP transit, MPLS, and dedicated internet access
- Verizon Tier-1 transit and enterprise WAN options
What you will pay for
Indicative tiers below. The pricing page lays out the full structure; a written workload description gets a numbered quote within 24 hours.
Quarter Cabinet
Built for single-server placements and small footprints. The fastest path from contract to powered-on hardware.
Half Cabinet
Designed for the workload that has outgrown a half cabinet but does not need a private cage. Most customers live here.
Full Cabinet
For organizations that treat the cabinet floor as their primary site, with the contractual and operational rigor that implies.
FAQ
What happens during a regional power event?
Generators carry the floor. We hold 72 hours of fuel against full design load, with priority refill contracts in place. Transfer is tested monthly under load — not just simulated.
What is the cross-connect provisioning time?
24 Hours is our standard commitment for in-building cross connects. Expedited turnups are available with a defined surcharge — we quote them, we do not improvise them.
Do you offer managed services?
We offer structured remote-hands support. We do not offer fully managed services — that is a different business, and we are honest about not running it.
Do you publish a real SLA with credits?
Yes. Power and cooling SLAs pay credits when missed. Network SLA covers blended transit. We publish exclusions clearly in the contract — not buried.
Where is the facility located?
We operate from a Atlanta metro site selected for low flood risk, prioritized utility restoration, and proximity to Atlanta's primary interconnection points. Further details are shared after an NDA — like most colocation operators, we do not publish floor maps publicly.
How is bandwidth billed?
Committed-rate or 95th-percentile, customer's choice. Burstable ceilings are documented.
What active customers tell us
“The team treats our runbook as the source of truth. We did not have to fight to get them to follow it.”
See pricing first.
Most colocation buyers want to know if we are in range before booking a call. The pricing page covers the model in detail.