Anyone Noticed That European Links Went Bad?, Latency >400ms (Update Aft 2 Mths Unrsv)
|
|
 May 16 2024, 06:14 PM
Show posts by this member only | IPv6 | Post
#81
|
 
Senior Member
1,030 posts Joined: Jan 2022 
|
QUOTE(rezzorix @ May 16 2024, 05:29 PM) Can you back that statement up with data? Ooops no improvement yet with TIME? Because my constantly running smokeping tells otherwise (at least for TIME).  Most SG major carriers are already getting <220ms to Amsterdam today. It's normalizing now. |
|
|
|
|
|
May 16 2024, 07:01 PM
|
Junior Member
376 posts Joined: May 2019 
|
QUOTE(petpenyubobo @ May 16 2024, 06:14 PM) Ooops no improvement yet with TIME? Most SG major carriers are already getting <220ms to Amsterdam today. It's normalizing now.  On TIME. Edit: Last time i download, was only getting 10kb/s. Now at least 1mb/s This post has been edited by ChenKaiWen: May 16 2024, 07:05 PM |
|
|
May 16 2024, 08:54 PM
|
Junior Member
98 posts Joined: Nov 2021
|
QUOTE(ChenKaiWen @ May 16 2024, 07:01 PM) On TIME. Edit: Last time i download, was only getting 10kb/s. Now at least 1mb/s I would rather take data centres in Marseille, Amsterdam, Frankfurt as reference. |
|
|
May 16 2024, 10:07 PM
Show posts by this member only | IPv6 | Post
#84
|
|
Senior Member
1,030 posts Joined: Jan 2022
|
Server Source:
DataPacket Telecom: https://www.datapacket.com/looking-glass OVH Roubaix Paris: rbx.proof.ovh.net DataPacket Amsterdam  DataPacket Frankfurt  OVH Roubaix Paris  |
|
|
May 16 2024, 10:28 PM
|
|
Junior Member
376 posts Joined: May 2019
|
DataPacket Amsterdam
 DataPacket Frankfurt  DataPacket Paris  OVH Roubaix Paris  For the most parts, I think fixed but some still affected |
