We started checking Livestorm on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Livestorm reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Livestorm's own status page declared. Below it, any public chatter we saw about Livestorm and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Livestorm's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Livestorm in the last 24 hours, which is not evidence that nothing is wrong.
Livestorm's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Livestorm's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Livestorm next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
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.
Region
Checks passing
Probes recorded
US-East
100.00%
443
US-West
99.70%
334
Europe
100.00%
307
Asia-Pacific
100.00%
186
Their declared record
Livestorm's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Potential Interruption to Attendance AnalyticsMinor incident
Nov 2, 2026, 4:03 PM UTC to Nov 2, 2026, 4:31 PM UTC (29 min)resolved
their latest update (Nov 2, 2026, 4:31 PM UTC): The component upgrade has been successfully rolled back, and Attendance Analytics are now being recorded as expected. The issue is considered resolved.
We sincerely apologize for any inconvenience this may have caused and thank you for your patience and understanding.
Live Captions and Translations unavailableMinor incident
Sep 24, 2026, 9:00 AM UTC to Sep 24, 2026, 9:33 AM UTC (33 min)resolved
their latest update (Sep 24, 2026, 9:33 AM UTC): This incident has been resolved. Live Captions and Translations are working normally again.
We have also taken steps to prevent this from happening again.
We apologize for the inconvenience.
Session list has latency in some casesPartial outage
Jul 9, 2026, 4:41 PM UTC to Jul 9, 2026, 5:41 PM UTC (1h)resolved
their latest update (Jul 9, 2026, 5:41 PM UTC): The incident has been resolved. The root cause has been identified and we took measures to fix it.
Some attendees unable to complete event registrationPartial outage
Jun 11, 2026, 12:14 PM UTC to Jun 11, 2026, 12:34 PM UTC (20 min)resolved
their latest update (Jun 11, 2026, 12:34 PM UTC): This incident has been resolved. Event registration is fully operational, and all attendees can register and receive their access link normally. Already-registered attendees were unaffected and no data was lost.
We apologize for the disruption and appreciate your patience.
May 27, 2026, 3:08 PM UTC to May 27, 2026, 3:33 PM UTC (25 min)resolved
their latest update (May 27, 2026, 3:33 PM UTC): This incident has been resolved. Service availability has been fully restored, and monitoring confirms that the platform is operating normally.
The disruption was caused by a change introduced during a Kubernetes cluster upgrade, which affected internal cluster connectivity. We …
Login with Google or Microsoft SSO is currently failingAll systems operational
May 19, 2026, 8:15 AM UTC to May 19, 2026, 8:28 AM UTC (13 min)resolved
their latest update (May 19, 2026, 8:28 AM UTC): The issue affecting Google and Microsoft SSO login has been resolved following the rollback.
We have confirmed that SSO authentication is functioning as expected.
Observed latency on the platformPartial outage
May 18, 2026, 1:16 PM UTC to May 18, 2026, 1:48 PM UTC (32 min)resolved
their latest update (May 18, 2026, 1:48 PM UTC): Following our monitoring over the past few minutes, we can confirm that there is no longer any ongoing impact related to this issue. Users should now be able to access the platform and its features as expected.
We sincerely apologize for any inconvenience caused and appreciate y…
Event creation and event registration failingPartial outage
May 14, 2026, 11:45 PM UTC to May 14, 2026, 11:46 PM UTC (0 min)resolved
their latest update (May 14, 2026, 11:46 PM UTC): This incident has now been resolved. The root cause was identified as an internal component being overwhelmed by an unusually high volume of scheduled jobs originating from a single source. We have since removed the problematic jobs and scaled the infrastructure accordingly.
All…
Event creation and event registration failingPartial outage
May 14, 2026, 12:54 PM UTC to May 14, 2026, 2:03 PM UTC (1h 9m)resolved
their latest update (May 14, 2026, 2:03 PM UTC): This incident has been resolved. The root cause was identified as an internal component being overwhelmed by an abnormally large number of scheduled jobs originating from a single source. We have removed the offending jobs and scaled our infrastructure accordingly. All features, …
Users are unable to join the event roomPartial outage
Apr 29, 2026, 9:30 AM UTC to Apr 29, 2026, 9:47 AM UTC (18 min)resolved
their latest update (Apr 29, 2026, 9:47 AM UTC): The issue has now been resolved following the rollback of the recent infrastructure update. Normal behavior has been restored, and no further impact has been observed.
We apologize for any inconvenience this may have caused and appreciate your patience. We will continue monitori…
Showing the 10 most recent of 51 incidents Livestorm has declared in the history we hold.
These entries are Livestorm'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.
Livestorm'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.