naranja网络太拉垮了

igoogle

收了mjj一个19o的naranja，发现网络太拉垮了。。

本来只是用来做反代，但是发现连后端DE和NL的服务器，都有20%的丢包，

ping Google都有5%的丢包，而且网络波动很大。。。

发ticket要求换到其它母鸡，都不理会

1. PING google.com(ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e)) 56 data bytes
   
2. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=1 ttl=119 time=1347 ms
   
3. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=2 ttl=119 time=1334 ms
   
4. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=4 ttl=119 time=2.63 ms
   
5. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=3 ttl=119 time=1161 ms
   
6. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=5 ttl=119 time=2.59 ms
   
7. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=6 ttl=119 time=50.10 ms
   
8. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=7 ttl=119 time=2.41 ms
   
9. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=8 ttl=119 time=2.34 ms
   
10. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=9 ttl=119 time=2.42 ms
    
11. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=10 ttl=119 time=2.45 ms
    
12. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=11 ttl=119 time=2.30 ms
    
13. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=12 ttl=119 time=2.33 ms
    
14. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=14 ttl=119 time=68.1 ms
    
15. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=15 ttl=119 time=2.30 ms
    
16. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=16 ttl=119 time=3.36 ms
    
17. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=17 ttl=119 time=3.10 ms
    
18. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=18 ttl=119 time=2.42 ms
    
19. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=19 ttl=119 time=2.41 ms
    
20. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=21 ttl=119 time=3.42 ms
    
21. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=20 ttl=119 time=1068 ms
    
22. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=22 ttl=119 time=2.60 ms
    
23. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=23 ttl=119 time=4.02 ms
    
24. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=24 ttl=119 time=2.37 ms
    
25. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=25 ttl=119 time=3.10 ms
    
26. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=26 ttl=119 time=2.32 ms
    
27. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=27 ttl=119 time=2.22 ms
    
28. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=28 ttl=119 time=2.55 ms
    
29. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=29 ttl=119 time=4.17 ms
    
30. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=30 ttl=119 time=979 ms
    
31. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=31 ttl=119 time=2.37 ms
    
32. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=32 ttl=119 time=901 ms
    
33. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=33 ttl=119 time=758 ms
    
34. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=34 ttl=119 time=2.32 ms
    
35. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=35 ttl=119 time=769 ms
    
36. 64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=36 ttl=119 time=2.27 ms
    
37. ^C
    
38. --- google.com ping statistics ---
    
39. 37 packets transmitted, 35 received, 5.40541% packet loss, time 953ms
    
40. rtt min/avg/max/mdev = 2.221/242.922/1347.394/445.929 ms, pipe 2

复制代码

Jaywxl

网络确实得套cf，盘大性能可以，借楼出个27.5，见帖子

igoogle

QTOP 发表于 2025-3-25 07:06
30o还凑活用，18、19欧的还是放弃吧

我还有个12O的网络没问题，19O的这个太离谱了。。

larry

9o没问题,0丢包. 说明不是网络拉胯, 是你的邻居作妖.

acg88

宁静致远 发表于 2025-3-25 08:54
它真抗吗？有卢森堡那么猛？

我从卢森堡换到naranja的

宁静致远

acg88 发表于 2025-3-25 04:20
不是，你们拿这种鸡来生产？我们是为了抗dmca，还得套CF，你直接就用？

它真抗吗？有卢森堡那么猛？

shinzi

的确够拉胯的，这网络丢包率高的不行

QTOP

30o还凑活用，18、19欧的还是放弃吧

acg88

不是，你们拿这种鸡来生产？我们是为了抗dmca，还得套CF，你直接就用？

igoogle

hkbbdx 发表于 2025-3-24 21:52
前阵子老是有人在出，有玄机，国外那个论坛有在说网络异常

知道拉跨，不知道这么拉跨。。