TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Net Ops, what's a customer to do – years of packet loss at Level 3

3 点作者 biturd将近 10 年前
This has literally been going on for over a year, I can tell Comcast, but it is like talking into a black hole.<p>Traces from me, near always, look about like this: http:&#x2F;&#x2F;pastebin.com&#x2F;81dvXj0v<p>Two offenders are always Level 3, always 60% loss or more:<p>ae-4-90.edge1.SanJose3.Level3.net te-11-0-2.edge4.Frankfurt1.level3.net<p>There is still ~4% loss on the first node outside my network. Even the IP address I am given, and is a few feet away, has loss. I have tried this wired and wireless. I can load a page faster over a 3G wireless hotspot on my phone than I can wired. Oddly, I get 50+ Mbit on a speed test. But to try to load a heavy page like &quot;the verge&quot;, with 14M+ and hundreds of files it is calling, never works.<p>Who do I report this to? How can this go on so long and not get solved?<p>Thank you for any pointers.

3 条评论

wmf将近 10 年前
<i>How can this go on so long and not get solved?</i><p>Because Comcast is probably doing it on purpose. <a href="http:&#x2F;&#x2F;blog.level3.com&#x2F;open-internet&#x2F;observations-internet-middleman&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blog.level3.com&#x2F;open-internet&#x2F;observations-internet-m...</a> <a href="http:&#x2F;&#x2F;arstechnica.com&#x2F;business&#x2F;2015&#x2F;05&#x2F;comcast-ends-an-interconnection-fight-before-net-neutrality-takes-effect&#x2F;" rel="nofollow">http:&#x2F;&#x2F;arstechnica.com&#x2F;business&#x2F;2015&#x2F;05&#x2F;comcast-ends-an-inte...</a>
sbuttgereit将近 10 年前
I feel your pain:<p><pre><code> 2 48 ms 11 ms 9 ms 96.120.89.137 3 10 ms 12 ms 26 ms te-0-7-0-0-sur03.sfmission.ca.sfba.comcast.net [68.85.103.129] 4 14 ms 12 ms 11 ms be-210-ar01.santaclara.ca.sfba.comcast.net [68.85.57.245] 5 281 ms 1030 ms 974 ms te-11-0-2.edge4.Frankfurt1.level3.net [4.68.127.105] 6 964 ms 1007 ms 1028 ms ae-4-90.edge1.SanJose3.Level3.net [4.69.152.208] 7 284 ms 689 ms 1048 ms 72.14.223.91 8 444 ms 1074 ms 927 ms 72.14.234.173 9 427 ms 980 ms 1012 ms google-public-dns-a.google.com [8.8.8.8] </code></pre> And that&#x27;s when the higher latency hops don&#x27;t just time out.<p>If that Frankfurt1 actually means Frankfurt... as in Deutschland... the latency makes sense, though I&#x27;m curious as why that route.<p>EDIT: Actually for me it&#x27;s all egress from the comcast network. Comcast told me that they&#x27;re currently doing some work that is the cause. Naturally, your mileage may vary.
biturd将近 10 年前
Also, this does not look too good for level 3 either, at least, not at first glance and my understanding of how to interpret the results.<p><a href="http:&#x2F;&#x2F;www.dslreports.com&#x2F;routerwatch&#x2F;ae-4-90.edge1.SanJose3.Level3.net" rel="nofollow">http:&#x2F;&#x2F;www.dslreports.com&#x2F;routerwatch&#x2F;ae-4-90.edge1.SanJose3...</a>