LebGeeks

bigricenergy

Member

Re: Feedback for Ogero

Does anyone know what does the vdsl feasibility test consists of and why does it take so long to be done? What exactly do they test?

wollyka

Member

Re: Feedback for Ogero

They check the distance between your phone/house to the centrale and monitor the line stats (like SNR, etc..) over a few days.

Last edited by wollyka (January 13)

bigricenergy

Member

Re: Feedback for Ogero

They check the distance between your phone/house to the centrale and monitor the line stats (like SNR, etc..) over a few days.

Because few years ago it took them more than 4 months to tell me that it is feasible and in the end they called me from the central to tell me that all vdsl ports are full. I reapplied last week at the centrale and again they will be doing the test which should take 10-15 days.

wollyka

Member

Re: Feedback for Ogero

Because the stats might change. For example, I have VDSL and I used to get 28 Mbps, now I am lucky if  i can get 20 Mbps! They told me that the cabinet in the street is affected by EMI but they can't do anything about it. If I wanted to apply  to VDSL now, I won't be eligible

bigricenergy

Member

Re: Feedback for Ogero

Yep noticed that also, my max rate used to be around 20 21Mbps, now barely 16Mbps

bigricenergy

Member

Re: Feedback for Ogero

Anyone knows someone I can contact directly to get an answer or update about the vdsl feasibility? Been waiting for over 20 days calling the centrale everyday and they still don't have an answer

Space

Member

Re: Feedback for Ogero

Anyone knows someone I can contact directly to get an answer or update about the vdsl feasibility? Been waiting for over 20 days calling the centrale everyday and they still don't have an answer

Contact them on twitter.

bigricenergy

Member

Re: Feedback for Ogero

Anyone knows someone I can contact directly to get an answer or update about the vdsl feasibility? Been waiting for over 20 days calling the centrale everyday and they still don't have an answer

Contact them on twitter.

They don’t know

HzSamer

Member

Re: Feedback for Ogero

Anyone knows someone I can contact directly to get an answer or update about the vdsl feasibility? Been waiting for over 20 days calling the centrale everyday and they still don't have an answer

Go to the central and reach to the manager of the central there and talk to him directly. He must help you. When I had VDSL in the past they didn't switch my ports to VDSL until I talked the the manager in person and he sent a request immediately with my landline number.

dio

Member

Re: Feedback for Ogero

Is it just me or has the Fiber in the Hamra area been iffy the past day or two? Lots of Packet Loss, few disconnects.

yasamoka

Member

Re: Feedback for Ogero

Is it just me or has the Fiber in the Hamra area been iffy the past day or two? Lots of Packet Loss, few disconnects.

Same here. It's driving me nuts.

Ahmad_k

Member

Re: Feedback for Ogero

I think there is a problem with OGERO DNS, I got a lot of frustration because of it. Try to use google dns or cloudflare dns, you will have better connection. Still not great but it solves a lot of of problems.

I have contacted ogero about their dns issue but still no reply from them. Online gaming is impossible with this issue striking every minute

dio

Member

Re: Feedback for Ogero

I think there is a problem with OGERO DNS, I got a lot of frustration because of it. Try to use google dns or cloudflare dns, you will have better connection. Still not great but it solves a lot of of problems.

I have contacted ogero about their dns issue but still no reply from them. Online gaming is impossible with this issue striking every minute

I already use Google DNS. Still quite annoying with the constant packet loss. Gaming is stable for a while, then it just starts spiking. I dunno whats going on.

dio

Member

Re: Feedback for Ogero

Here is the current ping to google.com via CMD.

