Professional cable manufacturer
The voltage move to megawatt racks is real and it is funded. The specification layer underneath it has started to arrive — a certification standard for the cable itself was published in July 2026 — but connector qualification, DC arc-flash assessment and conductor identification are still open. Here is where each piece actually stands, and what to write in an RFQ while the rest catches up.
Published 31 Aug 2026 · Updated 3 Sep 2026 · Reviewed by Luo Qiang
800 VDC is a low-voltage DC power architecture for AI data centers that replaces 54 V rack distribution so one rack can reach 1 MW. It is not HVDC: 800 V DC sits inside the IEC low-voltage band, which tops out at 1500 V DC. No ratified 800 VDC data center cable standard exists yet from IEC, ISO, UL, NFPA or ANSI.
800 VDC is a power-delivery architecture for AI factories, pushed hardest by NVIDIA with Google, Microsoft and OCP named alongside it, that replaces rack-level 54 V distribution so a rack can climb toward 1 MW. It is low-voltage DC, not HVDC — inside the IEC band that tops out around 1500 V DC. What is settled: the architecture, the partner ecosystem, the fact that switchgear sold to the IEC 61439 family already covers DC to 1500 V, and — as of July 2026 — a certification standard for the cable itself, published jointly by China Quality Certification Centre, TÜV Rheinland and Shanghai Guolan Testing. What is not settled: no IEC, ISO, UL, NFPA or ANSI document names 800 VDC for data centres, IEEE 1584 arc-flash calculation is scoped to AC, and DC fault current has no natural zero crossing for a breaker to interrupt into. Buyers should name the standard they are testing to and demand DC test evidence; "800 VDC compliant" on its own still means nothing, because there is no 800 VDC system standard to be compliant to.Most coverage of 800 VDC is written from the silicon side — who wins the power-switch sockets. Almost none of it is written from the copper side, which is where our readers live. That gap is the whole reason for this article, and it is now narrower than it was: the cable half of the specification layer started to close in July 2026.
NVIDIA's product page says it, with Google, Microsoft and OCP, "sets the 800 VDC standard." Read plainly, that sentence has caused more confusion in the last twelve months than the architecture itself. The word standard is doing two different jobs, and buyers keep getting charged for the wrong one.
Here is what we could and could not establish. As of early September 2026, we found no IEC, ISO, UL, NFPA or ANSI document that names 800 VDC for data centres. Dell'Oro's recap of the OCP Global Summit — an independent analyst firm, not a vendor press release — describes the industry as pushing toward an open standard, with "much remains in flux" and "codes and standards will need to evolve accordingly." That remains the accurate reading of the system side: 800 VDC is an industry alignment, a reference design and a contribution pipeline. It is not a document you can certify a whole installation against.
The product side is a different story, and it changed while we were writing. On 9 July 2026, at the Open Compute Tech Summit in Beijing, China Quality Certification Centre (CQC), TÜV Rheinland and Shanghai Guolan Testing published a High-Voltage DC Cable for Data Centres standard (CQC announcement), developed from a first review meeting held in Wuxi on 23 April 2026 with nine cable and materials manufacturers signed on as drafters. CQC's own wording is that it "precisely fills the gap in standards supporting 800 V power supply," and it focuses on three things a cable buyer actually cares about: electrical safety, mechanical performance, and long-term thermal endurance.
Why does this distinction matter to a buyer? Because "compliant to the 800 VDC standard" is a sentence a supplier can write on a quotation and nobody can check. If you are the one signing the purchase order, the useful question is not "is it 800 VDC compliant" but "which published standard does this product test to, and which questions about DC duty are you answering outside any standard."
Because at megawatt-class racks, the low-voltage answer stops being an engineering trade-off and starts being a physics wall.
Do the arithmetic on one 1 MW rack. At the 54 V busbar that has sat inside server racks for years, 1 MW is roughly 18,500 A. At 800 V it is about 1,250 A. Those are not connector part numbers, they are busbar cross-sections, torque, thermal mass and the weight of the copper you have to hang overhead. NVIDIA frames it the same way in its own words: traditional 54 V in-rack distribution "isn't designed to support the megawatt-scale racks." The company also puts the busbar mass behind a 1 MW rack at around 200 kg, and extrapolates that to 200 tonnes of copper for a gigawatt facility — its own figure, presented as an illustration rather than a measured build.
We ran the copper comparison once already, in our AI data center power cable design guide, which carries the 208 V / 415 V / 480 V / 800 VDC table and the thermal side of it. What that table cannot tell you is which of the circulating efficiency claims are actually independent — so here they are side by side instead.
Notice something else in that line-up. NVIDIA's product page compares 800 VDC against a 480 V AC facility baseline; its technical blog compares against 415 V AC. Both are real three-phase facility voltages, and the vendor's own materials disagree about which one is the reference. When you see a spec sheet or a sales deck quoting a percentage saving, the first question worth asking is against what.
This is the part most cable buyers haven't seen, because it doesn't fit the headline. The data-centre DC conversation is not "AC versus DC." It's a fight between two DC topologies, and they don't put the same demands on your conductors.
NVIDIA's is a single unipolar 800 V bus — its own blog describes two-conductor 800 V feeds running down the aisle. The competing approach is ±400 V DC: a bipolar system with a mid-point, so three conductors carry two poles at 400 V to mid. Same delivered power, different cable count, different voltage-to-earth on every insulation surface, different fault loop. The ±400 V work is associated with Open Compute Project documentation under the name "Mt Diablo," and OCP's own announcement describes a published Mt Diablo ±400 V sidecar specification with a later revision to support native 800 V.
| Item | 800 VDC (unipolar) | ±400 VDC (bipolar) |
|---|---|---|
| Conductors per circuit | 2 | 3 |
| Voltage to midpoint | Full 800 V across the pair | 400 V per pole |
| Pole-to-pole fault | 800 V event | 800 V event |
| Pole-to-mid fault | Not applicable | 400 V event |
| Tray fill and copper | Lower conductor count per circuit | Higher conductor count per circuit |
| Standard status | Certification standard for the cable exists (CQC/TÜV, Jul 2026); no system standard | OCP "Mt Diablo" documentation; no published DC bus standard |
Why should a cable buyer care about a topology fight they aren't part of? Three concrete reasons. Conductor count changes the copper per circuit and the tray fill. Voltage-to-earth changes insulation stress, creepage and clearance, and therefore what you test to — the same principle we set out in our comparison of why DC and AC cable are not interchangeable. And a fault between one pole and mid on a ±400 system is a 400 V event, while a pole-to-pole fault is 800 V — the same nominal "800 V class" bus can present two very different fault duties to your protective device.
On who backs what, we'll be careful. NVIDIA names Google, Microsoft and OCP. Trade coverage puts Meta behind the ±400 V camp instead, and describes Google and Microsoft as working both sides — but that attribution traces to a single supplier analysis, from a company selling the switching semiconductors that either outcome would consume. So we won't state it as fact. What we can say is that two architectures are live, and nobody outside the hyperscalers knows which one their next project will be.
This is the section we wrote the article for. Take the things you'd normally pin a data-centre power cable to, and ask what covers them at 800 V DC in a computing facility.
Unpack the two rows that carry the most weight.
Switchgear is further along than people assume. The IEC 61439 family covers low-voltage switchgear and controlgear assemblies, and its scope reaches 1000 V AC or 1500 V DC. The 2020 edition of the general rules adds explicit requirements in respect of DC — precisely because DC gives you continuous arcing during a fault with no natural current zero to interrupt into. So 800 VDC is inside that envelope. Confirm the clause reference against the edition you are actually buying to before it goes on a submittal; the voltage limits in particular are worth reading in the primary text rather than in anyone's summary, including ours.
Arc-flash assessment is the real hole. IEEE's own scope title for 1584.2-2025 puts it in the world of "Three-Phase 50/60 Hz AC 1000 V and Below." Schneider Electric's August 2026 study and its accompanying white paper WP219 say the same thing in plainer language: the assessment methods in use were developed for AC systems, and the analysis is "preliminary, direction-setting."
An 800 VDC bus isn't automatically more dangerous than a 415 V AC one. It's differently dangerous.
That distinction is the one worth carrying into any DC design review: system topology affects arc-flash exposure more than the voltage level itself. The difference is converter-driven, time-dependent, and full of capacitor discharge in the first milliseconds.
| Document | What it actually covers | Status for 800 VDC | Buyer action |
|---|---|---|---|
| IEC 61439 family | LV switchgear and controlgear assemblies; the 2020 general rules add DC requirements; scope quoted to 1000 V AC / 1500 V DC | Covers the duty | Ask which part and which edition the assembly is type-tested to, and for the DC clause |
| IEEE Std 1584 / 1584.2-2025 | Arc-flash hazard calculation guides | AC-scoped by title | Don't accept an AC arc-flash study as DC evidence; ask what method was used |
| High-Voltage DC Cable for Data Centres — CQC / TÜV Rheinland / Shanghai Guolan Testing | Cable electrical safety, mechanical performance and long-term thermal endurance; published at OCTS 2026 after a first review meeting on 23 Apr 2026 | New in this revision | Get the standard number and scope from CQC before citing it. It is a certification-body standard, not an IEC or UL document |
| ISO/IEC 22237-1 (2021) and -3 (2021); ISO/IEC TS 22237-5 (2018, under revision) | Data centre facilities and infrastructures — general concepts, power distribution, telecom cabling | Current; predates 800 VDC | Useful for facility-level intent, not for DC product qualification |
| IEC 61140 / 60364 series | Shock-protection thresholds and LV installation rules; the LV band is quoted to 1500 V DC | 800 VDC is inside LV, not HV | Confirm the band figures against the standard you're designing to |
| EN 50575 / IEC 60332 / IEC 61034 | Reaction to fire, flame propagation, smoke production of installed cable | Applies unchanged | Fire class is still a separate question from voltage class — specify both |
| ANSI/UL 489I Ed.1 (2025) | Solid-state and solid-state hybrid circuit breakers rated to 1000 Vac / 1500 Vdc; an Outline of Investigation, not yet a consensus standard | Device-level path only | A device certification path exists, but it does not solve system-level coordination at 800 VDC |
| An 800 VDC data-centre system, connector or protection standard from IEC, ISO, UL, NFPA or ANSI | — | None found as of Sep 2026 | Treat "800 VDC compliant" as an unsupported phrase; ask which real standard is behind it |
| UL 891 / 1977 / 1699 / 489 / 248 DC ratings | Switchboards, busways, arc-fault devices, branch protection, fuses | Not verified this session | DC ratings vary by certification scope — check the specific UL file number rather than the standard title |
That last row is unusual for an article like this, and deliberately so. We looked at the DC voltage ratings quoted for the North American product standards and found they differ by manufacturer and by certification scope, so we haven't printed numbers for them. If you're selling into a US project that needs them, go get them from UL rather than from a blog — including ours.
Terminology drift is doing quiet damage here. Several trade articles call 800 VDC "HVDC," and one even used the phrase "±400 V HVDC." It isn't.
Back to procurement: because 800 VDC is low voltage, it inherits the LV rulebook rather than the medium-voltage one. No MV switchgear discipline, no MV cable class, no utility-style protection scheme. That's good news for cost and bad news for rigour, because the LV rulebook was written for a world where nobody ran hundreds of amperes of DC through a computer room.
On the US side, the number to hold on to is the one we verified for our NEC 2026 data-center power guide: the code's medium-voltage articles begin above 1000 V AC / 1500 V DC nominal. 800 V DC is comfortably under that line, so it stays in the general provisions. The 1500 VDC BESS cable whitepaper covers the voltage-class logic that carries across, and it's a better template for questioning a DC cable supplier than most data-centre material currently published.
Strip out the marketing and an 800 VDC bus asks a cable to answer six questions an AC feeder datasheet never had to.
Rows 3 and 4 deserve the space, because they're where "it's just a higher DC voltage" thinking falls apart.
Then there's the one nobody raises until the cable is on site: conductor identification. The colour schedule most of Europe sells AC cable against, HD 308, doesn't reach DC at all — Nexans' own guidance lists cables for DC applications as outside its scope. So "brown for positive, grey for negative" tables you'll find circulating online aren't HD 308 answers, and we could not find a single authoritative schedule for a DC bus in a computing facility that we'd be comfortable printing as fact. If a customer asks you for polarity-marked DC conductors, treat the identification method as an open item to close with the designer of record, not a line to fill from a datasheet. Our HD 308, BS 7671 and NEC colour-code guide covers where the AC rules do agree — and where they don't.
Two years of grey zone. Here's how we'd work it, and none of it involves guessing which hyperscaler wins the topology fight.
Items 1 and 2 are the two worth dwelling on, because there is a right way and a wrong way to ask. There is no agreed DC withstand value for an 800 VDC data-centre cable — that is the point. So don't ask "does it pass a DC withstand test." Ask what voltage, applied for how long, against which clause, and on how many samples. A supplier who can answer all four has done the work; one who answers "yes" has not.
One page, nine lines, current as of 3 September 2026. The middle column is the one to quote in a meeting; the right-hand column is the one that keeps you out of trouble.
| Item | Status as of 3 Sep 2026 | What to do about it |
|---|---|---|
| The architecture itself | Settled — public whitepapers, named partners, hardware shown at OCP Global Summit 2025 | Assume it's coming for megawatt racks; don't assume it's coming for yours |
| 800 VDC vs ±400 VDC | Two live topologies; the camp split is reported by a single supplier analysis | Qualify to a voltage class and topology, not to a brand's roadmap |
| Voltage classification | 800 VDC is low-voltage DC under IEC bands, not HVDC (band figures via secondary summaries) | Correct the "HVDC" wording when you see it in a specification |
| Switchgear assemblies | IEC 61439 covers DC duty to a quoted 1500 V DC ceiling | Ask which part and edition; confirm the DC clause yourself |
| Arc-flash assessment | IEEE 1584 line-up is AC-scoped; DC methods described as AC-derived and preliminary | Require the method name; refuse an AC study presented as DC evidence |
| Cable product standard | A certification standard for the cable was published in July 2026 by CQC, TÜV Rheinland and Shanghai Guolan Testing. Number and scope not published in the announcements | Get the number and scope from CQC. Note it is a certification-body standard, not an IEC or UL document |
| Connector product standard | No published 800 VDC data-centre connector standard found | Specify named connector standards plus DC test reports; drop "800 VDC compliant" |
| Conductor identification | HD 308 does not cover DC applications, per one cablemaker's guidance | Agree the polarity marking method with the designer, in writing |
| Fire performance | Unchanged and independent of voltage class | Specify as normal — EN 50575 / UL listing still required |
Every standards statement above was checked against at least two sources where two exist, and marked as single-source where they don't. The IEC band figures came from secondary summaries of paywalled standards, NVIDIA's whitepaper-level detail sits behind a gated CDN we could not open, and the CQC/TÜV standard we have not seen the text of. Confirm against the primary documents before any of this enters a contract or a design.
Not one from IEC, ISO, UL, NFPA or ANSI, as far as we could find. What exists is the general low-voltage DC rulebook — IEC 61439 for assemblies, DC-rated protective devices, installation standards that treat 800 V as low voltage — plus NVIDIA's own reference architecture, which it describes as setting a standard but which is an industry alignment rather than a published normative document. Since July 2026 there is also a cable-specific standard published jointly by CQC, TÜV Rheinland and Shanghai Guolan Testing; we have not seen its text and its number has not been published, so get both before citing it. Specify against named existing standards and ask for DC test evidence.
No. Under the IEC voltage bands quoted in the sources we read, 800 V DC is low-voltage DC — above extra-low voltage, well below the medium-voltage threshold, which the NEC places above 1000 V AC / 1500 V DC. Calling it HVDC in a specification will send your supplier looking in the wrong product catalogue. The practical effect is that 800 VDC inherits the LV rulebook, which was never written with hundreds of amperes of DC inside a computer room in mind.
Conductor count and voltage stress. A unipolar 800 V bus is two conductors with the full 800 V across them. A bipolar ±400 V bus is three conductors, with each pole at 400 V to the midpoint, so a pole-to-mid fault is a 400 V event while a pole-to-pole fault is 800 V. Same nominal class, different insulation stress to earth, different fault duty, different tray fill. Which one wins isn't settled, and a line qualified for one isn't automatically qualified for the other.
No. Reaction to fire is a property of the cable in the building, not of the circuit it carries. EN 50575 classes, IEC 60332 flame propagation and IEC 61034 smoke measurement apply the same way whether the bus is 415 V AC or 800 V DC. Keep fire and voltage in two separate columns of your specification — treating them as one question is how cables get approved on the wrong basis.
Probably not for the next build, and that's worth saying plainly. The public roadmap points at 800 VDC power hardware in the second half of 2026 and full rack or row deployments around 2027, tied to specific NVIDIA generations, and independent analysis expects hybrid AC-and-DC deployments to dominate in the meantime. There's no announced date for when this becomes procurable outside hyperscale-style builds. What a non-hyperscale buyer should take from it is the procurement hygiene: name your standards, demand DC test evidence, and put a standards-change clause in your contracts.
Specifying a DC bus against a standard that isn't written yet?
Tell us the voltage, the topology and the certification date. SORIVO will quote DC-duty cable and assemblies against named standards, with the DC withstand and ampacity evidence to go behind the claim — and flag the lines where no standard exists yet. Or email sale@sorivocable.com directly.
