Back to news

BGP ORIGIN Rewrites Affect 70% of Paths; Lambda Gets Scaling Logs

Cloudflare's research exposes widespread BGP manipulation by transit providers, while AWS adds CloudWatch visibility into Lambda's managed compute scaling.

BGP ORIGIN Rewrites Affect 70% of Paths; Lambda Gets Scaling Logs

What happened

Cloudflare published findings showing that nearly 70% of BGP routing paths on the global internet have their ORIGIN attribute rewritten by transit providers, typically to gain traffic-routing advantages. The research argues that ORIGIN has become so routinely manipulated that its role in route selection should be formally deprecated. Separately, AWS announced that Lambda Managed Instances capacity providers now stream logs to Amazon CloudWatch, covering scaling events and instance lifecycle activity. LMI lets teams run Lambda functions on EC2 infrastructure while preserving serverless operational patterns, and the new logging pipeline closes a key observability gap.

Why it matters for your business

For network and security teams, Cloudflare's data reframes ORIGIN as an unreliable signal rather than a trustworthy routing input, meaning organizations relying on ORIGIN-based policies for traffic engineering or anomaly detection may be working from corrupted data. CTOs and infrastructure leads should audit whether any automated tooling treats ORIGIN values as authoritative and begin evaluating route-selection logic that does not depend on the attribute. On the AWS side, operations teams running latency-sensitive or high-throughput workloads on LMI now have actionable data for diagnosing capacity events, right-sizing provisioning rules, and building alerts around abnormal scaling patterns. The practical takeaway: treat BGP ORIGIN as advisory at best, and use the new Lambda logs to proactively tune capacity provider configurations before scaling incidents affect end users.

What to watch next

Cloudflare's push to deprecate ORIGIN in route selection could gain traction at the IETF level, so network architects should monitor working group discussions for proposed RFC changes that would formalize new selection criteria. On the cloud side, AWS is likely to extend structured logging and observability tooling deeper into LMI, potentially adding metrics integration with CloudWatch Container Insights or EventBridge triggers for automated remediation workflows.

Sources

Want this kind of clarity applied to your own systems?

HashWhales can review your website, infrastructure, security posture, and growth bottlenecks, then send a prioritized action plan.

Free AuditChat on WhatsApp