Reply from 172.217.18.238: bytes=32 time=151ms TTL=252
Reply from 172.217.18.238: bytes=32 time=166ms TTL=252
Reply from 172.217.18.238: bytes=32 time=155ms TTL=252
Reply from 172.217.18.238: bytes=32 time=144ms TTL=252
Reply from 172.217.18.238: bytes=32 time=156ms TTL=252
Reply from 172.217.18.238: bytes=32 time=157ms TTL=252
Reply from 172.217.18.238: bytes=32 time=147ms TTL=252
Reply from 172.217.18.238: bytes=32 time=147ms TTL=252
Reply from 172.217.18.238: bytes=32 time=141ms TTL=252
Reply from 172.217.18.238: bytes=32 time=154ms TTL=252
Reply from 172.217.18.238: bytes=32 time=154ms TTL=252
Request timed out.
Reply from 172.217.18.238: bytes=32 time=149ms TTL=252
Request timed out.
Reply from 172.217.18.238: bytes=32 time=150ms TTL=252
Reply from 172.217.18.238: bytes=32 time=141ms TTL=252
Reply from 172.217.18.238: bytes=32 time=138ms TTL=252
Reply from 172.217.18.238: bytes=32 time=147ms TTL=252
Reply from 172.217.18.238: bytes=32 time=150ms TTL=252
Reply from 172.217.18.238: bytes=32 time=150ms TTL=252
Reply from 172.217.18.238: bytes=32 time=151ms TTL=252

yasamoka

Member

Re: Feedback for Ogero

Google DNS (IPv4):

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=3 ttl=251 time=157 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=251 time=155 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=251 time=162 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=251 time=159 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=251 time=145 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=251 time=152 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=251 time=153 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=251 time=149 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=251 time=154 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=251 time=146 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=251 time=156 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=251 time=151 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=251 time=152 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=251 time=146 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=251 time=148 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=251 time=151 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=251 time=157 ms
64 bytes from 8.8.8.8: icmp_seq=27 ttl=251 time=150 ms
64 bytes from 8.8.8.8: icmp_seq=32 ttl=251 time=148 ms
64 bytes from 8.8.8.8: icmp_seq=33 ttl=251 time=154 ms
64 bytes from 8.8.8.8: icmp_seq=34 ttl=251 time=158 ms
64 bytes from 8.8.8.8: icmp_seq=36 ttl=251 time=156 ms
64 bytes from 8.8.8.8: icmp_seq=37 ttl=251 time=146 ms
^C
--- 8.8.8.8 ping statistics ---
37 packets transmitted, 23 received, 37.8378% packet loss, time 36224ms
rtt min/avg/max/mdev = 144.534/152.271/161.803/4.646 ms

Google 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=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=4 ttl=111 time=172 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=5 ttl=111 time=172 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=171 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=172 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=171 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=14 ttl=111 time=171 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=15 ttl=111 time=172 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=171 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=20 ttl=111 time=172 ms
^C
--- 2001:4860:4860::8888 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19023ms
rtt min/avg/max/mdev = 170.521/171.708/172.430/0.427 ms

Cloudflare DNS (IPv6):

PING 2606:4700:4700::1111 (2606:4700:4700::1111) 56 data bytes
64 bytes from 2606:4700:4700::1111: icmp_seq=2 ttl=54 time=150 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=4 ttl=54 time=41.1 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=5 ttl=54 time=40.3 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=6 ttl=54 time=40.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=7 ttl=54 time=40.4 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=8 ttl=54 time=41.4 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=10 ttl=54 time=40.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=11 ttl=54 time=41.3 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=12 ttl=54 time=41.4 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=13 ttl=54 time=154 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=14 ttl=54 time=156 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=15 ttl=54 time=41.2 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=16 ttl=54 time=50.2 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=17 ttl=54 time=148 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=18 ttl=54 time=147 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=19 ttl=54 time=40.6 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=20 ttl=54 time=40.7 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=21 ttl=54 time=41.1 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=22 ttl=54 time=41.3 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=23 ttl=54 time=40.5 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=24 ttl=54 time=40.8 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=25 ttl=54 time=162 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=26 ttl=54 time=41.0 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=27 ttl=54 time=152 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=28 ttl=54 time=41.0 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=29 ttl=54 time=41.3 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=30 ttl=54 time=156 ms

--- 2606:4700:4700::1111 ping statistics ---
30 packets transmitted, 27 received, 10% packet loss, time 29090ms
rtt min/avg/max/mdev = 40.310/74.525/162.337/51.085 ms

Cloudflare DNS (IPv6) traceroute 1:

