GlobalMeet Outage History

GlobalMeet is up right now

Pingoru has recorded 11 incidents for GlobalMeet: 4 in the last 12 months and 1 in the last 90 days.

Source: status.globalmeet.com

11incidents recorded
4last 12 months
1last 90 days
14 hourstypical duration

Incidents, newest first

Notice September 23, 2026 Updated WYSIWYG Editor - Unanticipated Effects 2d 3h GlobalMeet Webcast

Started Sep 23, 2026, 09:51 PM UTC· resolved Sep 26, 2026, 01:32 AM UTC

  1. monitoring Sep 23, 2026, 09:51 PM UTC

    We are investigating issues related to our latest release (6.4) on Sept 19th affecting the behavior of our new WYSIWYG editor: 1. When making edits using Code View on some WYSIWYG editors you must toggle from Code View back to the default (text view) prior to saving the page. 2. Additionally, emails that include HTML tables may now show borders where previously they did not. If you are experiencing any issues with the editor, please contact [email protected] for assistance.

  2. resolved Sep 26, 2026, 01:32 AM UTC

    We have released an update to resolve the issues experienced with the WYSIWYG editor. If you continue to experience any issues, please contact [email protected].

Read the full incident report →

Notice May 21, 2026 Live Streaming Performance Issue 2h 45m GlobalMeet Webcast

Started May 21, 2026, 07:00 AM UTC· resolved May 21, 2026, 09:45 AM UTC

  1. investigating May 21, 2026, 09:22 AM UTC

    We are currently investigating an issue where GlobalMeet Webcast platform users may be experiencing service disruption during live streaming events.

  2. resolved May 21, 2026, 09:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 18, 2026 Webcast Link Access Issues 21m GlobalMeet Webcast

Started May 18, 2026, 01:37 PM UTC· resolved May 18, 2026, 01:58 PM UTC

  1. investigating May 18, 2026, 01:37 PM UTC

    We are currently investigating an issue with some viewers not being able to access Webcast links. An update will be provide once more information is available.

  2. resolved May 18, 2026, 01:58 PM UTC

    The issue with viewer access to links has been resolved. Links should now be available or available shortly.

Read the full incident report →

Critical December 3, 2025 Webcast Platform Impairment 53m GlobalMeet Webcast

Started Dec 03, 2025, 01:22 PM UTC· resolved Dec 03, 2025, 02:15 PM UTC

  1. investigating Dec 03, 2025, 02:15 PM UTC

    We are experiencing a temporary system impairment, and our engineers are currently on site. We have identified the problem and are working to resolve the issue. At this time, there is no ETA. We will provide an update as soon as we have one.

  2. identified Dec 03, 2025, 02:15 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Dec 03, 2025, 02:20 PM UTC

    Services have been fully restored. Our team will continue to monitor.

Read the full incident report →

Notice August 19, 2025 Unable to Create Telephony Events 1h 9m GlobalMeet Webcast

Started Aug 19, 2025, 08:05 AM UTC· resolved Aug 19, 2025, 09:14 AM UTC

  1. investigating Aug 19, 2025, 08:05 AM UTC

    Incident Symptom(s)*: Users are currently unable to create a telephone event. Additionally, the number of presenters displays as 0 despite both primary and backup bridges being connected. Impact: Users are experiencing issues with creating and maintaining stable telephone events. API calls to both SIP providers are timing out. Additional comment: Users are currently unable to create a telephone event. Additionally, during the live event, the number of presenters displays as 0 even though both the primary and backup bridges are connected. The count intermittently changes to 1, then fluctuates between 1 and 0.

  2. identified Aug 19, 2025, 08:52 AM UTC

    Engineering identified the problem and contacted Support for both SIP providers, awaiting response.

  3. monitoring Aug 19, 2025, 08:53 AM UTC

    The SIP providers have returned to a 'Green' status in our monitoring system.

  4. resolved Aug 19, 2025, 09:14 AM UTC

    This incident has been resolved.

Read the full incident report →