• igoogle

    收了mjj一个19o的naranja,发现网络太拉垮了。。
    本来只是用来做反代,但是发现连后端DE和NL的服务器,都有20%的丢包,
    ping Google都有5%的丢包,而且网络波动很大。。。
    发ticket要求换到其它母鸡,都不理会 [vip]PING google.com(ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e)) 56 data bytes
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=1 ttl=119 time=1347 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=2 ttl=119 time=1334 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=4 ttl=119 time=2.63 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=3 ttl=119 time=1161 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=5 ttl=119 time=2.59 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=6 ttl=119 time=50.10 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=7 ttl=119 time=2.41 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=8 ttl=119 time=2.34 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=9 ttl=119 time=2.42 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=10 ttl=119 time=2.45 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=11 ttl=119 time=2.30 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=12 ttl=119 time=2.33 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=14 ttl=119 time=68.1 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=15 ttl=119 time=2.30 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=16 ttl=119 time=3.36 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=17 ttl=119 time=3.10 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=18 ttl=119 time=2.42 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=19 ttl=119 time=2.41 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=21 ttl=119 time=3.42 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=20 ttl=119 time=1068 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=22 ttl=119 time=2.60 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=23 ttl=119 time=4.02 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=24 ttl=119 time=2.37 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=25 ttl=119 time=3.10 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=26 ttl=119 time=2.32 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=27 ttl=119 time=2.22 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=28 ttl=119 time=2.55 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=29 ttl=119 time=4.17 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=30 ttl=119 time=979 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=31 ttl=119 time=2.37 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=32 ttl=119 time=901 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=33 ttl=119 time=758 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=34 ttl=119 time=2.32 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=35 ttl=119 time=769 ms
    64 bytes from ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=36 ttl=119 time=2.27 ms
    ^C
    --- google.com ping statistics ---
    37 packets transmitted, 35 received, 5.40541% packet loss, time 953ms
    rtt min/avg/max/mdev = 2.221/242.922/1347.394/445.929 ms, pipe 2[/vip]

    主楼
  • 江湖骗子

    ipv4呢

    #1
  • igoogle

    江湖骗子 发表于 2025-3-24 21:46
    ipv4呢
    一样,丢包甚至比v6更厉害

    #2
  • hkbbdx

    前阵子老是有人在出,有玄机,国外那个论坛有在说网络异常

    #3
  • igoogle

    hkbbdx 发表于 2025-3-24 21:52
    前阵子老是有人在出,有玄机,国外那个论坛有在说网络异常
    知道拉跨,不知道这么拉跨。。

    #4
  • acg88

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

    #5
  • QTOP

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

    #6
  • shinzi

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

    #7
  • 宁静致远

    acg88 发表于 2025-3-25 04:20
    不是,你们拿这种鸡来生产?我们是为了抗dmca,还得套CF,你直接就用?
    它真抗吗?有卢森堡那么猛?

    #8
  • acg88larry

    宁静致远 发表于 2025-3-25 08:54
    它真抗吗?有卢森堡那么猛?
    我从卢森堡换到naranja的9o没问题,0丢包. 说明不是网络拉胯, 是你的邻居作妖.

    #9

发表回复

登录后回复