My ping is stable for the past few hours in games at least. On discord its really bad, ~200 ms in voice, lagging voice comms etc. Cant seem to load 1080p vids either on twitch/youtube.
Feedback for Ogero
Same here. I'm in the same area connected to Sakiet al jenzir central, not Hamra central.dio wroteIs it just me or has the Fiber in the Hamra area been iffy the past day or two? Lots of Packet Loss, few disconnects.
Google DNS (IPv4):
Google DNS (IPv6):PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=251 time=52.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=251 time=40.9 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=251 time=46.8 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=251 time=41.4 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=251 time=56.9 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=251 time=41.1 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=251 time=41.2 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=251 time=41.6 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=251 time=40.3 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=251 time=40.1 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=251 time=40.9 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=251 time=43.7 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=251 time=40.2 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=251 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=251 time=41.4 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=251 time=41.0 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=251 time=54.9 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=251 time=41.4 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=251 time=40.2 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=251 time=41.2 ms
--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19025ms
rtt min/avg/max/mdev = 40.112/43.450/56.895/4.975 ms
Cloudflare DNS (IPv6):PING 2001:4860:4860::8888 (2001:4860:4860::8888) 56 data bytes
64 bytes from 2001:4860:4860::8888: icmp_seq=1 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=2 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=3 ttl=111 time=171 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=4 ttl=111 time=171 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=5 ttl=111 time=171 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=6 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=7 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=8 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=9 ttl=111 time=171 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=10 ttl=111 time=171 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=11 ttl=111 time=171 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=12 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=13 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=14 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=15 ttl=111 time=171 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=16 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=17 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=18 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=19 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=20 ttl=111 time=171 ms
--- 2001:4860:4860::8888 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19002ms
rtt min/avg/max/mdev = 171.089/171.520/171.988/0.210 ms
google.com (IPv6):PING 2606:4700:4700::1111 (2606:4700:4700::1111) 56 data bytes
64 bytes from 2606:4700:4700::1111: icmp_seq=1 ttl=54 time=42.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=2 ttl=54 time=42.5 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=3 ttl=54 time=42.1 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=4 ttl=54 time=41.0 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=5 ttl=54 time=41.2 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=6 ttl=54 time=40.2 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=7 ttl=54 time=40.5 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=8 ttl=54 time=41.7 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=9 ttl=54 time=40.2 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=10 ttl=54 time=47.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=11 ttl=54 time=44.6 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=12 ttl=54 time=42.7 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=13 ttl=54 time=40.3 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=14 ttl=54 time=41.0 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=15 ttl=54 time=41.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=16 ttl=54 time=43.2 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=17 ttl=54 time=41.0 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=18 ttl=54 time=41.1 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=19 ttl=54 time=41.6 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=20 ttl=54 time=41.1 ms
--- 2606:4700:4700::1111 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19022ms
rtt min/avg/max/mdev = 40.202/41.955/47.906/1.752 ms
Seems much better now. Trying later in the day.PING google.com (2a00:1450:4006:80d::200e) 56 data bytes
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=1 ttl=113 time=43.5 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=2 ttl=113 time=41.8 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=3 ttl=113 time=42.1 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=4 ttl=113 time=41.9 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=5 ttl=113 time=42.3 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=7 ttl=113 time=42.6 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=8 ttl=113 time=41.9 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=9 ttl=113 time=42.2 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=10 ttl=113 time=42.0 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=11 ttl=113 time=42.0 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=12 ttl=113 time=42.0 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=13 ttl=113 time=42.0 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=14 ttl=113 time=41.9 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=15 ttl=113 time=44.1 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=16 ttl=113 time=41.8 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=17 ttl=113 time=43.7 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=18 ttl=113 time=42.1 ms
64 bytes from mrs08s18-in-x0e.1e100.net (2a00:1450:4006:80d::200e): icmp_seq=19 ttl=113 time=43.4 ms
--- google.com ping statistics ---
20 packets transmitted, 18 received, 10% packet loss, time 19042ms
rtt min/avg/max/mdev = 41.811/42.398/44.093/0.714 ms
Try again towards the evening on the weekend. (7 pm - 11pm) that's when it gets really bad
- Edited
~7:55PM.
Google DNS (IPv4):
Google DNS (IPv4):
Google DNS (IPv6):PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=251 time=70.3 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=251 time=72.9 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=251 time=71.0 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=251 time=76.1 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=251 time=71.5 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=251 time=68.8 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=251 time=72.4 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=251 time=72.7 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=251 time=71.4 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=251 time=73.9 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=251 time=74.6 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=251 time=75.8 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=251 time=73.8 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=251 time=70.7 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=251 time=73.4 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=251 time=80.7 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=251 time=83.8 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=251 time=76.0 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=251 time=73.3 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=251 time=79.2 ms
--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19027ms
rtt min/avg/max/mdev = 68.771/74.114/83.823/3.613 ms
Cloudflare DNS (IPv6):PING 2001:4860:4860::8888 (2001:4860:4860::8888) 56 data bytes
64 bytes from 2001:4860:4860::8888: icmp_seq=1 ttl=114 time=68.5 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=2 ttl=114 time=67.9 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=3 ttl=114 time=67.0 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=4 ttl=114 time=68.8 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=5 ttl=114 time=68.3 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=6 ttl=114 time=67.4 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=7 ttl=114 time=67.8 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=8 ttl=114 time=68.3 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=10 ttl=114 time=67.9 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=11 ttl=114 time=68.7 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=12 ttl=114 time=68.2 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=13 ttl=114 time=68.0 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=14 ttl=114 time=68.4 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=15 ttl=114 time=66.9 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=16 ttl=114 time=67.1 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=17 ttl=114 time=68.2 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=18 ttl=114 time=68.3 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=20 ttl=114 time=68.4 ms
--- 2001:4860:4860::8888 ping statistics ---
20 packets transmitted, 18 received, 10% packet loss, time 19057ms
rtt min/avg/max/mdev = 66.910/68.000/68.779/0.552 ms
google.com (IPv6):PING 2606:4700:4700::1111 (2606:4700:4700::1111) 56 data bytes
64 bytes from 2606:4700:4700::1111: icmp_seq=1 ttl=51 time=95.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=2 ttl=51 time=89.8 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=3 ttl=51 time=93.2 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=4 ttl=51 time=94.5 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=5 ttl=51 time=95.0 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=6 ttl=51 time=93.8 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=7 ttl=51 time=93.0 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=8 ttl=51 time=89.8 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=9 ttl=51 time=90.7 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=10 ttl=51 time=88.7 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=11 ttl=51 time=93.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=12 ttl=51 time=87.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=13 ttl=51 time=94.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=14 ttl=51 time=92.3 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=15 ttl=51 time=95.5 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=16 ttl=51 time=89.2 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=17 ttl=51 time=90.8 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=18 ttl=51 time=92.0 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=19 ttl=51 time=92.3 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=20 ttl=51 time=86.1 ms
--- 2606:4700:4700::1111 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19026ms
rtt min/avg/max/mdev = 86.118/91.955/95.879/2.671 ms
Lots of delays when browsing around though, probably due to packet loss.PING google.com (2a00:1450:4006:800::200e) 56 data bytes
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=1 ttl=113 time=68.2 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=2 ttl=113 time=68.6 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=3 ttl=113 time=69.0 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=4 ttl=113 time=68.4 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=5 ttl=113 time=68.0 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=6 ttl=113 time=68.9 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=7 ttl=113 time=68.9 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=8 ttl=113 time=67.8 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=9 ttl=113 time=68.7 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=10 ttl=113 time=68.6 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=11 ttl=113 time=69.2 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=12 ttl=113 time=68.6 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=13 ttl=113 time=68.6 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=14 ttl=113 time=67.5 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=15 ttl=113 time=69.1 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=16 ttl=113 time=69.0 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=17 ttl=113 time=69.1 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=18 ttl=113 time=69.0 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=19 ttl=113 time=68.9 ms
--- google.com ping statistics ---
20 packets transmitted, 19 received, 5% packet loss, time 19008ms
rtt min/avg/max/mdev = 67.548/68.639/69.221/0.453 ms
- Edited
It was fine most of the day. But got really bad around 10 pm. ~405 ms on discord and super lag spikes in games. I hope theyre aware of this.
Edit: it just fixed itself around 11 pm. Everything went back to normal,. i dont know why or how, or for how long.
Edit: it just fixed itself around 11 pm. Everything went back to normal,. i dont know why or how, or for how long.
Same issue with me for the past 4 days. Ping to 8.8.8.8 with 250ms and online gaming is impossible.
Exact same for me. It starts around 7-8 PM. Spoke to Ogero, they asked me to run some tests, they said "and the latency issue is due to high latency outside Lebanon, and it is being escalated with the international peer"
HzSamer wroteThis is now, browsing sometimes very slow, and suddenly go back to normal speed. Also, download speed ranging from 40KB/s then go back to 35MB/s.
Today morning/afternoon the situation was way better.
https://i.ibb.co/zr3ZDpn/Screenshot-2024-02-05-210332.png
Can confirm amd hate to say it for the first time in years Ogero's service is shit. Dsl, LTe and fiber all are shit and they havent acknowleged anything is wrong...
I dont think it's their fault to be honest. It seems to be an outside issue that's affecting latency/packet loss.DNA wroteCan confirm amd hate to say it for the first time in years Ogero's service is shit. Dsl, LTe and fiber all are shit and they havent acknowleged anything is wrong...
9 days later
- Edited
No IPv6 connectivity now. Grr...
EDIT: Turns out it was an issue on my end. Fixed.
EDIT: Turns out it was an issue on my end. Fixed.
How can I setup IPv6 on my tplink router? I configured it myself a while back, now Ogero is configuring them with IPv6 directly. Can I do it myself or it requires some credentials from them?yasamoka wroteNo IPv6 connectivity now. Grr...
is ipv6 only for fiber accounts? because i do not have it on my vdsl
Feel free to contact me by PM, both of you, and I'll try and help you set up IPv6 on your network.
7 days later
Same story as 2 weeks ago, getting packet loss and latency in games. The fuck is going on.
a month later
- Edited
nvm literally just plug your phone into the router..
15 days later
Anyone is noticing speed/delay problems on Fiber? Both download and browsing.
It started yesterday and some websites isn't opening without a VPN.
It started yesterday and some websites isn't opening without a VPN.
on adsl 2+ too, here in Saida, a lot of speed drop, and sudden requested timed out !!! about 6 or 7, then backs to normalHzSamer wroteAnyone is noticing speed/delay problems on Fiber? Both download and browsing.
It started yesterday and some websites isn't opening without a VPN.
yep same thing here on fiberHzSamer wroteAnyone is noticing speed/delay problems on Fiber? Both download and browsing.
It started yesterday and some websites isn't opening without a VPN.