MeetingPulse Outage History

Started Oct 21, 2026, 10:40 PM UTC· resolved Oct 22, 2026, 04:00 PM UTC

1. identified Oct 21, 2026, 10:40 PM UTC

   MeetingPulse is experiencing access and loading failures related to an ongoing Google Firebase service disruption. Organizers and moderators may be unable to log in, and participants may be unable to access meetings through their meeting links. There is currently no confirmed restoration time. If your meeting is scheduled to begin soon, please arrange an alternative way to hold it and notify participants. We apologize for the disruption. We will post updates here as more information becomes available. You can also follow updates on the underlying service disruption on the Google Firebase status page.

2. monitoring Oct 22, 2026, 12:05 AM UTC

   Google confirmed at 4:13pm PT that a fix for the Firebase incident affecting MeetingPulse is being deployed. No completion time has been given. We are seeing some improvement, but service is not yet reliable: logins and participant links may load intermittently or fail. Please continue to use an alternative for any meeting or survey starting in the next few hours. We will post here as soon as service is stable, and again when Google marks the incident resolved. If you have an event starting soon, please email [email protected] with the start time and we will watch it with you.

3. monitoring Oct 22, 2026, 12:20 AM UTC

   Our checks have recorded no failed requests since 17:10 PDT, across roughly 180 test requests. Live meeting features are working normally again. Response times are mostly back to baseline, with a minority of requests still taking a few seconds longer than usual. Google's upstream incident remains open, so we are continuing on monitoring status until it closes and the remaining slowness clears.

4. monitoring Oct 22, 2026, 04:03 AM UTC

   MeetingPulse is fully operation as of 08:30pm Pacific time. We are awaiting the resolution of the underlying Google incident to mark this as Resolved.

5. resolved Oct 22, 2026, 04:00 PM UTC

   This incident has been resolved. Google marked the Firebase incident resolved at 7:57 AM PT on October 22. MeetingPulse has been operating normally since 8:30 PM PT on October 21. Thank you for your patience.

Read the full incident report →

Started Jun 25, 2025, 08:36 AM UTC· resolved Jun 25, 2025, 10:59 AM UTC

1. resolved Jun 25, 2025, 05:30 PM UTC

   Customers experienced errors in trying to reach the app

2. postmortem Jun 25, 2025, 05:33 PM UTC

   The incident was first reported at 9:01 AM UTC Began to resolve by 9:06 UTC and was resolved within a few minutes after that DigitalOcean Data center completed an initial investigation by 10:59 AM UTC and unable to detect root cause The issue appears to have been transient and is now resolved. Monitoring indicates that this is most likely caused by networking issues within the data center. We are working with the data center team to identify the root cause analysis, and working to identify potential preventative steps that we can take proactively.

Read the full incident report →

Started Jun 12, 2025, 06:18 PM UTC· resolved Jun 12, 2025, 08:36 PM UTC

1. investigating Jun 12, 2025, 06:18 PM UTC

   We are currently investigating this issue.

2. investigating Jun 12, 2025, 06:28 PM UTC

   Our systems are down due to an outage in the Google Cloud Platform.

3. resolved Jun 12, 2025, 08:36 PM UTC

   MeetingPulse access has been restored. The issue was caused by an outage in the Google Cloud Services. Further details are here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

Read the full incident report →

Started Jan 27, 2025, 10:03 PM UTC· resolved Jan 28, 2025, 07:40 AM UTC

1. investigating Jan 27, 2025, 10:03 PM UTC

   There is currently a known issue with our PowerPoint Add-In. We are investigating.

2. resolved Jan 28, 2025, 07:58 PM UTC

   The issue was resolved as of 11:40PM, Pacific Time, January 27th.

Read the full incident report →