this post was submitted on 16 Nov 2026
459 points (97.7% liked)

Technology

89924 readers
3483 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] DougPiranha42@lemmy.world 41 points 4 days ago (2 children)

Interesting. A client side bug causes server-level overload but only after unrelated changes gradually make the problem worse. Rerouting traffic to healthy servers overloads those too and spreads the outage. The client code surely “worked on my computer” lol

[–] eleijeep@piefed.social 34 points 4 days ago (2 children)

Where did they say it was a client side bug?

[–] threeonefour@piefed.ca 52 points 4 days ago (1 children)

It says multiple times that the issue was with Microsoft's internal cloud server software, not Windows.

The defect came from a fix prepared specifically for Microsoft 365 networking gateway servers.

The failure was within Microsoft’s cloud infrastructure, not customer Windows systems

[–] eleijeep@piefed.social 9 points 4 days ago* (last edited 4 days ago)

Yeah exactly, I don't understand how the original comment is still getting upvotes.

Since your comment it gained (+36, -11). People don't read, I guess.

[–] DougPiranha42@lemmy.world 3 points 4 days ago

I guess I misunderstood it.

Inside an internal Windows process, competing tasks were waiting for access to shared resources, a problem called lock contention. Under certain traffic conditions, this exhausted processor and memory capacity.

I read this as the behavior that precipitated the issue on the gateway was caused by how Windows sent traffic to exchange servers. So by Windows they mean whatever is running on the gateway?

[–] gian@lemmy.grys.it 1 points 3 days ago

Probably.

Joking aside, the problem with testing is that you normally cannot have a complete copy of the production env to test against, with all the possible cases.
You may have a test env that do not trigger certain corner case scenario which can be dependent on something completely out of the domain, like in this case.

If they learned something, they would add some way of testing even this kind of scenario in the future.