This presentation investigates the proximity to a low Signal-to-Noise Ratio (SNR) threshold that can still maintain a tolerable Bit Error Rate (BER) in 100G / 400G / 800G network links. Additionally, we account for factors such as temperature and cable length to predict the duration for which a reliable network connection can be sustained between transceivers. The analysis, based on data...
In response to increasing regulatory pressures, major telecommunications providers have begun to measure and report their carbon footprints. However, this initial step is just the beginning of a complex journey toward achieving sustainability. One of the most significant challenges these companies face is addressing Scope 3 emissions, which are generated by their supply chains and lie outside...
AI represents one of the biggest inflection points in the modern world of technology. Hyperscalers and other companies see a once-in-a-lifetime opportunity to leverage AI to enhance existing business models and create new innovations. Today the only way we know of to enhance AI performance is to use more and more compute power to train Generative AI models. This in turn seems to require...
This presentation explores the impact of recent submarine cable outages in the Baltic Sea and how the Internet adapted to maintain connectivity. Using RIPE Atlas measurements, we analyze latency shifts, packet loss, and rerouting patterns following incidents affecting the BSC East-West and C-LION1 cables.
A long format talk on handling extremes of weather when your network is mostly outdoors, covering the basics of wind, snow, heat and cold, and then focusing on the events of October 23 and Storm Babet and how we managed to keep our network running with our office and primary POP under 4ft of floodwater, and the lessons we learned form it
Draft Powerpoint presentation attached
How we route-leaked everything to everyone due to a fun Arista bug.
A post-mortem kind of story about us changing Arista RCF function names, resulting in a global route leak. The talk includes the history of why we intended to make a change, how we rollout configurations, why it resulted in an unexpected behavior and how it was fixed.
