Urgent.News

What's breaking now, across thousands of outlets.

Tech

Co-Packaged Optics vs Pluggable 1.6T: Who Pays When the Laser Dies

The switch industry has spent a decade promising that optics would move onto the package. In 2026 it is finally happening, in volume, at 51.2 terabits per second per chassis. The interesting question is no longer whether co-packaged optics works. It is who absorbs the operational consequences, because those consequences are not symmetric between a hyperscaler and everyone else. Pluggable optics…

The co-packaged optics debate revolves around the shift in the industry's packaging approach for optics, with a focus on whether hyperscalers or other entities bear the operational consequences. The transition from pluggable to co-packaged optics has shown notable differences in failure mode and cost implications. Pluggable optics are easily replaceable, consuming around 12-15 watts for 800G, while co-packaged optics integrate the photonic engine with the switch ASIC, resulting in a lower power consumption for the engine at 5-7 watts but a higher overall system-level saving due to the removal of the retimer and package-to-front-panel path.

However, the failure model of co-packaged optics is different, as a failure in the integrated engine could lead to a more costly chassis replacement instead of a simple field-replaceable unit swap. This change in failure mode carries significant implications for the operational rhythm and cost structures of different network environments.

At 1.6T, pluggable modules are projected to draw 25-30 watts, with the front-panel power budget of a 1U switch reaching its limit. This situation is expected to drive the adoption of co-packaged optics due to physical constraints. As the industry moves towards standardisation and multi-vendor optical engines, the transition from proprietary interfaces to open standards is anticipated to occur within one product cycle, ultimately affecting the pricing and availability of network services.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

High-NA EUV vs Multi-Patterning: The 2nm Decision Nobody Wants to Price

Every leading-edge fab that plans to ship a 2nm-class node in the next three years is having the same argument behind closed doors. The question is not whether High-NA EUV works.

  • High-NA EUV scanners enable 8nm features, compared to 13nm for low-NA systems
  • High-NA scanners cost $350-$400M upfront, higher than low-NA systems
  • Fewer patterning passes in High-NA EUV reduce cycle time and working capital costs

My app passed 1,100 tests. Six minutes on a real phone found five bugs.

I'm building a budgeting app called Budget Lover. It is a personal project, written in Flutter with Firebase behind it, and it tries to answer one question: how much can I spend today?

  • App tested on real phone for six minutes
  • Five bugs discovered despite 1,100+ automated tests
  • New tests added to address each identified bug

More from Wednesday 4 November →