<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:meetgeek.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://meetgeek.instatus.com/history.atom"/>
  <title>Meetgeek Status - Incident history</title>
  <updated>2026-06-11T07:17:41.989+00:00</updated>
  <author>
    <name>Meetgeek</name>
  </author>
  
<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmq960trh049yqrk8uk9045qg</id>
  <published>2026-06-11T07:17:41.989+00:00</published>
  <updated>2026-06-11T07:17:41.989+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmq960trh049yqrk8uk9045qg"/>
  <title>Degraded performance Issues with Zoom Agents joining calls</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>07:17:41</var> GMT+0</small><br /><strong>Identified</strong> -
  A subset of users are experiencing issues with meeting agents joining Zoom calls. We recommend using alternative recording options such as the Desktop App or Chrome Extension..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmq0pncgm0ciuparx9552mgdj</id>
  <published>2026-06-04T10:00:00.000+00:00</published>
  <updated>2026-06-04T10:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmq0pncgm0ciuparx9552mgdj"/>
  <title>Google Meet bots randomly quit meeting issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 2 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Google Meet meetings might be cut off short randomly.  
A minor percentage of users are affected by this issue.  
We are actively working on a fix for this incident..</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>12:23:39</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmpxyr9ab01zznwp2vfv79pzd</id>
  <published>2026-06-03T10:00:06.586+00:00</published>
  <updated>2026-06-03T10:00:06.586+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmpxyr9ab01zznwp2vfv79pzd"/>
  <title>Google Meet Agent Joining Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 14 hours</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>10:00:06</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>10:38:06</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmkz7yqr0084ijcrmwtx8dt2e</id>
  <published>2026-01-29T07:30:38.087+00:00</published>
  <updated>2026-01-29T07:30:38.087+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmkz7yqr0084ijcrmwtx8dt2e"/>
  <title>Service Disruption Notification</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>07:30:38</var> GMT+0</small><br /><strong>Resolved</strong> -
  Dear Customer,  

We would like to inform you that on **28 Jan**, between **16:00 and 20:00 (UTC)**, we experienced an **unexpected incident in our AWS infrastructure**. During this period, our system was temporarily unable to allocate resources for the bots, which may have resulted in **missed or unfulfilled meetings**.  

The incident has been fully resolved, and all services are now operating normally. We sincerely apologize for any inconvenience this may have caused and truly appreciate your understanding.  

If you have any questions or require further clarification, please do not hesitate to contact us.

  
Kind regards,  
The MeetGeek Team.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmkb1ro6k0ndlu3sgj0a3w9n5</id>
  <published>2026-01-12T10:55:56.120+00:00</published>
  <updated>2026-01-12T14:04:58.236+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmkb1ro6k0ndlu3sgj0a3w9n5"/>
  <title>Zoom bot fails to join meetings</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 9 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>14:04:58</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>10:55:56</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>11:38:43</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmghrav5i001nsptvykulqk2k</id>
  <published>2025-10-07T21:42:00.000+00:00</published>
  <updated>2025-10-07T21:42:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmghrav5i001nsptvykulqk2k"/>
  <title>Issues with the meeting page not loading on the web app</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 42 minutes</p>
    <p><strong>Affected Components:</strong> Web Dashboard</p>
    <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>21:42:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>07:19:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmelo7oif000111xgq3dr45wf</id>
  <published>2025-08-21T14:30:00.000+00:00</published>
  <updated>2025-08-21T14:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmelo7oif000111xgq3dr45wf"/>
  <title>Degraded performance with the web and mobile apps and delays in analysis</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 5 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> Web Dashboard, Meeting Insights</p>
    <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified that users are experiencing elevated errors for the impacted services. At this time, no meeting recordings created during the affected period have been lost. All missing data will be fully recovered once the fix is implemented. Our team is committed to resolving this issue as quickly as possible, and we appreciate your patience..</p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>18:55:57</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result. All impacted services have now fully recovered. Our team is working to regenerate the missing or incomplete summaries for the affected meetings. We apologize for any inconvenience this may have caused and appreciate your patience while we resolve this issue..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>19:45:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmdfqwm6l00slehi03emkshn7</id>
  <published>2025-07-22T06:00:00.000+00:00</published>
  <updated>2025-07-22T06:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmdfqwm6l00slehi03emkshn7"/>
  <title>Google Meet Bot not recording meetings</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 2 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and we are working on a fix.</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmd4aqiv300cfr4v8c93zzsxq</id>
  <published>2025-07-01T21:00:00.000+00:00</published>
  <updated>2025-07-01T21:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmd4aqiv300cfr4v8c93zzsxq"/>
  <title>Zoom bot transcript has missing speakers</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 days, 12 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  There is an issue where the meetings recorded by the zoom bot do not provide the speakers.</p>
