Microsoft 365 and Outlook restored after nearly 24-hour global outage

·1 views

Microsoft 365, Outlook, Teams, Copilot and over ten other services went offline for nearly a day, affecting users in at least 70 countries. The company attributed the disruption to problems during an earlier network capacity upgrade and ruled out cyberattacks and AI agents as causes. Services returned around 3 p.m. ET on Friday, with recovery carried out in stages and stability checked at each step. Organizations including businesses, governments, schools, courts and UK NHS staff were affected, and some Japanese firms temporarily reverted to fax. Microsoft has apologized, said emails held during the outage will be queued for up to 48 hours, and plans to publish a full post-incident report.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Workplace notices on H-1B filings: what employers must post and what they do not mean

U.S. labor rules require employers to post a notice at the workplace when they file a Labor Condition Application for an H-1B worker. The notice can be posted on the filing day or during the 30 days before it. It lists the job category, offered wage, employment period, and work locations, and tells readers how to file a complaint with the Department of Labor. The notice is not a job advertisement, a USCIS approval, or the LCA itself. The requirement comes from 20 CFR 655.734 and section 212(n) of the Immigration and Nationality Act, and is described in DOL's Wage and Hour Division Fact Sheet #62M.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

LudyPlay Combines Trivia, Survival, and Racing in One Browser Game Portal

Developer Ludy has built LudyPlay, a free browser-based game portal offering open-answer trivia, a 15-minute survival run, and a coastal motorcycle race. The write-up argues that the key design challenge is giving very different games a shared entry point while letting each one keep its own rules, input handling, and lifecycle. For typed trivia answers, it suggests normalizing input and applying an explicit acceptance check, since overly generous fuzzy matching can wrongly mark incorrect answers as correct. The author recommends that each game own its session state while shared navigation stays separate, which avoids one oversized state object and makes testing easier. Ludy is asking players for specific feedback, especially on trivia answer acceptance and survival session length.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Restaurant POS contracts can lock owners into exit fees, including for menu pages

Many restaurant owners pay a single monthly bill that bundles a point-of-sale system with a website and menu page, but the bundle is in fact a term contract. Reviewing agreements from Toast, Clover and Square on 14 November 2026, the author found that Toast and Clover impose renewal terms and early-exit fees, while Square advertises monthly plans with no lock-in. Toast's early termination fee can equal the remaining subscription fees, or $150 per remaining month on pay-as-you-go plans, so two years left would cost $3,600. The author argues the menu page is not part of the financed hardware and software, so it need not be bundled into the contract at all.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Re-Encoding Before Upscaling Often Wastes Quality, Measurements Show

A DEV Community author tested whether transcoding compressed video to a lossless format before upscaling improves results, as many tutorials recommend. Using a downscaled test frame with a full-resolution original as ground truth, the author scored each pipeline with PSNR, SSIM, and a blockiness index. A lossless round trip produced results identical to skipping it, so it adds a step without changing the output. When bitrate was matched per pixel, encoding after upscaling outperformed encoding before by 0.6 to 1.4 dB. The author attributes this to the upscaler amplifying codec errors that were introduced during pre-encoding.

0 comments Read more at DEV Community