Microsoft Viva Glint became unreachable for some users for 1h 38m starting at 21:48 UTC. Microsoft's own status page confirms this was a fault on their side, affecting any user attempting to access Viva Glint.
Started
21:48 UTC
Duration
Lasted 1h 38m
Source
IsDown
Next time
Microsoft 365 is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Microsoft Viva
What happened?
Microsoft logged one incident on 28 September 2026, affecting Viva Glint, a single component within Microsoft 365. It started at 21:48 UTC and ran for 1h 38m. Microsoft's first update, posted a minute later at 21:49, described the issue as a potential problem with Viva Glint and said they were checking for impact to your organisation, with a further update promised within 30 minutes. That second update came at 22:16, by which point Microsoft said they were reviewing service logs to isolate the source and find a mitigation. The scope line in that update is explicit: this event impacts any user attempting to access Viva Glint. Microsoft gave a start time of 9:15 PM UTC and said the next update would come by 11:30 PM UTC. Only two updates were filed in total for this incident, and neither explains what caused the fault. No user reports were filed during the window, so there is no independent account of symptoms beyond what Microsoft itself described. The record does not show whether Microsoft published a closing update at or near the 1h 38m mark, only that the incident's duration is recorded as 1h 38m. Over the past 90 days Microsoft 365 has logged 43 incidents with a median duration of 10 hours 47 minutes, so this one resolved well under that typical length. Across all time, Microsoft averages 7.7 incidents a month on this service.
Learning
Viva Glint is a narrow slice of Microsoft 365, and an incident confined to it will not necessarily show up if your own monitoring only checks core services like Exchange or SharePoint. That is the general shape of this kind of failure: a single component breaks on the provider's side, the provider confirms impact to anyone trying to use it, and nothing about your own endpoints changes because the fault never touched your infrastructure. Watching your own product tells you whether your systems are up, not whether the services you depend on are. Microsoft's own status page is the only account here, since no user reports landed in this window, which means the full picture rests on two short updates thirty minutes apart. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