<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>08:21:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and we are currently working on a fix..</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>09:10:53</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmbuly1n2000jkogodr084kpk</id>
  <published>2025-06-13T09:31:01.322+00:00</published>
  <updated>2025-06-13T09:31:01.322+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmbuly1n2000jkogodr084kpk"/>
  <title>Microsoft Teams bot not joining</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 4 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>09:31:01</var> GMT+0</small><br /><strong>Identified</strong> -
  We are experiencing degraded performance with our Microsoft Teams Bots. .</p>
<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>09:43:13</var> GMT+0</small><br /><strong>Identified</strong> -
  Microsoft Teams is experiencing degraded performance, which causes a subset of Microsoft Teams Bots to have trouble joining the call. As a temporary workaround, you can use the MeetGeek CE &lt;https://chromewebstore.google.com/detail/meetgeek-ai-meeting-notes/jgcndlaikgkhpbcekabcmnfeiaelgaon&gt;.</p>
<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>14:10:03</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmbtqbq03000jjmdrm1iekx0v</id>
  <published>2025-06-12T18:45:49.829+00:00</published>
  <updated>2025-06-12T18:45:49.829+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmbtqbq03000jjmdrm1iekx0v"/>
  <title>Google Meet down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 18 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:45:49</var> GMT+0</small><br /><strong>Identified</strong> -
  There is currently an outgoing outage with Google Meet in some regions. Our bots are currently not able to join Google Meet meetings due to this issue..</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:04:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmbrtw8b10001b5i5xx4dht2b</id>
  <published>2025-06-10T12:25:00.000+00:00</published>
  <updated>2025-06-11T11:05:47.258+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmbrtw8b10001b5i5xx4dht2b"/>
  <title>Video not being recorded for Google Meet calls</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>11:05:47</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>12:25:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified cases where the Google Meet calls were being recorded without video. Our team is working on a solution to resolve this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmbqmfasf000dnj1bdw28497n</id>
  <published>2025-06-10T11:00:00.000+00:00</published>
  <updated>2025-06-10T11:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmbqmfasf000dnj1bdw28497n"/>
  <title>Meeting Summary delayed or not arriving</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Insights, Meeting Assistant</p>
    <p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an issue with meeting summaries going out or being delayed .</p>
<p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>14:12:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved, and all the incomplete summaries and insights have been regenerated..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cmavc1gt500fd11pirb6h8whr</id>
  <published>2025-05-18T15:00:00.000+00:00</published>
  <updated>2025-05-23T07:36:44.670+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cmavc1gt500fd11pirb6h8whr"/>
  <title>Long analysis time</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 16 hours and 37 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Insights</p>
    <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>07:36:44</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 18</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an incident where some meetings do not get analysed and summaries are not being sent out.  
  
Bots joining and recording are not affected by this incident..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>20:14:08</var> GMT+0</small><br /><strong>Identified</strong> -
  During peak hours, the analysis may take longer than anticipated, resulting in incomplete or missing summary and insights data for a subset of meetings. Our team is currently investigating the root cause of this issue and will restore any missing data once it is resolved..</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>06:35:34</var> GMT+0</small><br /><strong>Monitoring</strong> -
  All the missing summaries have been successfully generated. Our team has found the root cause of the longer analysis times and incomplete insights and is working on a solution to ensure this issue does not occur again. We apologize for any inconvenience this may have caused and appreciate your patience while we resolve this issue..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cma2pe221002ft76bick9modd</id>
  <published>2025-04-29T14:00:00.000+00:00</published>
  <updated>2025-04-29T14:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cma2pe221002ft76bick9modd"/>
  <title>Long analysis time and missing transcripts</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 10 hours</p>
    <p><strong>Affected Components:</strong> Meeting Insights</p>
    <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an incident where some meetings do not get analysed and summaries are not being sent out.  
  