|
|
May 16 2024, 11:07 PM
Show posts by this member only | IPv6 | Post
#86
|
|
Junior Member
98 posts Joined: Nov 2021
|
Nothing changed.
I suggest not to just run adhoc pings and judge based on that. Continuous, long-term monitoring of network latency and packet loss are better for analysis. Regular ping commands provide only a snapshot in time. Frankfurt:  Amsterdam:  |
|
|
|
|
|
May 17 2024, 11:14 AM
|
|
Junior Member
376 posts Joined: May 2019
|
QUOTE(rezzorix @ May 16 2024, 11:07 PM) Nothing changed. You're right. A large amount of data would be better than a small amount of data. I've already setup smokeping yesterday.I suggest not to just run adhoc pings and judge based on that. Continuous, long-term monitoring of network latency and packet loss are better for analysis. Regular ping commands provide only a snapshot in time. » Click to show Spoiler - click again to hide... « |
|
|
May 17 2024, 11:32 AM
Show posts by this member only | IPv6 | Post
#88
|
|
Junior Member
120 posts Joined: May 2018
|
Not for me (certain hosts are ok):
CODE @Mareks-MacBook-Pro-M1 ~ % ping elbiaadmin.sk PING elbiaadmin.sk (109.74.156.7): 56 data bytes 64 bytes from 109.74.156.7: icmp_seq=0 ttl=53 time=441.063 ms Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 Request timeout for icmp_seq 5 Request timeout for icmp_seq 6 Request timeout for icmp_seq 7 Request timeout for icmp_seq 8 64 bytes from 109.74.156.7: icmp_seq=9 ttl=53 time=462.775 ms Request timeout for icmp_seq 10 Request timeout for icmp_seq 11 64 bytes from 109.74.156.7: icmp_seq=12 ttl=53 time=529.903 ms 64 bytes from 109.74.156.7: icmp_seq=13 ttl=53 time=428.958 ms Request timeout for icmp_seq 14 64 bytes from 109.74.156.7: icmp_seq=15 ttl=53 time=490.878 ms 64 bytes from 109.74.156.7: icmp_seq=16 ttl=53 time=511.674 ms 64 bytes from 109.74.156.7: icmp_seq=17 ttl=53 time=530.935 ms Request timeout for icmp_seq 18 Request timeout for icmp_seq 19 64 bytes from 109.74.156.7: icmp_seq=20 ttl=53 time=484.982 ms Request timeout for icmp_seq 21 ^C --- elbiaadmin.sk ping statistics --- 23 packets transmitted, 8 packets received, 65.2% packet loss round-trip min/avg/max/stddev = 428.958/485.146/530.935/36.120 ms @Mareks-MacBook-Pro-M1 ~ % ping www.pravda.sk PING kultura.pravda.sk (217.67.31.48): 56 data bytes 64 bytes from 217.67.31.48: icmp_seq=0 ttl=54 time=434.474 ms 64 bytes from 217.67.31.48: icmp_seq=1 ttl=54 time=468.696 ms Request timeout for icmp_seq 2 64 bytes from 217.67.31.48: icmp_seq=3 ttl=54 time=428.379 ms Request timeout for icmp_seq 4 64 bytes from 217.67.31.48: icmp_seq=5 ttl=54 time=488.469 ms Request timeout for icmp_seq 6 64 bytes from 217.67.31.48: icmp_seq=7 ttl=54 time=451.559 ms 64 bytes from 217.67.31.48: icmp_seq=8 ttl=54 time=468.445 ms Request timeout for icmp_seq 9 64 bytes from 217.67.31.48: icmp_seq=10 ttl=54 time=506.781 ms Request timeout for icmp_seq 11 Request timeout for icmp_seq 12 64 bytes from 217.67.31.48: icmp_seq=13 ttl=54 time=468.073 ms 64 bytes from 217.67.31.48: icmp_seq=14 ttl=54 time=488.777 ms Request timeout for icmp_seq 15 64 bytes from 217.67.31.48: icmp_seq=16 ttl=54 time=532.247 ms Request timeout for icmp_seq 17 64 bytes from 217.67.31.48: icmp_seq=18 ttl=54 time=471.417 ms 64 bytes from 217.67.31.48: icmp_seq=19 ttl=54 time=494.049 ms Request timeout for icmp_seq 20 Request timeout for icmp_seq 21 64 bytes from 217.67.31.48: icmp_seq=22 ttl=54 time=555.287 ms 64 bytes from 217.67.31.48: icmp_seq=23 ttl=54 time=471.291 ms Request timeout for icmp_seq 24 Request timeout for icmp_seq 25 Request timeout for icmp_seq 26 64 bytes from 217.67.31.48: icmp_seq=27 ttl=54 time=551.736 ms 64 bytes from 217.67.31.48: icmp_seq=28 ttl=54 time=569.938 ms Request timeout for icmp_seq 29 64 bytes from 217.67.31.48: icmp_seq=30 ttl=54 time=461.410 ms ^C --- kultura.pravda.sk ping statistics --- 31 packets transmitted, 17 packets received, 45.2% packet loss round-trip min/avg/max/stddev = 428.379/488.884/569.938/40.438 ms Mareks-MacBook-Pro-M1 ~ % ping www.telekom.sk PING www.telekom.sk (213.81.204.245): 56 data bytes 64 bytes from 213.81.204.245: icmp_seq=0 ttl=239 time=389.462 ms 64 bytes from 213.81.204.245: icmp_seq=1 ttl=239 time=302.982 ms 64 bytes from 213.81.204.245: icmp_seq=2 ttl=239 time=429.105 ms 64 bytes from 213.81.204.245: icmp_seq=3 ttl=239 time=299.103 ms 64 bytes from 213.81.204.245: icmp_seq=4 ttl=239 time=365.269 ms 64 bytes from 213.81.204.245: icmp_seq=5 ttl=239 time=384.616 ms 64 bytes from 213.81.204.245: icmp_seq=6 ttl=239 time=303.455 ms 64 bytes from 213.81.204.245: icmp_seq=7 ttl=239 time=324.830 ms 64 bytes from 213.81.204.245: icmp_seq=8 ttl=239 time=303.106 ms 64 bytes from 213.81.204.245: icmp_seq=9 ttl=239 time=367.755 ms 64 bytes from 213.81.204.245: icmp_seq=10 ttl=239 time=386.028 ms 64 bytes from 213.81.204.245: icmp_seq=11 ttl=239 time=403.420 ms 64 bytes from 213.81.204.245: icmp_seq=12 ttl=239 time=421.840 ms 64 bytes from 213.81.204.245: icmp_seq=13 ttl=239 time=311.739 ms ^C QUOTE(petpenyubobo @ May 16 2024, 03:38 PM) There's already some improvements observed today and European links are slowly recovering. Almost back to normal. Stay tuned. |
|
|
May 17 2024, 11:35 AM
Show posts by this member only | IPv6 | Post
#89
|
|
Junior Member
98 posts Joined: Nov 2021
|
QUOTE(ChenKaiWen @ May 17 2024, 11:14 AM) I've already setup smokeping yesterday. Awesome! Maybe also worth pinging Go626201 who has a pretty conclusive smokeping setup here: http://smokeping.mywebping.com/smokeping/  Would be cool if he could share his smokeping config in a zip-file or so - he has soo many servers in there, too much work to copy all  |
|
|
May 17 2024, 11:51 AM
Show posts by this member only | IPv6 | Post
#90
|
|
Junior Member
98 posts Joined: Nov 2021
|
QUOTE(xhruso00 @ May 17 2024, 11:32 AM) Not for me (certain hosts are ok) If you would really engage in this forum and also read what other people write, then you would not post this.Just running a ping and then judging the situation based on that wont give you correct results. |
|
|
May 17 2024, 12:03 PM
Show posts by this member only | IPv6 | Post
#91
|
|
Junior Member
120 posts Joined: May 2018
|
I am just trying to understand why my webhosting has enormous packet loss. According to traceroute is because of different routing.
I did the ping last night as well with same results. I understand I need to have continuos results. No need to scold me for this. QUOTE(rezzorix @ May 17 2024, 11:51 AM) If you would really engage in this forum and also read what other people write, then you would not post this. Just running a ping and then judging the situation based on that wont give you correct results. |
|
|
May 17 2024, 12:16 PM
Show posts by this member only | IPv6 | Post
#92
|
|
Junior Member
98 posts Joined: Nov 2021
|
QUOTE(xhruso00 @ May 17 2024, 12:03 PM) No need to scold me for this. My fault, sorry, didn't mean to come over as someone who scolds.  Just a lot people write in different posts across forum that all is good again - while in reality it isnt. A bit frustrating.  |
|
|
May 17 2024, 12:50 PM
|
|
Junior Member
376 posts Joined: May 2019
|
Idk how much this matters but after doing a traceroute to those data center. I've noticed those with lower ping and much stable is routed through TATA(MY -> SG -> IN -> destination) while higher ping is routed through NTT(MY -> SG -> JP -> US -> destination)
|
|
|
|
|
|
May 17 2024, 03:33 PM
|
Senior Member
1,350 posts Joined: Nov 2004 From: HEAVEN & HELL
|
QUOTE(ChenKaiWen @ May 17 2024, 12:50 PM) Idk how much this matters but after doing a traceroute to those data center. I've noticed those with lower ping and much stable is routed through TATA(MY -> SG -> IN -> destination) while higher ping is routed through NTT(MY -> SG -> JP -> US -> destination) is due to longer destination to reach the host so the ping is higher. this is normal.EU normal ping would be 160-190ms US West ping would be 170-190ms US EAST ping would be 220-250ms |
|
|
May 17 2024, 05:37 PM
|
|
Junior Member
120 posts Joined: May 2018
|
Any help why Time optic to EU is much different than Celcom 5G? Time has lousy peering with EU?
  QUOTE(rezzorix @ May 17 2024, 12:16 PM) My fault, sorry, didn't mean to come over as someone who scolds. Just a lot people write in different posts across forum that all is good again - while in reality it isnt. A bit frustrating. |
