![]() ![]() ![]() ![]() |
|
Please support Geekzone by subscribing, or using one of our referral links: Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync | Backblaze backup
Sideface
VodafoneDylan: ... Work will continue over the next week to upgrade all the busy nodes. ...
Sideface
Sideface:VodafoneDylan: ... Work will continue over the next week to upgrade all the busy nodes. ...
Will there be any work over the weekend?
vortexnz: Cable connection in Woodridge seems to be struggling in the past few weeks.... but tonight seems to be hitting all time lows in the low single digits both ways (on 100/10) fairly consistently in peak times. Obviously better than some however would hate to be overlooked by the big V 'cause I didn't complain enough!
vortexnz: Cable connection in Woodridge seems to be struggling in the past few weeks.... but tonight seems to be hitting all time lows in the low single digits both ways (on 100/10) fairly consistently in peak times. Obviously better than some however would hate to be overlooked by the big V 'cause I didn't complain enough!
Meaning holding SSH and IRC connections a pipe-dream!
Im getting VERY sick of Vodafone not taking the responsibility here and wanting me to do the same old isolation tests, then never getting back to me
Beaker: ... I have been having issues with cable for 4-5 months. ....
I am on the same complaint scale or do I have a different issue than everyone else?
Sideface
Beaker: New to the Rant Here!
I have been having issues with cable for 4-5 months.
Has anyone noticed the sporadic packet-loss and latency? run a continuous ping to 8.8.8.8 and occationally get 3-4s of dropped packets, or occasionally a 200ms+ ping? Meaning holding SSH and IRC connections a pipe-dream! Im getting VERY sick of Vodafone not taking the responsibility here and wanting me to do the same old isolation tests, then never getting back to me
Reply from 8.8.8.8: bytes=32 time=46ms TTL=54
Reply from 8.8.8.8: bytes=32 time=45ms TTL=54
Reply from 8.8.8.8: bytes=32 time=48ms TTL=54
Reply from 8.8.8.8: bytes=32 time=46ms TTL=54
Reply from 121.73.217.87: Destination host unreachable.
Reply from 8.8.8.8: bytes=32 time=2058ms TTL=54
Reply from 8.8.8.8: bytes=32 time=45ms TTL=54
Reply from 8.8.8.8: bytes=32 time=48ms TTL=54
Reply from 8.8.8.8: bytes=32 time=49ms TTL=54
Reply from 8.8.8.8: bytes=32 time=50ms TTL=54
Reply from 8.8.8.8: bytes=32 time=45ms TTL=54
Reply from 8.8.8.8: bytes=32 time=46ms TTL=54
Reply from 121.73.217.87: Destination host unreachable.
Reply from 121.73.217.87: Destination host unreachable.
Reply from 121.73.217.87: Destination host unreachable.
Reply from 121.73.217.87: Destination host unreachable.
Reply from 121.73.217.87: Destination host unreachable.
Reply from 121.73.217.87: Destination host unreachable.
Reply from 8.8.8.8: bytes=32 time=57ms TTL=54
Reply from 8.8.8.8: bytes=32 time=46ms TTL=54
Reply from 8.8.8.8: bytes=32 time=45ms TTL=54
Reply from 8.8.8.8: bytes=32 time=49ms TTL=54
Reply from 8.8.8.8: bytes=32 time=47ms TTL=54
Same Goes with their own DNS server
Reply from 203.96.152.4: bytes=32 time=23ms TTL=58
Reply from 203.96.152.4: bytes=32 time=19ms TTL=58
Reply from 203.96.152.4: bytes=32 time=14ms TTL=58
Reply from 121.73.217.87: Destination host unreachable.
Reply from 121.73.217.87: Destination host unreachable.
Reply from 203.96.152.4: bytes=32 time=26ms TTL=58
Reply from 203.96.152.4: bytes=32 time=15ms TTL=58
I am on the same complaint scale or do I have a different issue than everyone else?
Scotty1986: Once again tonight, speeds are maxed but performance is not so good. I'm going to be pevved if this is what I can expect from now on. Everything was fine 1-2 weeks ago.
|
![]() ![]() ![]() ![]() |