Bots joining and recording are not affected by this incident..</p>
<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result. All impacted services have now fully recovered. Our team will work to recover the missing recordings, transcripts, and summaries for the meetings that finished recording in the affected period. We apologize for any inconvenience this may have caused..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cm9lo3qwm0094114ct0z1auo4</id>
  <published>2025-04-17T15:20:00.000+00:00</published>
  <updated>2025-04-17T15:20:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cm9lo3qwm0094114ct0z1auo4"/>
  <title>Elevated error rates</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 25 minutes</p>
    <p><strong>Affected Components:</strong> Web Dashboard, Meeting Assistant, Meeting Insights, Public API</p>
    <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>15:20:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified elevated error rates today, April 17th, from 3:20 PM to 4:45 PM UTC. During this time, the bot failed to join meetings, and recorded meetings that finished in this timeframe were not analyzed. .</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>16:45:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  All impacted services have now fully recovered. Our team will work to recover the missing recordings, transcripts, and summaries for the meetings that finished recording in the affected period. However, we regret to inform you that the meetings that were not recorded cannot be recovered. We apologize for any inconvenience this may have caused..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cm8myid3q002tjy2cnl7m7i0w</id>
  <published>2025-03-24T11:01:21.690+00:00</published>
  <updated>2025-03-24T11:01:21.690+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cm8myid3q002tjy2cnl7m7i0w"/>
  <title>Teams bot dropping </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 5 hours and 25 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>11:01:21</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an incident where the teams bot sometimes drops from the call..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>16:26:57</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>16:12:10</var> GMT+0</small><br /><strong>Identified</strong> -
  Issue was identified. We are working on a fix..</p>
<p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>16:26:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cm5o4a6i5000sl2h120nki1b7</id>
  <published>2025-01-07T15:25:00.000+00:00</published>
  <updated>2025-01-13T17:07:32.773+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cm5o4a6i5000sl2h120nki1b7"/>
  <title>Incomplete summary &amp; insights</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 1 hour and 43 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant, Meeting Insights</p>
    <p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>17:07:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>15:25:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  During peak hours, the analysis may take longer than anticipated, resulting in incomplete or missing summary and insights data for a subset of meetings. This incident started yesterday, January 7th at 3:25 GMT. Our team is currently investigating the root cause of this issue and will restore any missing data once it is resolved..</p>
<p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>16:05:44</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our team has successfully implemented a solution and is currently in the process of restoring the missing summaries for the affected meetings. We continue to investigate the longer analysis times and the incomplete insights data. We sincerely appreciate your patience and understanding in this matter..</p>
<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>12:34:12</var> GMT+0</small><br /><strong>Monitoring</strong> -
  All the missing summaries have been successfully generated. Our team has found the root cause of the longer analysis times and incomplete insights and is working on a solution to ensure this issue does not occur again. We apologize for any inconvenience this may have caused and appreciate your patience while we resolve this issue..</p>
<p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>15:43:44</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cm5b80tbd00022l0sj6kk87sg</id>
  <published>2024-12-30T15:55:24.357+00:00</published>
  <updated>2024-12-30T17:01:57.854+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cm5b80tbd00022l0sj6kk87sg"/>
  <title>Bot fails to join meetings</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 7 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>17:01:57</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The issue causing our bots to not join meetings earlier today has been fully resolved. Please rest assured this was not an issue on MeetGeek’s side but rather an outage with our server provider.

Our team worked diligently alongside our provider to ensure a swift resolution. All systems are now operating normally, and we’re closely monitoring performance to ensure a smooth experience moving forward.

We sincerely apologize for any inconvenience this may have caused and appreciate your understanding..</p>
<p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>15:55:24</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating reports where the bot is not joining some meetings..</p>
<p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>17:01:57</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cm4tqan5u001pt8swfdqjar2r</id>
  <published>2024-12-18T10:07:04.568+00:00</published>
  <updated>2024-12-18T10:07:04.568+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cm4tqan5u001pt8swfdqjar2r"/>
  <title>Teams bot not joining all calls</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 8 hours and 25 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>10:07:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating reports where the teams bot is not joining some meetings..</p>
<p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>10:25:20</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and are working on a solution..</p>
<p><small>Dec <var data-var='date'> 19</var>, <var data-var='time'>07:36:06</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have deployed a fix and currently monitoring.</p>
<p><small>Dec <var data-var='date'> 19</var>, <var data-var='time'>18:32:17</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cm4l6wrb3000x47w4iicp5och</id>
  <published>2024-12-11T23:30:00.000+00:00</published>
  <updated>2024-12-11T23:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cm4l6wrb3000x47w4iicp5och"/>
  <title>Summary missing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 hours and 33 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant, Meeting Insights</p>
    <p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>23:30:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have identified an issue with the summary generation between 11:30 PM and 03:00 AM GMT. Our team has successfully resolved the problem and is monitoring the situation. All the missing summaries from the last 12 hours will be recovered. We sincerely appreciate your patience and understanding..</p>