|
|
May 17 2024, 06:44 PM
|
|
Senior Member
1,350 posts Joined: Nov 2004 From: HEAVEN & HELL
|
QUOTE(xhruso00 @ May 17 2024, 05:37 PM) Any help why Time optic to EU is much different than Celcom 5G? Time has lousy peering with EU? TIME and celcom using different transit provider, you can see the different on traceroute.TIME majority traffic incoming is using NTT which is congested all time right now. |
|
|
May 18 2024, 11:23 AM
|
|
Senior Member
1,266 posts Joined: Oct 2009
|
Anyone know the underseas cable broken by ship anchor at Bangladesh connection related to EU fixed yet?
The online game i play before mid April EU server always 165 -175 ping, recently i try log in still getting 250 and random spike 500-1000 pukimak . |
|
|
May 18 2024, 01:38 PM
Show posts by this member only | IPv6 | Post
#98
|
|
Junior Member
98 posts Joined: Nov 2021
|
QUOTE(zuozi @ May 18 2024, 11:23 AM) Anyone know the underseas cable broken by ship anchor at Bangladesh connection related to EU fixed yet? This is what happened:The online game i play before mid April EU server always 165 -175 ping, recently i try log in still getting 250 and random spike 500-1000 pukimak . 1) AAE-1 - 24. Feb 2024: There was a terrorist attack on a boat near Yemen. As a result the boats anchor then cut the cable. 2) SEA-ME-WE 5 - 17.-19. Apr2024: There were maintenance works going on 440km off the coast of Singapore after that salt water penetrated the cable causing an outage. Repair of 2) was estimated to take 2..3 weeks so people are expecting the links again up and better working from around now onwards; however it will take some more time... Since we are already waiting so long.. add another one or two weeks... who cares   |
|
|
May 18 2024, 01:44 PM
|
|
Senior Member
1,266 posts Joined: Oct 2009
|
QUOTE(rezzorix @ May 18 2024, 01:38 PM) This is what happened: Waa so details thanks 😂1) AAE-1 - 24. Feb 2024: There was a terrorist attack on a boat near Yemen. As a result the boats anchor then cut the cable. 2) SEA-ME-WE 5 - 17.-19. Apr2024: There were maintenance works going on 440km off the coast of Singapore after that salt water penetrated the cable causing an outage. Repair of 2) was estimated to take 2..3 weeks so people are expecting the links again up and better working from around now onwards; however it will take some more time... Since we are already waiting so long.. add another one or two weeks... who cares |
|
|
May 19 2024, 04:14 PM
Show posts by this member only | IPv6 | Post
#100
|
|
Senior Member
1,882 posts Joined: Sep 2017
|
QUOTE(rezzorix @ May 17 2024, 11:35 AM) Awesome! Feel free to utilize the Target File.Maybe also worth pinging Go626201 who has a pretty conclusive smokeping setup here: http://smokeping.mywebping.com/smokeping/ Would be cool if he could share his smokeping config in a zip-file or so - he has soo many servers in there, too much work to copy all https://1fichier.com/?stwfro58yre9rk3jxxbw rezzorix liked this post
|
|
Topic ClosedOptions
|
| Change to: |  0.0238sec
 0.65
 5 queries
 GZIP Disabled
Time is now: 10th December 2025 - 08:18 PM |
Quote