traceroute to 2606:4700:4700::1111 (2606:4700:4700::1111), 30 hops max, 80 byte packets
1  2a00:6920:e10b:27c::1 (2a00:6920:e10b:27c::1)  0.966 ms  0.994 ms  1.059 ms
2  2a00:6920:e12b:3393::1 (2a00:6920:e12b:3393::1)  2.403 ms  2.361 ms  2.412 ms
3  2a00:6920:e1a7::16 (2a00:6920:e1a7::16)  3.843 ms  4.031 ms  4.138 ms
4  fc11::6 (fc11::6)  3.958 ms  4.612 ms  4.573 ms
5  * * *
6  * 2400:cb00:577:1024::ac47:b90e (2400:cb00:577:1024::ac47:b90e)  153.169 ms *

Cloudflare DNS (IPv6) traceroute 2:

traceroute to 2606:4700:4700::1111 (2606:4700:4700::1111), 30 hops max, 80 byte packets
1  2a00:6920:e10b:27c::1 (2a00:6920:e10b:27c::1)  1.047 ms  1.098 ms  1.197 ms
2  2a00:6920:e12b:3393::1 (2a00:6920:e12b:3393::1)  2.412 ms  2.494 ms  2.378 ms
3  2a00:6920:e1a7::16 (2a00:6920:e1a7::16)  4.035 ms  4.118 ms  4.103 ms
4  fc11::6 (fc11::6)  4.395 ms  4.467 ms  4.452 ms
5  2400:cb00:49:1024::a29e:155c (2400:cb00:49:1024::a29e:155c)  42.793 ms 2400:cb00:49:1024::a29e:15a8 (2400:cb00:49:1024::a29e:15a8)  42.778 ms 2400:cb00:49:1024::a29e:155c (2400:cb00:49:1024::a29e:155c)  42.671 ms

Done in direct succession. Using different routes.

google.com (IPv6):

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=41.5 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=2 ttl=113 time=41.4 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=3 ttl=113 time=40.2 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=4 ttl=113 time=41.9 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=5 ttl=113 time=41.0 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=6 ttl=113 time=41.7 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=7 ttl=113 time=41.2 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=8 ttl=113 time=41.0 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=9 ttl=113 time=41.3 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=10 ttl=113 time=41.1 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=11 ttl=113 time=41.0 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=12 ttl=113 time=41.4 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=13 ttl=113 time=41.0 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=14 ttl=113 time=40.9 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=15 ttl=113 time=41.2 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=16 ttl=113 time=41.0 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=17 ttl=113 time=40.6 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=18 ttl=113 time=40.9 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=19 ttl=113 time=40.7 ms
64 bytes from mrs08s21-in-x0e.1e100.net (2a00:1450:4006:800::200e): icmp_seq=20 ttl=113 time=40.5 ms
^C
--- google.com ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19024ms
rtt min/avg/max/mdev = 40.221/41.063/41.885/0.380 ms

What is going on..

Last edited by yasamoka (February 3)

GeorgeN

Member

Re: Feedback for Ogero

It's not just Ogero, Cyberia as well and i'm guessing IDM, very high ping and very slow download speeds.

Last edited by GeorgeN (February 3)

dio

Member

Re: Feedback for Ogero

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.

HzSamer

Member

Re: Feedback for Ogero

Is it just me or has the Fiber in the Hamra area been iffy the past day or two? Lots of Packet Loss, few disconnects.

Same here. I'm in the same area connected to Sakiet al jenzir central, not Hamra central.

yasamoka

Member

Re: Feedback for Ogero

Google DNS (IPv4):

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

Google 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

Cloudflare DNS (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

google.com (IPv6):

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

Seems much better now. Trying later in the day.

GeorgeN

Member

Re: Feedback for Ogero

Try again towards the evening on the weekend. (7 pm - 11pm) that's when it gets really bad

yasamoka

Member

Re: Feedback for Ogero

~7:55PM.

Google DNS (IPv4):

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

Google 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

Cloudflare DNS (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

google.com (IPv6):

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

Lots of delays when browsing around though, probably due to packet loss.

Last edited by yasamoka (February 4)

dio

Member

Re: Feedback for Ogero

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.

Last edited by dio (February 4)

bobo619

Member

Re: Feedback for Ogero

Same issue with me for the past 4 days. Ping to 8.8.8.8 with 250ms and online gaming is impossible.

HzSamer

Member

Re: Feedback for Ogero

This 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.

dio

Member

Re: Feedback for Ogero

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"

This 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