Snapshot 166204

Document
Registry listing
URL
https://meetgeek.instatus.com/history.rss
Fetched
HTTP status
200
Content type
text/xml
Fetch mode
api
Size
48847 bytes
SHA-256 (raw)
55604276022fa09edb9b3c8b8c5fd02b9947b9940c47b1e5f401186d7adf94f4
SHA-256 (normalized text)
42b2c23107712d08106989a784c50c955599a4a9c1d8b1d4b44c8d7b12d37379

Raw (normalized text)

Scripts and page chrome removed; this is what change detection compares.

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Meetgeek Status - Incident history</title>
<link>https://meetgeek.instatus.com</link>
<description>Meetgeek</description>
<pubDate>Thu, 22 Oct 2026 14:00:00 +0000</pubDate>
<item>
<title>MeetGeek Web Application not working</title>
<description>
Type: Incident
Duration: 58 minutes
Affected Components: Web Dashboard
Oct 22, 14:57:51 GMT+0 - Resolved - This incident has been resolved. Oct 22, 14:00:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 58 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>14:57:51</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Thu, 22 Oct 2026 14:00:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmvjnip4o02ib13n5go02n4fo</link>
<guid>https://meetgeek.instatus.com/incident/cmvjnip4o02ib13n5go02n4fo</guid>
</item>
<item>
<title>Degraded Performance / Increased Latency in Application Services</title>
<description>
Type: Incident
Duration: 2 hours and 58 minutes
Affected Components: Web Dashboard
Oct 5, 10:42:46 GMT+0 - Resolved - Oct 5, 07:44:46 GMT+0 - Investigating - We are continuing to work on a fix for this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 2 hours and 58 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 5</var>, <var data-var='time'>10:42:46</var> GMT+0</small><br><strong>Resolved</strong> -
.</p>
<p><small>Oct <var data-var='date'> 5</var>, <var data-var='time'>07:44:46</var> GMT+0</small><br><strong>Investigating</strong> -
We are continuing to work on a fix for this incident..</p>
]]>
</content:encoded>
<pubDate>Mon, 5 Oct 2026 07:44:46 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmuuy2gd201420wjwo6mki85t</link>
<guid>https://meetgeek.instatus.com/incident/cmuuy2gd201420wjwo6mki85t</guid>
</item>
<item>
<title>MeetGeek Web Dashboard issues</title>
<description>
Type: Incident
Duration: 50 minutes
Affected Components: Web Dashboard
Sep 15, 15:19:34 GMT+0 - Resolved - This incident has been identified and resolved. Sep 15, 14:30:00 GMT+0 - Investigating - An error in our application caused the web dashboard to not function properly, we are currently investigating the cause.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 50 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>15:19:34</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been identified and resolved..</p>
<p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
An error in our application caused the web dashboard to not function properly, we are currently investigating the cause..</p>
]]>
</content:encoded>
<pubDate>Tue, 15 Sep 2026 14:30:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmu2tg9wt00h313qh5fi51394</link>
<guid>https://meetgeek.instatus.com/incident/cmu2tg9wt00h313qh5fi51394</guid>
</item>
<item>
<title>Degraded performance Issues with Zoom Agents joining calls</title>
<description>
Type: Incident
Duration: 27 days and 5 minutes
Affected Components: Meeting Assistant
Oct 6, 07:22:39 GMT+0 - Resolved - This incident has been resolved. Sep 2, 12:01:56 GMT+0 - Identified - We&#039;re seeing degraded performance for meeting agents joining Zoom calls. Video recording and Voice Agents are unavailable for these meetings, which will be captured as audio-only. Transcripts and summaries are unaffected. In the meantime, we recommend using the Desktop App or Chrome Extension. Jun 11, 07:17:41 GMT+0 - Identified - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 27 days and 5 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>07:22:39</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>12:01:56</var> GMT+0</small><br><strong>Identified</strong> -
We&#039;re seeing degraded performance for meeting agents joining Zoom calls. Video recording and Voice Agents are unavailable for these meetings, which will be captured as audio-only. Transcripts and summaries are unaffected. In the meantime, we recommend using the Desktop App or Chrome Extension..</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:encoded>
<pubDate>Thu, 11 Jun 2026 07:17:41 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmq960trh049yqrk8uk9045qg</link>
<guid>https://meetgeek.instatus.com/incident/cmq960trh049yqrk8uk9045qg</guid>
</item>
<item>
<title>Google Meet bots randomly quit meeting issue</title>
<description>
Type: Incident
Duration: 1 day, 2 hours and 24 minutes
Affected Components: Meeting Assistant
Jun 5, 12:23:39 GMT+0 - Resolved - This incident has been resolved. Jun 4, 10:00:00 GMT+0 - Identified - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 day, 2 hours and 24 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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>
]]>
</content:encoded>
<pubDate>Thu, 4 Jun 2026 10:00:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmq0pncgm0ciuparx9552mgdj</link>
<guid>https://meetgeek.instatus.com/incident/cmq0pncgm0ciuparx9552mgdj</guid>
</item>
<item>
<title>Google Meet Agent Joining Issues</title>
<description>
Type: Incident
Duration: 1 day and 14 hours
Affected Components: Meeting Assistant
Jun 3, 10:38:06 GMT+0 - Resolved - This incident has been resolved. Jun 3, 10:00:06 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 day and 14 hours</p>
<p><strong>Affected Components:</strong> </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>
<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>
]]>
</content:encoded>
<pubDate>Wed, 3 Jun 2026 10:00:06 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmpxyr9ab01zznwp2vfv79pzd</link>
<guid>https://meetgeek.instatus.com/incident/cmpxyr9ab01zznwp2vfv79pzd</guid>
</item>
<item>
<title>Service Disruption Notification</title>
<description>
Type: Incident
Affected Components: Meeting Assistant
Jan 29, 07:30:38 GMT+0 - Resolved - 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
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Affected Components:</strong> </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:encoded>
<pubDate>Thu, 29 Jan 2026 07:30:38 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmkz7yqr0084ijcrmwtx8dt2e</link>
<guid>https://meetgeek.instatus.com/incident/cmkz7yqr0084ijcrmwtx8dt2e</guid>
</item>
<item>
<title>Zoom bot fails to join meetings</title>
<description>
Type: Incident
Duration: 3 hours and 9 minutes
Affected Components: Meeting Assistant
Jan 12, 14:04:58 GMT+0 - Resolved - This incident has been resolved. Jan 12, 11:38:43 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 12, 10:55:56 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 3 hours and 9 minutes</p>
<p><strong>Affected Components:</strong> </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'>11:38:43</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</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>
]]>
</content:encoded>
<pubDate>Mon, 12 Jan 2026 10:55:56 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmkb1ro6k0ndlu3sgj0a3w9n5</link>
<guid>https://meetgeek.instatus.com/incident/cmkb1ro6k0ndlu3sgj0a3w9n5</guid>
</item>
<item>
<title>Issues with the meeting page not loading on the web app</title>
<description>
Type: Incident
Duration: 10 hours and 42 minutes
Affected Components: Web Dashboard
Oct 8, 07:19:00 GMT+0 - Resolved - This incident has been resolved. Oct 7, 21:42:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 10 hours and 42 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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>
]]>
</content:encoded>
<pubDate>Tue, 7 Oct 2025 21:42:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmghrav5i001nsptvykulqk2k</link>
<guid>https://meetgeek.instatus.com/incident/cmghrav5i001nsptvykulqk2k</guid>
</item>
<item>
<title>Degraded performance with the web and mobile apps and delays in analysis</title>
<description>
Type: Incident
Duration: 6 days, 5 hours and 15 minutes
Affected Components: Web Dashboard, Meeting Insights
Aug 27, 19:45:00 GMT+0 - Resolved - This incident has been resolved. Aug 21, 18:55:57 GMT+0 - Monitoring - 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. Aug 21, 14:30:00 GMT+0 - Investigating - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 6 days, 5 hours and 15 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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'> 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>
]]>
</content:encoded>
<pubDate>Thu, 21 Aug 2025 14:30:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmelo7oif000111xgq3dr45wf</link>
<guid>https://meetgeek.instatus.com/incident/cmelo7oif000111xgq3dr45wf</guid>
</item>
<item>
<title>Google Meet Bot not recording meetings</title>
<description>
Type: Incident
Duration: 1 day, 2 hours and 30 minutes
Affected Components: Meeting Assistant
Jul 23, 08:30:00 GMT+0 - Resolved - This incident has been resolved. Jul 23, 07:00:00 GMT+0 - Identified - We have identified the issue and we are working on a fix Jul 22, 06:00:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 day, 2 hours and 30 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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'> 22</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Tue, 22 Jul 2025 06:00:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmdfqwm6l00slehi03emkshn7</link>
<guid>https://meetgeek.instatus.com/incident/cmdfqwm6l00slehi03emkshn7</guid>
</item>
<item>
<title>Zoom bot transcript has missing speakers</title>
<description>
Type: Incident
Duration: 21 days, 12 hours and 11 minutes
Affected Components: Meeting Assistant
Jul 23, 09:10:53 GMT+0 - Resolved - This incident has been resolved. Jul 9, 08:21:00 GMT+0 - Identified - We have identified the issue and we are currently working on a fix. Jul 1, 21:00:00 GMT+0 - Investigating - There is an issue where the meetings recorded by the zoom bot do not provide the speakers
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 21 days, 12 hours and 11 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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'> 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>
]]>
</content:encoded>
<pubDate>Tue, 1 Jul 2025 21:00:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmd4aqiv300cfr4v8c93zzsxq</link>
<guid>https://meetgeek.instatus.com/incident/cmd4aqiv300cfr4v8c93zzsxq</guid>
</item>
<item>
<title>Microsoft Teams bot not joining</title>
<description>
Type: Incident
Duration: 5 days, 4 hours and 39 minutes
Affected Components: Meeting Assistant
Jun 18, 14:10:03 GMT+0 - Resolved - This incident has been resolved. Jun 13, 09:43:13 GMT+0 - Identified - 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; Jun 13, 09:31:01 GMT+0 - Identified - We are experiencing degraded performance with our Microsoft Teams Bots.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 5 days, 4 hours and 39 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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'> 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>
]]>
</content:encoded>
<pubDate>Fri, 13 Jun 2025 09:31:01 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmbuly1n2000jkogodr084kpk</link>
<guid>https://meetgeek.instatus.com/incident/cmbuly1n2000jkogodr084kpk</guid>
</item>
<item>
<title>Google Meet down</title>
<description>
Type: Incident
Duration: 1 hour and 18 minutes
Affected Components: Meeting Assistant
Jun 12, 20:04:05 GMT+0 - Resolved - This incident has been resolved. Jun 12, 18:45:49 GMT+0 - Identified - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 18 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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>
]]>
</content:encoded>
<pubDate>Thu, 12 Jun 2025 18:45:49 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmbtqbq03000jjmdrm1iekx0v</link>
<guid>https://meetgeek.instatus.com/incident/cmbtqbq03000jjmdrm1iekx0v</guid>
</item>
<item>
<title>Video not being recorded for Google Meet calls</title>
<description>
Type: Incident
Duration: 22 hours and 41 minutes
Affected Components: Meeting Assistant
Jun 11, 11:05:47 GMT+0 - Resolved - This incident has been resolved. Jun 10, 12:25:00 GMT+0 - Identified - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 22 hours and 41 minutes</p>
<p><strong>Affected Components:</strong> </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:encoded>
<pubDate>Tue, 10 Jun 2025 12:25:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmbrtw8b10001b5i5xx4dht2b</link>
<guid>https://meetgeek.instatus.com/incident/cmbrtw8b10001b5i5xx4dht2b</guid>
</item>
<item>
<title>Meeting Summary delayed or not arriving</title>
<description>
Type: Incident
Duration: 3 hours and 12 minutes
Affected Components: Meeting Insights, Meeting Assistant
Jun 10, 14:12:00 GMT+0 - Resolved - This incident has been resolved, and all the incomplete summaries and insights have been regenerated. Jun 10, 11:00:00 GMT+0 - Investigating - We are currently investigating an issue with meeting summaries going out or being delayed
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 3 hours and 12 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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>
]]>
</content:encoded>
<pubDate>Tue, 10 Jun 2025 11:00:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmbqmfasf000dnj1bdw28497n</link>
<guid>https://meetgeek.instatus.com/incident/cmbqmfasf000dnj1bdw28497n</guid>
</item>
<item>
<title>Long analysis time</title>
<description>
Type: Incident
Duration: 4 days, 16 hours and 37 minutes
Affected Components: Meeting Insights
May 23, 07:36:44 GMT+0 - Resolved - This incident has been resolved. May 20, 06:35:34 GMT+0 - Monitoring - 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. May 19, 20:14:08 GMT+0 - Identified - 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. May 18, 15:00:00 GMT+0 - Investigating - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 4 days, 16 hours and 37 minutes</p>
<p><strong>Affected Components:</strong> </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'> 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>
<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'> 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>
]]>
</content:encoded>
<pubDate>Sun, 18 May 2025 15:00:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cmavc1gt500fd11pirb6h8whr</link>
<guid>https://meetgeek.instatus.com/incident/cmavc1gt500fd11pirb6h8whr</guid>
</item>
<item>
<title>Long analysis time and missing transcripts</title>
<description>
Type: Incident
Duration: 2 days and 10 hours
Affected Components: Meeting Insights
May 2, 00:00:00 GMT+0 - Resolved - This incident has been resolved. Apr 29, 22:00:00 GMT+0 - Monitoring - 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. Apr 29, 14:00:00 GMT+0 - Investigating - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 2 days and 10 hours</p>
<p><strong>Affected Components:</strong> </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>
<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>
]]>
</content:encoded>
<pubDate>Tue, 29 Apr 2025 14:00:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cma2pe221002ft76bick9modd</link>
<guid>https://meetgeek.instatus.com/incident/cma2pe221002ft76bick9modd</guid>
</item>
<item>
<title>Elevated error rates</title>
<description>
Type: Incident
Duration: 1 hour and 25 minutes
Affected Components: Web Dashboard, Meeting Assistant, Meeting Insights, Public API
Apr 17, 16:45:00 GMT+0 - Resolved - 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. Apr 17, 15:20:00 GMT+0 - Identified - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 25 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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>
]]>
</content:encoded>
<pubDate>Thu, 17 Apr 2025 15:20:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cm9lo3qwm0094114ct0z1auo4</link>
<guid>https://meetgeek.instatus.com/incident/cm9lo3qwm0094114ct0z1auo4</guid>
</item>
<item>
<title>Teams bot dropping </title>
<description>
Type: Incident
Duration: 1 day, 5 hours and 25 minutes
Affected Components: Meeting Assistant
Mar 25, 16:26:00 GMT+0 - Resolved - This incident has been resolved. Mar 24, 16:26:57 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 24, 16:12:10 GMT+0 - Identified - Issue was identified. We are working on a fix. Mar 24, 11:01:21 GMT+0 - Investigating - We are currently investigating an incident where the teams bot sometimes drops from the call.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 day, 5 hours and 25 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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'> 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>
]]>
</content:encoded>
<pubDate>Mon, 24 Mar 2025 11:01:21 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cm8myid3q002tjy2cnl7m7i0w</link>
<guid>https://meetgeek.instatus.com/incident/cm8myid3q002tjy2cnl7m7i0w</guid>
</item>
<item>
<title>Incomplete summary &amp; insights</title>
<description>
Type: Incident
Duration: 6 days, 1 hour and 43 minutes
Affected Components: Meeting Assistant, Meeting Insights
Jan 13, 17:07:32 GMT+0 - Resolved - This incident has been resolved. Jan 12, 15:43:44 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 10, 12:34:12 GMT+0 - Monitoring - 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. Jan 9, 16:05:44 GMT+0 - Monitoring - 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. Jan 7, 15:25:00 GMT+0 - Investigating - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 6 days, 1 hour and 43 minutes</p>
<p><strong>Affected Components:</strong> </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'> 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>
<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'> 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'> 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>
]]>
</content:encoded>
<pubDate>Tue, 7 Jan 2025 15:25:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cm5o4a6i5000sl2h120nki1b7</link>
<guid>https://meetgeek.instatus.com/incident/cm5o4a6i5000sl2h120nki1b7</guid>
</item>
<item>
<title>Bot fails to join meetings</title>
<description>
Type: Incident
Duration: 1 hour and 7 minutes
Affected Components: Meeting Assistant
Dec 30, 17:01:57 GMT+0 - Monitoring - 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. Dec 30, 17:01:57 GMT+0 - Resolved - This incident has been resolved. Dec 30, 15:55:24 GMT+0 - Investigating - We are investigating reports where the bot is not joining some meetings.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 7 minutes</p>
<p><strong>Affected Components:</strong> </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'>17:01:57</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</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>
]]>
</content:encoded>
<pubDate>Mon, 30 Dec 2024 15:55:24 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cm5b80tbd00022l0sj6kk87sg</link>
<guid>https://meetgeek.instatus.com/incident/cm5b80tbd00022l0sj6kk87sg</guid>
</item>
<item>
<title>Teams bot not joining all calls</title>
<description>
Type: Incident
Duration: 1 day, 8 hours and 25 minutes
Affected Components: Meeting Assistant
Dec 19, 18:32:17 GMT+0 - Resolved - This incident has been resolved. Dec 19, 07:36:06 GMT+0 - Monitoring - We have deployed a fix and currently monitoring Dec 18, 10:25:20 GMT+0 - Identified - We have identified the issue and are working on a solution. Dec 18, 10:07:04 GMT+0 - Investigating - We are investigating reports where the teams bot is not joining some meetings.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 day, 8 hours and 25 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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'> 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'> 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>
]]>
</content:encoded>
<pubDate>Wed, 18 Dec 2024 10:07:04 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cm4tqan5u001pt8swfdqjar2r</link>
<guid>https://meetgeek.instatus.com/incident/cm4tqan5u001pt8swfdqjar2r</guid>
</item>
<item>
<title>Summary missing</title>
<description>
Type: Incident
Duration: 15 hours and 33 minutes
Affected Components: Meeting Assistant, Meeting Insights
Dec 12, 15:03:21 GMT+0 - Resolved - This incident has been resolved and all the missing summaries were successfully generated. Dec 11, 23:30:00 GMT+0 - Monitoring - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 15 hours and 33 minutes</p>
<p><strong>Affected Components:</strong> </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>
<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>
]]>
</content:encoded>
<pubDate>Wed, 11 Dec 2024 23:30:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cm4l6wrb3000x47w4iicp5och</link>
<guid>https://meetgeek.instatus.com/incident/cm4l6wrb3000x47w4iicp5och</guid>
</item>
<item>
<title>Issue with the summary email delivery</title>
<description>
Type: Incident
Duration: 21 hours and 46 minutes
Affected Components: Meeting Assistant
Dec 4, 13:30:54 GMT+0 - Resolved - This incident has been resolved. Dec 4, 13:25:05 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 3, 15:45:00 GMT+0 - Identified - 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.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 21 hours and 46 minutes</p>
<p><strong>Affected Components:</strong> </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'> 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>
<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>
]]>
</content:encoded>
<pubDate>Tue, 3 Dec 2024 15:45:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/incident/cm49w4t9100945ujki8uns3m5</link>
<guid>https://meetgeek.instatus.com/incident/cm49w4t9100945ujki8uns3m5</guid>
</item>
<item>
<title>Scheduled maintenance on Friday, 13th of January. Our services will be unavailable during 2PM - 6PM UTC.</title>
<description>
Type: Maintenance
Duration: 5 hours and 22 minutes
Affected Components: Meeting Insights, Web Dashboard, Meeting Assistant
Jan 13, 21:21:40 GMT+0 - Completed - Maintenance has been completed successfully. This time it is for real. :) Jan 13, 18:00:00 GMT+0 - Identified - Maintenance is almost done. Jan 13, 17:00:00 GMT+0 - Identified - Our services will be unavailable during 2PM - 6PM UTC time for planned service maintenance. Jan 13, 17:00:00 GMT+0 - Identified - Maintenance is now in progress Jan 13, 16:00:01 GMT+0 - Identified - Maintenance is not completed yet.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 5 hours and 22 minutes</p>
<p><strong>Affected Components:</strong> </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'>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'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</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>
]]>
</content:encoded>
<pubDate>Fri, 13 Jan 2023 17:00:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/maintenance/clcq2tcs370725poomtv54pqgj</link>
<guid>https://meetgeek.instatus.com/maintenance/clcq2tcs370725poomtv54pqgj</guid>
</item>
<item>
<title>Scheduled maintenance for 9-12 CET, 3rd of November 2022</title>
<description>
Type: Maintenance
Duration: 3 hours
Affected Components: Meeting Insights, Web Dashboard, Meeting Assistant
Nov 3, 12:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 3, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 3, 09:00:00 GMT+0 - Identified - We are going to perform a scheduled maintenance during 9-12 CET, the 3rd of November 2022
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 3 hours</p>
<p><strong>Affected Components:</strong> </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>
<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'>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>
]]>
</content:encoded>
<pubDate>Thu, 3 Nov 2022 09:00:00 +0000</pubDate>
<link>https://meetgeek.instatus.com/maintenance/cl9zd8z8l0714j7ohwvzl973y</link>
<guid>https://meetgeek.instatus.com/maintenance/cl9zd8z8l0714j7ohwvzl973y</guid>
</item>
</channel>
</rss>