[HN Gopher] Microsoft Teams outage causes connection issues, mes...
___________________________________________________________________
Microsoft Teams outage causes connection issues, message delays
Author : daviddavis
Score : 78 points
Date : 2024-01-26 18:50 UTC (4 hours ago)
(HTM) web link (www.bleepingcomputer.com)
(TXT) w3m dump (www.bleepingcomputer.com)
| packetlost wrote:
| Oh good, I was worried my accounts had been locked and I had been
| laid off
| jacquesm wrote:
| That could still be the case ;)
| packetlost wrote:
| It's not ;)
| bloopernova wrote:
| What's the correct status page to check?
|
| I would have assumed this: https://status.office365.com/ but it
| shows nothing useful.
|
| https://portal.office.com/servicestatus At least this one shows
| there's an issue.
| jdksmdbtbdnmsm wrote:
| that usually depends on who wants to know
| LordGrey wrote:
| That page indicates that "Teams (Consumer)" is having an issue,
| but my enterprise version is also fubar'd. Messages are coming
| through, but with a 30 minute delay. A person's status is not
| realtime.
|
| Weirdly, I am unable to hide an entire conversation, which is
| something I didn't think would require a round trip to the
| backend.
| zamadatix wrote:
| The service health page of the 365 admin center. Normal users
| won't have access to those though, best place for reliable
| updates in that case is the X account from the article.
| pid-1 wrote:
| I've found the 'Health > Dashboard' page on the admin portal to
| be the most reliable place to check for incidents:
| https://admin.microsoft.com/AdminPortal/Home?#/healthovervie...
|
| Some users may experience multiple issues with their Microsoft
| Teams TM710344, Last updated: Jan 26, 2024, 6:00 PM GMT-3
| Estimated start time: Jan 26, 2024, 12:37 PM GMT-3
|
| User impact Users may experience multiple issues with their
| Microsoft Teams.
|
| Title: Some users may experience multiple issues with their
| Microsoft Teams
|
| User impact: Users may experience multiple issues with their
| Microsoft Teams.
|
| More info: Affected scenarios include, but aren't limited to: -
| Users performing a cold boot may not able to log into teams and
| will see an "oops" page
|
| - Users logging in or unlocking their devices after some time
| may see missing messages
|
| - Users may fail to load messages in channels and chats
|
| - Users are unable to view or download their media (images,
| videos, audio, call recordings, code snippets)
|
| - Some messages may experience delays being sent
|
| - Call Recordings might take longer to appear in user's
| OneDrive for Business and SharePoint Online
|
| - Users may be unable to load previous Copilot history, or new
| history is not written
|
| - Bots may be unable to download attachments
|
| - Sending and receiving read receipt notifications may be
| delayed
|
| - Anonymous users may be unable to join meetings
|
| - Teams connectors for Power Automate/Power Apps may
| experiencing errors
|
| Current status: Our failover operation did not provide the
| immediate relief intended for end users in North and South
| America regions. However, we're monitoring telemetry closely as
| we continue to optimize traffic patterns and apply
| configuration changes intended to reduce customer impact as
| quickly as possible. We understand the impact an issue like
| this can have on your organization, and we appreciate your
| partnership and patience as we work to remediate this issue.
|
| Scope of impact: This issue can potentially impact any
| Microsoft Teams user in the scenarios outlined in the More info
| section.
|
| Start time: Friday, January 26, 2024 at 11:55 AM GMT-3 .
|
| Next update by: Friday, January 26, 2024 at 7:00 PM GMT-3
| numbsafari wrote:
| You won't see "CxO customer tee-times impacted" on that
| list...
| BobaFloutist wrote:
| https://downdetector.com/status/teams/
| Xiol32 wrote:
| So nothing out of the ordinary, then.
| a_vanderbilt wrote:
| No one noticing it is down because it usually isn't working
| anyways.
| stagger87 wrote:
| It's always interesting to hear others experiences. I've used
| Teams for 4+ years now with zero issues until this morning.
| I'm only mad in that I tried troubleshooting my PC and
| network connection for far too long before seeing this
| thread.
| blibble wrote:
| I had a new one this week
|
| every time someone tries screensharing to me the call hangs
| up and I get "Uh oh, something went wrong!"
|
| yeah something went wrong, someone decided to pay for Teams
| PH95VuimJjqBqy wrote:
| pretty sure you're wrong, I think Teams gets bundled, no
| one actually pays for it ;)
| robertlagrant wrote:
| Yeah, it's free. Somehow that's competitive, even though
| it forced Slack to sell up, but iPhone having a 20%
| global smartphone market share is anticompetitive.
| JohnFen wrote:
| My employer certainly pays for it. It's bundled with
| O365, but they pay for O365 and so they also pay for
| Teams.
| zwieback wrote:
| Same here, hp switched to Teams a while back and it's been
| working great until today. Also think we should have gotten
| an alert earlier. I switched to my phone app, that kept
| working for a bit but now it's total blackout.
| stagger87 wrote:
| Some sort of banner at the top of Teams indicating there
| is ongoing issues would be nice.
| robertlagrant wrote:
| Logging into two Teams accounts is always hilarious.
| nerdjon wrote:
| 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.
| dangerboysteve wrote:
| I think it was because it was a widespread problem or did not
| appear that way. Teams for our company were mostly working.
| hrunt wrote:
| I think it was because most people are used to Teams being an
| application with a poor experience, so a widespread
| degradation in service just looks like what people normally
| expect from Teams.
|
| I know in the orgs that I work with, everyone today blamed
| any problems on Teams being a crappy application. No one
| thought twice about it being something more than that.
| digging wrote:
| This was my experience. Teams was slow and functioning
| badly this morning, but it wasn't until someone else said
| they were also not seeing images that I realized it wasn't
| just typical jank. Teams is just not good to use in the
| first place so it doesn't occur to me to think I should
| check for outages whenever I have a problem.
| nerdjon wrote:
| I think especially with how Teams responded to this
| problem. It wasn't saying it couldn't connect or anything.
|
| I had a few symptoms:
|
| First teams froze my entire computer when I started it when
| it couldn't connect.
|
| Then it finally loaded and a message I sent would appear in
| the preview on the left but not actually in the chat window
| (the preview where it shows the name list of chats I have).
|
| Then messages would just sit with that circle sending, but
| I would receive messages occasionally.
|
| A simple "can't connect" would have gone a long way.
| JohnFen wrote:
| Personally, I just expect Teams to be janky. At least where I
| work, I don't think that a day goes by that it doesn't glitch
| out in one way or another.
| Quot wrote:
| That's my experience too. This outage seemed like the same
| jank I see every day. It just took me longer to realize it's
| jankier than usual.
| daemonologist wrote:
| Yeah, I noticed Teams messages being out of order (and being
| re-incorrectly-ordered multiple times) this morning and
| didn't think anything of it. I hadn't seen that particular
| bug before but it didn't stand out from the normal background
| jank.
| Vigorosotuna96 wrote:
| Spot on analysis. It's a broken product, most of the time,
| for me.
| robertlagrant wrote:
| People seem much harsher on Slack, for some reason. Sometimes
| being the better product just means people notice when it's
| broken.
| FridgeSeal wrote:
| Is there a term for how people just kind of acclimatise to a
| broken, buggy tool, and don't realise when it's extra broken?
|
| A sort of software Stockholm syndrome?
| myko wrote:
| 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
| heywire wrote:
| We started seeing signs of issues Wednesday and Thursday with
| messages being out of order or disappearing and reappearing.
| Today has been much worse. Not even able to send images (though
| thankfully gifs still work lol).
|
| Not sure if it is related, but in the same time period, Microsoft
| Family Safety has been flaky. My son will request more Xbox / PC
| time, I'll get the notification, but inside the app there is no
| request to approve. Or I'll get another notification hours later.
| blitzd wrote:
| The MS Family stuff has all been broken through the app for me
| for the past 2-3 months - I get the notifications, get the
| buttons to approve, and click works, everything seems normal -
| but nothing ever happens on the Xbox end. I just gave up on it.
| nyarlathotep_ wrote:
| Explains my afternoon.
| ParetoOptimal wrote:
| Wishful thinking:
|
| May this outage be perpetual and signal the demise of the
| enshittification of messaging platforms like teams.
| ArtemZ wrote:
| You still are going to have to use them at work, so be careful
| with your wishes.
| HumblyTossed wrote:
| Teams is pretty janky anyway, but today sucked.
| millzlane wrote:
| I honestly though this was all normal. Teams works great when
| it's working.
| password4321 wrote:
| For like 2 days a while back I was able to schedule sending
| messages in Teams, is that a feature controlled by admins or
| something?
___________________________________________________________________
(page generated 2024-01-26 23:00 UTC)