naranja网络太拉垮了
<i class="pstatus"> 本帖最后由 igoogle 于 2025-3-24 21:42 编辑 </i><br /><br />
收了mjj一个19o的naranja，发现网络太拉垮了。。<br />
<br />
本来只是用来做反代，但是发现连后端DE和NL的服务器，都有20%的丢包，<br />
<br />
ping Google都有5%的丢包，而且网络波动很大。。。<img src="https://hostloc.com/static/image/smiley/yct/006.gif" smilieid="32" border="0" alt="" /> <br />
<br />
发ticket要求换到其它母鸡，都不理会<img src="https://hostloc.com/static/image/smiley/yct/006.gif" smilieid="32" border="0" alt="" /> <br />
<br /><div class="blockcode"><div id="code_t0P"><ol><li>PING google.com(ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e)) 56 data bytes<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=1 ttl=119 time=1347 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=2 ttl=119 time=1334 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=4 ttl=119 time=2.63 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=3 ttl=119 time=1161 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=5 ttl=119 time=2.59 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=6 ttl=119 time=50.10 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=7 ttl=119 time=2.41 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=8 ttl=119 time=2.34 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=9 ttl=119 time=2.42 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=10 ttl=119 time=2.45 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=11 ttl=119 time=2.30 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=12 ttl=119 time=2.33 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=14 ttl=119 time=68.1 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=15 ttl=119 time=2.30 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=16 ttl=119 time=3.36 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=17 ttl=119 time=3.10 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=18 ttl=119 time=2.42 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=19 ttl=119 time=2.41 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=21 ttl=119 time=3.42 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=20 ttl=119 time=1068 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=22 ttl=119 time=2.60 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=23 ttl=119 time=4.02 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=24 ttl=119 time=2.37 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=25 ttl=119 time=3.10 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=26 ttl=119 time=2.32 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=27 ttl=119 time=2.22 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=28 ttl=119 time=2.55 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=29 ttl=119 time=4.17 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=30 ttl=119 time=979 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=31 ttl=119 time=2.37 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=32 ttl=119 time=901 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=33 ttl=119 time=758 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=34 ttl=119 time=2.32 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=35 ttl=119 time=769 ms<br /><li>64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=36 ttl=119 time=2.27 ms<br /><li>^C<br /><li>--- google.com ping statistics ---<br /><li>37 packets transmitted, 35 received, 5.40541% packet loss, time 953ms<br /><li>rtt min/avg/max/mdev = 2.221/242.922/1347.394/445.929 ms, pipe 2</ol></div><em onclick="copycode($('code_t0P'));">复制代码</em></div> ipv4呢 <div class="quote"><blockquote><font size="2"><a href="https://hostloc.com/forum.php?mod=redirect&goto=findpost&pid=16297360&ptid=1398217" target="_blank"><font color="#999999">江湖骗子 发表于 2025-3-24 21:46</font></a></font><br />
ipv4呢</blockquote></div><br />
一样，丢包甚至比v6更厉害 前阵子老是有人在出，有玄机，国外那个论坛有在说网络异常 <div class="quote"><blockquote><font size="2"><a href="https://hostloc.com/forum.php?mod=redirect&goto=findpost&pid=16297372&ptid=1398217" target="_blank"><font color="#999999">hkbbdx 发表于 2025-3-24 21:52</font></a></font><br />
前阵子老是有人在出，有玄机，国外那个论坛有在说网络异常</blockquote></div><br />
知道拉跨，不知道这么拉跨。。 不是，你们拿这种鸡来生产？我们是为了抗dmca，还得套CF，你直接就用？<img src="https://hostloc.com/static/image/smiley/default/titter.gif" smilieid="9" border="0" alt="" /> 30o还凑活用，18、19欧的还是放弃吧 的确够拉胯的，这网络丢包率高的不行 <div class="quote"><blockquote><font size="2"><a href="https://hostloc.com/forum.php?mod=redirect&goto=findpost&pid=16297586&ptid=1398217" target="_blank"><font color="#999999">acg88 发表于 2025-3-25 04:20</font></a></font><br />
不是，你们拿这种鸡来生产？我们是为了抗dmca，还得套CF，你直接就用？</blockquote></div><br />
它真抗吗？有卢森堡那么猛？ <div class="quote"><blockquote><font size="2"><a href="https://hostloc.com/forum.php?mod=redirect&goto=findpost&pid=16297669&ptid=1398217" target="_blank"><font color="#999999">宁静致远 发表于 2025-3-25 08:54</font></a></font><br />
它真抗吗？有卢森堡那么猛？</blockquote></div><br />
我从卢森堡换到naranja的9o没问题,0丢包. 说明不是网络拉胯, 是你的邻居作妖.
页:
[1]
2