Sumo Logic: incident history

← Back to Sumo Logic's check readings

We started checking Sumo Logic on November 2, 2026, which is 7 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Sumo Logic's own status page declared. Below it, any public chatter we saw about Sumo Logic and the extra probe it triggered.

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

Their declared record

Sumo Logic's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Showing the 10 most recent of 51 incidents Sumo Logic has declared in the history we hold.

These entries are Sumo Logic's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Sumo Logic's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.