rewindex

ChangesFireHydrantUnable to start incidents in Microsoft Teams

FireHydrant: Major incident: Unable to start incidents in Microsoft Teams

Major incidentoutage (model (Jev), 100%)Changed Detected status.firehydrant.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what FireHydrant removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Unable to start incidents in Microsoft Teams
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-06-26 18:18 UTC
AddedResolved time#5
Before: not present
After: 2025-06-26 18:36 UTC
AddedUpdate#6
Before: not present
After: We have deployed a fix to MS Teams and are waiting to confirm that this solves the issue

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

History of this incident

Thursday, June 26, 2025

1 incident change

Cite this

Major incident: Unable to start incidents in Microsoft Teams on FireHydrant’s status page, changed 2025-06-26 18:18 UTC (change 1 of 1).

Title
Major incident: Unable to start incidents in Microsoft Teams
Vendor
FireHydrant
Date
URL
https://rewindex.com/change/i2d535d8741ced4

All FireHydrant changesFireHydrant profileMarkdownJSON