This incident has been resolved. Google has confirmed the Firebase incident ended at 8:30 PM PT on October 21. MeetingPulse has been operating normally since then. Thank you for your patience.
Posted Oct 22, 2026 - 16:00 UTC
Update
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.
Posted Oct 22, 2026 - 04:03 UTC
Update
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.
Posted Oct 22, 2026 - 00:20 UTC
Monitoring
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 support@meetingpulse.net with the start time and we will watch it with you.
Posted Oct 22, 2026 - 00:05 UTC
Identified
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.