<p><small>Dec <var data-var='date'> 12</var>, <var data-var='time'>15:03:21</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved and all the missing summaries were successfully generated..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cm49w4t9100945ujki8uns3m5</id>
  <published>2024-12-03T15:45:00.000+00:00</published>
  <updated>2024-12-04T13:30:54.364+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cm49w4t9100945ujki8uns3m5"/>
  <title>Issue with the summary email delivery</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>13:30:54</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>15:45:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified an issue with the meeting summary emails not being delivered since yesterday, Dec, 3rd. Our engineers are actively working on fixing it..</p>
<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>13:25:05</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cm2d3kftl000fvrbp16vjpc5a</id>
  <published>2024-10-17T09:00:00.000+00:00</published>
  <updated>2024-10-17T09:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cm2d3kftl000fvrbp16vjpc5a"/>
  <title>Summary missing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 9 hours and 23 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Oct <var data-var='date'> 17</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware of an issue which affects the generation of meeting summaries. We have identified the issue and are working on fixing it..</p>
<p><small>Oct <var data-var='date'> 17</var>, <var data-var='time'>16:30:45</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our team has successfully resolved the issue and is monitoring the situation. All the missing summaries from the last 20 hours will be recovered. We sincerely appreciate your patience and understanding..</p>
<p><small>Oct <var data-var='date'> 18</var>, <var data-var='time'>03:14:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved and all the missing summaries were successfully generated..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cm1ke6btj001jq76fkkdt7jf2</id>
  <published>2024-09-22T21:00:00.000+00:00</published>
  <updated>2024-09-29T21:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cm1ke6btj001jq76fkkdt7jf2"/>
  <title>Issues with Zoom recordings</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  After investigating the issues, we determined that the problem was on Zoom&#039;s side. Starting with 30/09/2024 this incident has been resolved. .</p>
<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified instances in which certain Zoom meetings are recorded without sound. Consequently, these meetings lack a transcript and do not appear on the Past Meetings page. Our team is actively investigating this issue..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Incident/cm0mau7n50035dsahe2gd17nz</id>
  <published>2024-09-01T12:30:00.000+00:00</published>
  <updated>2024-09-01T12:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/incident/cm0mau7n50035dsahe2gd17nz"/>
  <title>Issues with Zoom recordings</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 days, 19 hours and 28 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Assistant</p>
    <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We identified cases for a subset of users in which the bot leaves the call shortly after it starts recording. We are currently investigating this incident..</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>10:35:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We resolved the issue and are currently monitoring the situation. All impacted users are now able to record Zoom video meetings without any issues. We sincerely appreciate your patience and understanding during this time..</p>
<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>07:57:59</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Maintenance/clcq2tcs370725poomtv54pqgj</id>
  <published>2023-01-13T17:00:00.000+00:00</published>
  <updated>2023-01-13T16:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/maintenance/clcq2tcs370725poomtv54pqgj"/>
  <title>Scheduled maintenance on Friday, 13th of January. Our services will be unavailable during 2PM - 6PM UTC.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours and 22 minutes</p>
    <p><strong>Affected Components:</strong> Meeting Insights, Web Dashboard, Meeting Assistant</p>
    <p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>16:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is not completed yet..</p>
<p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is almost done..</p>
<p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Our services will be unavailable during 2PM - 6PM UTC time for planned service maintenance..</p>
<p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>21:21:40</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has been completed successfully. This time it is for real. :) .</p>
<p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:meetgeek.instatus.com,2005:Maintenance/cl9zd8z8l0714j7ohwvzl973y</id>
  <published>2022-11-03T09:00:00.000+00:00</published>
  <updated>2022-11-03T09:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://meetgeek.instatus.com/maintenance/cl9zd8z8l0714j7ohwvzl973y"/>
  <title>Scheduled maintenance for 9-12 CET, 3rd of November 2022</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Meeting Insights, Web Dashboard, Meeting Assistant</p>
    <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are going to perform a scheduled maintenance during 9-12 CET, the 3rd of November 2022.</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

</feed>