Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Teams outage causes connection issues, message delays

bleepingcomputer.com

Post reply on HN
Print view View original

61–70 of 128 posts

Re: Microsoft Teams outage causes connection issues, message delays

#61

Post by w0m »

bboygravity wrote: post #46
Vigorosotuna96 wrote: post #42

Earlier quoted context omitted.

Spot on analysis. It's a broken product, most of the time, for me.

And yet companies don't mind the extremely obvious loss of productivity this causes. They also don't mind that it makes them look unprofessional. At all. I've seen townhall meetings where 200+ FTE where sitting around waiting for Teams to stop glitching for like 10 minutes. And after they go back to their desk for real work, the glitching continues. "innovation"

My previous employer forced us to use a Hip hat instance. It was legitimately hell, deleting history randomly and just atrocious. Using Teams now (switched jobs) it legitimately feels mystical in comparison.

Re: Microsoft Teams outage causes connection issues, message delays

#62

Post by hhh »

nerdjon wrote: post #7

What I find most interesting about this is how long it took to see reporting on this issue, unlike what I remember the reporting on Slack being down 5 or 6 years ago that I could fairly reliably find somewhere that said it was down. Has how we used these tools just changed? They are so janky in the first place that them being "down" is questionably different? Just seems weird.

I didn't even look at HN because our yammer page had a post within a few minutes with a description of the issue, an ETA for a fix, and a time for a next update.

I don't know if the speed of a technical status update is related to how much we pay to MS, but it definitely feels that way.

Re: Microsoft Teams outage causes connection issues, message delays

#63

Post by mh- »

w0m wrote: post #61
bboygravity wrote: post #46

Earlier quoted context omitted.

And yet companies don't mind the extremely obvious loss of productivity this causes. They also don't mind that it makes them look unprofessional. At all. I've seen townhall meetings where 200+ FTE where sitting around waiting for Teams to stop glitching for like 10 minutes. And after they go back to their desk for real work, the glitching continues. "innovation"

My previous employer forced us to use a Hip hat instance. It was legitimately hell, deleting history randomly and just atrocious. Using Teams now (switched jobs) it legitimately feels mystical in comparison.

I can't help but imagine what it'll feel like if you find a job that uses Slack.

Re: Microsoft Teams outage causes connection issues, message delays

#64

Post by myko »

portaouflop wrote: post #47
myko wrote: post #35

Earlier quoted context omitted.

Teams is always pretty bad, I noticed slightly worse service/message duplication/call drops today. If it weren't for MS being a monopoly I doubt we'd use it

How is MS a monopoly when it comes to workspace tools? Seems to me there are plenty of alternatives and I am lucky enough that I never had to use it at work.

If your org uses Microsoft products, typically a Teams license is baked in (or at least was at some point). So when it comes to choosing a better tool vs Teams it is an easy decision for the bean counters - we're already paying for Teams, let's just use it.

Re: Microsoft Teams outage causes connection issues, message delays

#65

Post by krisoft »

easton wrote: post #54
manmal wrote: post #53

Earlier quoted context omitted.

> I don't know why people waste their time using teams Because its use is mandated by workplaces, schools, and lots of other entities & communities. I rather hate Teams, but suddenly I’m finding myself spending half my days with it.

And those places use it because it’s free. You’re already paying for Exchange or Office, so Teams comes free. Nobody believes it’s the best product, but it’s 70% as good as Slack for free.

You are absolutely right. To me this kind of bundling is absolutely infuriating. I wish we could literally outlaw it.

At work we just transfered from zoom to google meet. We did this while everyone who expressed an opinion agreed that zoom is simply a superior product. And we did it because “we are already paying for it with our google docs subscription”.

It is just so anti-competitive I can’t even believe we collectively let this happen.

Re: Microsoft Teams outage causes connection issues, message delays

#68

Post by ziml77 »

I wouldn't have realized this issue if a coworker wasn't looking at my screen, seeing the messages they had sent 10 minutes prior just popping up. There was no way I could have known they were late because the timestamps in Teams were the time I received the messages instead of the time the messages were sent. On his end there was also nothing indicating that there was a delivery problem.

At the very least Microsoft could have given us some system-wide notification that there were problems...

Re: Microsoft Teams outage causes connection issues, message delays

#69

Post by Jedd »

ziml77 wrote: post #68

I wouldn't have realized this issue if a coworker wasn't looking at my screen, seeing the messages they had sent 10 minutes prior just popping up. There was no way I could have known they were late because the timestamps in Teams were the time I received the messages instead of the time the messages were sent. On his end there was also nothing indicating that there was a delivery problem. At the very least Microsoft…

How would that work? You'd get an in-app message in 40 minutes saying there's a problem 40 minutes ago?

Anyway, this is what status pages are for: https://admin.microsoft.com/servicestatus (currently showing a whole lotta information about problems with Microsoft Teams).

Re: Microsoft Teams outage causes connection issues, message delays

#70

Post by winrid »

Jedd wrote: post #69
ziml77 wrote: post #68

I wouldn't have realized this issue if a coworker wasn't looking at my screen, seeing the messages they had sent 10 minutes prior just popping up. There was no way I could have known they were late because the timestamps in Teams were the time I received the messages instead of the time the messages were sent. On his end there was also nothing indicating that there was a delivery problem. At the very least Microsoft…

How would that work? You'd get an in-app message in 40 minutes saying there's a problem 40 minutes ago? Anyway, this is what status pages are for: https://admin.microsoft.com/servicestatus (currently showing a whole lotta information about problems with Microsoft Teams).

Use message sent date for one, and check how late messages are arriving. If late, ping a status check endpoint.
Post reply on HN