On chrome i get this:
So you not alone 
6 Likes
This might have something to do with it…
5 Likes
Seems to be affecting all the Steam embeds on the forum.
2 Likes
For anyone that uses Teams, have you noted that you cannot screen share and share your camera together when using the web platform?
Not sure if there is a workaround for this as this is a serious issue for me.
1 Like
Nope sorry. Don’t think I’ve seen that before. What does it say if you hover your mouse over it or right click on it?
2 Likes
You don’t have an app alerts active anywhere?
2 Likes
It’s the Android Data Saver indicator.
It’s the top recommended data saving setting here:
3 Likes
Dankie!!
2 Likes
Holy cow, that’s on the phone? Man I’m an idiot. My brain automatically thought it’s the bottom right bar on a laptop.
4 Likes
Sorry my bad, I thought I said so on the post but my tired brain isn’t keeping up
2 Likes
If anyone else is losing their minds with people’s PCs crashing when trying to print:
https://support.microsoft.com/en-us/topic/march-15-2021-kb5001567-os-builds-19041-868-and-19042-868-out-of-band-6e0844a2-7551-4b2d-9c4b-4274a5949bf3
3 Likes
Good riddance
1 Like
My N+ is 25 years out of date and I am having issues with my ISP and they are bullshitting me with comments like “we will tweak your frequencies to see if it improves”. Hopefully someone here can shed more light on it. Some background: the only way to get internet is to pay a local company to bounce it to the closest fibre able town via radio towers. Here is a tracert that shows the route it walks:
All the IP addresses that start with 10. are the towers bouncing it on, when it hits 160. then that is the router to international. Things start falling apart from there. They also say it is their backend provider that is causing this. This happens roughly every 5 minutes and lasts 30 seconds then goes back to the packet loss free route I want.
I have complained and nothing has happened, what do you think I can tell them to get them going on it?
3 Likes
That IP (160.119.222.125) belongs to Saint ICT (saint.co.za).
So the “backend provider” appears to be Saint, who then uses Seacom as its upstream provider (105.23.234.1).
There is no packet loss until it hits that Saint router, so the problem appears to be on that link between 10.5.1.1 and 160.119.222.125.
It won’t help if they “tweak your frequencies” because the problem isn’t between you and your closest relay, but on your ISP’s link with the Saint router.
That’s what it looks like to me, anyway.
4 Likes
yea changing frequencies whatever they mean by that wont do anything this looks like an IP table routing issue. The fact that its such a massive spike is very odd
5 Likes
They probably just don’t care enough to pick up the phone to make a call…
2 Likes
Or the 1st line tech is just reading off a script and not getting someone involved who can actually fix the issue
3 Likes
Threatened them with termination of service, there is one other provider in the area that will take over my installation. Going to give them the day to see if they fix it, if not, I have to pay R1k to change over to the other provider, which I will gladly do.
2 Likes
I just really hope you don’t pay the R1k to go from bad to just as bad, as has been my experiences with all of the WISPs in my area.
1 Like