Snapshot 300208

Document
Registry listing
URL
https://status.fibery.io/history.rss
Fetched
HTTP status
200
Content type
text/xml
Fetch mode
api
Size
35172 bytes
SHA-256 (raw)
1f309769e8a29c8d6cd99839323a44583ab6c314980c9d67686268c2b9de157a
SHA-256 (normalized text)
fc0c1c42171e634aeaa17dd7a106c43453e8b8abac10146fcec449530f9294b4

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>Fibery Status - Incident history</title>
<link>https://status.fibery.io</link>
<description>Fibery</description>
<pubDate>Wed, 18 Nov 2026 14:14:33 +0000</pubDate>
<item>
<title>Partial outage</title>
<description>
Type: Incident
Duration: 1 hour and 36 minutes
Affected Components: Automations, Application, Collaborative Documents, Application, Automations, Search, Collaborative Documents, Live Updates, Integrations, Search, API, API, Website, Integrations, Live Updates, Reports, Reports
Nov 18, 15:50:38 GMT+0 - Resolved - This incident is resolved. Workspaces, integrations, AI features and MCP are working normally.
Between 13:30 and 15:35 UTC, the main database ran out of memory, which caused slow loading and errors, followed by a full outage from 14:08 to 14:31 UTC while the database was restarted. AI features and MCP were additionally unavailable from 14:57 to 15:33 UTC. Workspaces hosted in our US and UK regions were not affected, apart from delayed integrations and AI.
We have changed how the application manages its database connections to prevent this from recurring, and we are continuing to monitor. We&#039;re sorry for the disruption. Nov 18, 14:44:16 GMT+0 - Monitoring - Workspaces are loading normally again. The database is back online and the services affected by the restart have recovered.
Some integrations (email and Intercom sync) and AI features may still be delayed while they catch up. We are monitoring and will post another update within 30 minutes. Nov 18, 14:24:53 GMT+0 - Identified - We have identified a database problem as the cause. Most workspaces are currently unavailable or returning errors. Workspaces hosted in our US and UK regions are not affected.
We have rolled back a recent change and are restarting the database. We expect service to start recovering within the next few minutes, and it may be slow for a short while after that.
Next update within 15 minutes. Nov 18, 14:14:33 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 36 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>15:50:38</var> GMT+0</small><br><strong>Resolved</strong> -
This incident is resolved. Workspaces, integrations, AI features and MCP are working normally.
Between 13:30 and 15:35 UTC, the main database ran out of memory, which caused slow loading and errors, followed by a full outage from 14:08 to 14:31 UTC while the database was restarted. AI features and MCP were additionally unavailable from 14:57 to 15:33 UTC. Workspaces hosted in our US and UK regions were not affected, apart from delayed integrations and AI.
We have changed how the application manages its database connections to prevent this from recurring, and we are continuing to monitor. We&#039;re sorry for the disruption..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:44:16</var> GMT+0</small><br><strong>Monitoring</strong> -
Workspaces are loading normally again. The database is back online and the services affected by the restart have recovered.
Some integrations (email and Intercom sync) and AI features may still be delayed while they catch up. We are monitoring and will post another update within 30 minutes..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:24:53</var> GMT+0</small><br><strong>Identified</strong> -
We have identified a database problem as the cause. Most workspaces are currently unavailable or returning errors. Workspaces hosted in our US and UK regions are not affected.
We have rolled back a recent change and are restarting the database. We expect service to start recovering within the next few minutes, and it may be slow for a short while after that.
Next update within 15 minutes..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:14:33</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Wed, 18 Nov 2026 14:14:33 +0000</pubDate>
<link>https://status.fibery.io/incident/cmwm7d71800zj1nnt9rtbsud8</link>
<guid>https://status.fibery.io/incident/cmwm7d71800zj1nnt9rtbsud8</guid>
</item>
<item>
<title>Notifications</title>
<description>
Type: Incident
Duration: 1 hour and 3 minutes
Affected Components: Application
Sep 2, 19:03:13 GMT+0 - Resolved - This incident has been resolved. Sep 2, 18:39:38 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 2, 18:00:23 GMT+0 - Investigating - We are investigating delays in notification delivery. Some users may not receive notifications in a timely manner.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 3 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>19:03:13</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'>18:39:38</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>18:00:23</var> GMT+0</small><br><strong>Investigating</strong> -
We are investigating delays in notification delivery. Some users may not receive notifications in a timely manner..</p>
]]>
</content:encoded>
<pubDate>Wed, 2 Sep 2026 18:00:23 +0000</pubDate>
<link>https://status.fibery.io/incident/cmtkej14n02mi1nqt2m1k8m6f</link>
<guid>https://status.fibery.io/incident/cmtkej14n02mi1nqt2m1k8m6f</guid>
</item>
<item>
<title>Degraded performance</title>
<description>
Type: Incident
Duration: 1 hour and 55 minutes
Affected Components: Application
Sep 2, 09:00:00 GMT+0 - Resolved - This incident has been resolved. We experienced elevated database load, which caused degraded performance for all users. We identified the issue as a combination of background formula processing and API client activity, and took steps to mitigate the load. Performance has since returned to normal. Sep 2, 07:05: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 hour and 55 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved. We experienced elevated database load, which caused degraded performance for all users. We identified the issue as a combination of background formula processing and API client activity, and took steps to mitigate the load. Performance has since returned to normal..</p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>07:05:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Wed, 2 Sep 2026 07:05:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cmtjxsrwb0ryg1bmvo9yzt3f4</link>
<guid>https://status.fibery.io/incident/cmtjxsrwb0ryg1bmvo9yzt3f4</guid>
</item>
<item>
<title>Degraded performance in EU region</title>
<description>
Type: Incident
Duration: 9 minutes
Affected Components: Collaborative Documents, Automations, Search, API, Application, Integrations, Live Updates, Reports
Aug 25, 08:10:00 GMT+0 - Resolved - Error rates returned to normal at 08:10 UTC. Root cause: an internal background maintenance job coinciding with a spike in write activity overloaded the database. We have reconfigured the maintenance job and deployed an index fix to prevent recurrence. Aug 25, 08:01:00 GMT+0 - Identified - We are seeing elevated error rates and slow responses for workspaces in the EU region due to increased database load. US and UK regions are not affected.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 9 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>08:10:00</var> GMT+0</small><br><strong>Resolved</strong> -
Error rates returned to normal at 08:10 UTC. Root cause: an internal background maintenance job coinciding with a spike in write activity overloaded the database. We have reconfigured the maintenance job and deployed an index fix to prevent recurrence..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>08:01:00</var> GMT+0</small><br><strong>Identified</strong> -
We are seeing elevated error rates and slow responses for workspaces in the EU region due to increased database load. US and UK regions are not affected..</p>
]]>
</content:encoded>
<pubDate>Tue, 25 Aug 2026 08:01:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cmt9xree00ikm1bp2y774mvaf</link>
<guid>https://status.fibery.io/incident/cmt9xree00ikm1bp2y774mvaf</guid>
</item>
<item>
<title>App fails to load or takes a longer time</title>
<description>
Type: Incident
Duration: 2 hours and 23 minutes
Affected Components: Collaborative Documents, Automations, Search, API, Application, Integrations, Live Updates, Reports
Jul 16, 12:18:03 GMT+0 - Resolved - This incident has been resolved. Jul 16, 11:26:51 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 16, 09:55:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 2 hours and 23 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>12:18:03</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>11:26:51</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>09:55:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Thu, 16 Jul 2026 09:55:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cmrnf49jd09sf0zp0l92h2ih6</link>
<guid>https://status.fibery.io/incident/cmrnf49jd09sf0zp0l92h2ih6</guid>
</item>
<item>
<title>Degraded Performance Across Integrations, Automations and Reports</title>
<description>
Type: Incident
Duration: 18 hours and 58 minutes
Affected Components: Automations, Integrations, Reports
Jun 25, 02:58:03 GMT+0 - Resolved - This incident has been resolved. Jun 24, 09:20:00 GMT+0 - Identified - We are continuing to work on a fix for this incident.
Integrations are temporarily operating in read-only mode Jun 24, 08: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> 18 hours and 58 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>02:58:03</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>09:20:00</var> GMT+0</small><br><strong>Identified</strong> -
We are continuing to work on a fix for this incident.
Integrations are temporarily operating in read-only mode.</p>
<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident. .</p>
]]>
</content:encoded>
<pubDate>Wed, 24 Jun 2026 08:00:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cmqrvsgt200dt2io3o9dg756z</link>
<guid>https://status.fibery.io/incident/cmqrvsgt200dt2io3o9dg756z</guid>
</item>
<item>
<title>Fibery is down</title>
<description>
Type: Incident
Duration: 21 minutes
Affected Components: Collaborative Documents, Application, Automations, Search, Automations, Collaborative Documents, Live Updates, Integrations, API, Search, API, Integrations, Website, Live Updates, Application
Feb 24, 11:18:20 GMT+0 - Resolved - This incident has been resolved. Postmortem will follow... Feb 24, 10:57:47 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 21 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>11:18:20</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved. Postmortem will follow... .</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>10:57:47</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Tue, 24 Feb 2026 10:57:47 +0000</pubDate>
<link>https://status.fibery.io/incident/cmm0hrpph023cpyib0o0ee6za</link>
<guid>https://status.fibery.io/incident/cmm0hrpph023cpyib0o0ee6za</guid>
</item>
<item>
<title>Views service overload leading to application unavailability</title>
<description>
Type: Incident
Duration: 15 hours
Affected Components: Application
Jan 5, 09:13:00 GMT+0 - Resolved - This incident has been resolved. Jan 5, 08:58:00 GMT+0 - Identified -
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 15 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>09:13:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>08:58:00</var> GMT+0</small><br><strong>Identified</strong> -
.</p>
]]>
</content:encoded>
<pubDate>Mon, 5 Jan 2026 08:58:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cmk190fpi000heyk7fw2fav7q</link>
<guid>https://status.fibery.io/incident/cmk190fpi000heyk7fw2fav7q</guid>
</item>
<item>
<title>Search functionality outage</title>
<description>
Type: Incident
Duration: 1 hour and 30 minutes
Affected Components: Search
Jun 4, 18:49:58 GMT+0 - Resolved - This incident has been resolved. Jun 4, 17:20:00 GMT+0 - Identified - We are working on a fix for this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 30 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>18:49:58</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'>17:20:00</var> GMT+0</small><br><strong>Identified</strong> -
We are working on a fix for this incident..</p>
]]>
</content:encoded>
<pubDate>Wed, 4 Jun 2025 17:20:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cmbi9hcto000q14fsafft8k6r</link>
<guid>https://status.fibery.io/incident/cmbi9hcto000q14fsafft8k6r</guid>
</item>
<item>
<title>Search functionality outage</title>
<description>
Type: Incident
Duration: 2 hours and 8 minutes
Affected Components: Search
Jan 17, 16:43:00 GMT+0 - Resolved - This incident has been resolved. Jan 17, 14:35:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 2 hours and 8 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>16:43:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>14:35:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Fri, 17 Jan 2025 14:35:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cm613pnm6003a88a1g6cnjcil</link>
<guid>https://status.fibery.io/incident/cm613pnm6003a88a1g6cnjcil</guid>
</item>
<item>
<title>Search functionality outage: no results being returned</title>
<description>
Type: Incident
Duration: 1 hour
Affected Components: Search
Nov 26, 20:02:24 GMT+0 - Resolved - This incident has been resolved. Nov 26, 19:02:47 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 26</var>, <var data-var='time'>20:02:24</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 26</var>, <var data-var='time'>19:02:47</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Tue, 26 Nov 2024 19:02:47 +0000</pubDate>
<link>https://status.fibery.io/incident/cm3ytqun5000gf5n7e7uo9yc9</link>
<guid>https://status.fibery.io/incident/cm3ytqun5000gf5n7e7uo9yc9</guid>
</item>
<item>
<title>Integrations are down. All new synchronisations are &quot;Timed out&quot;</title>
<description>
Type: Incident
Duration: 18 hours and 15 minutes
Affected Components: Integrations, Integrations
Nov 7, 06:45:08 GMT+0 - Resolved - This incident has been resolved. Nov 6, 17:29:42 GMT+0 - Monitoring - Integrations should work now. Monitoring Nov 6, 12:30:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 18 hours and 15 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>06:45:08</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>17:29:42</var> GMT+0</small><br><strong>Monitoring</strong> -
Integrations should work now. Monitoring.</p>
<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Wed, 6 Nov 2024 12:30:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cm364ik74000398imfo0psnpc</link>
<guid>https://status.fibery.io/incident/cm364ik74000398imfo0psnpc</guid>
</item>
<item>
<title>Fibery is down :-(</title>
<description>
Type: Incident
Duration: 1 hour
Affected Components: API, API, Integrations, Website, Live Updates, Collaborative Documents, Application, Application, Automations, Search, Search, Collaborative Documents, Live Updates, Automations, Integrations
Jul 2, 09:56:00 GMT+0 - Resolved - This incident has been resolved. Jul 2, 09:00:00 GMT+0 - Identified - Root cause identified. Working on a fix Jul 2, 08:56:00 GMT+0 - Investigating - We are currently investigating.
Some workspaces have returned to normal, but root cause still to be confirmed.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>09:56:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> -
Root cause identified. Working on a fix.</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>08:56:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating.
Some workspaces have returned to normal, but root cause still to be confirmed..</p>
]]>
</content:encoded>
<pubDate>Tue, 2 Jul 2024 08:56:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cly47uyav72038b3mvidm901d6</link>
<guid>https://status.fibery.io/incident/cly47uyav72038b3mvidm901d6</guid>
</item>
<item>
<title>Service disruption in Live updates</title>
<description>
Type: Incident
Duration: 54 minutes
Affected Components: Live Updates
Jun 26, 12:10:00 GMT+0 - Resolved - This incident has been resolved. Jun 26, 11:16:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 54 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>12:10:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>11:16:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Wed, 26 Jun 2024 11:16:00 +0000</pubDate>
<link>https://status.fibery.io/incident/clxvrpkqa39662bhood5cypdry</link>
<guid>https://status.fibery.io/incident/clxvrpkqa39662bhood5cypdry</guid>
</item>
<item>
<title>App fails to load or takes a longer time</title>
<description>
Type: Incident
Duration: 20 minutes
Affected Components: Application
Mar 4, 13:15:00 GMT+0 - Resolved - This incident has been resolved. Mar 4, 12:55:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 20 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>13:15:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>12:55:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Mon, 4 Mar 2024 12:55:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cltcymcnk92250ban738xjaivq</link>
<guid>https://status.fibery.io/incident/cltcymcnk92250ban738xjaivq</guid>
</item>
<item>
<title>Collaborative Documents partial outage</title>
<description>
Type: Incident
Duration: 24 minutes
Affected Components: Collaborative Documents
Dec 20, 14:47:00 GMT+0 - Resolved - This incident has been resolved. Dec 20, 14:23:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 24 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>14:47:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>14:23:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Wed, 20 Dec 2023 14:23:00 +0000</pubDate>
<link>https://status.fibery.io/incident/clqdwtts24078b7lmw6quajz1</link>
<guid>https://status.fibery.io/incident/clqdwtts24078b7lmw6quajz1</guid>
</item>
<item>
<title>Intermittent errors when accessing application</title>
<description>
Type: Incident
Duration: 3 days and 11 hours
Affected Components: API, Application
Nov 16, 12:40:00 GMT+0 - Resolved - This incident has been resolved. Nov 16, 11:17:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 3 days and 11 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>12:40:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>11:17:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Thu, 16 Nov 2023 11:17:00 +0000</pubDate>
<link>https://status.fibery.io/incident/clp165wsz57158b7n63y0lb869</link>
<guid>https://status.fibery.io/incident/clp165wsz57158b7n63y0lb869</guid>
</item>
<item>
<title>🚨 Fibery is down for all customers</title>
<description>
Type: Incident
Duration: 1 day and 21 hours
Affected Components: API, Integrations, Live Updates, Collaborative Documents, Application, Automations, Search
Sep 5, 14:15:00 GMT+0 - Resolved - This incident has been resolved.
Here is the detailed postmortem https://fibery.io/blog/downtime-postmortem-core/
Sep 5, 13:30: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 and 21 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>14:15:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved.
Here is the detailed postmortem https://fibery.io/blog/downtime-postmortem-core/
.</p>
<p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Tue, 5 Sep 2023 13:30:00 +0000</pubDate>
<link>https://status.fibery.io/incident/clm6ckjzx8975bbn30atadofx</link>
<guid>https://status.fibery.io/incident/clm6ckjzx8975bbn30atadofx</guid>
</item>
<item>
<title>Collaborative documents periodically fail to load</title>
<description>
Type: Incident
Duration: 20 minutes
Affected Components: Collaborative Documents
Aug 28, 07:55:00 GMT+0 - Resolved - This incident has been resolved. Aug 28, 07:35:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 20 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>07:55:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>07:35:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Mon, 28 Aug 2023 07:35:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cllum30n663203bqokgksueyll</link>
<guid>https://status.fibery.io/incident/cllum30n663203bqokgksueyll</guid>
</item>
<item>
<title>Collaborative Documents are periodically not loaded</title>
<description>
Type: Incident
Duration: 25 days and 14 hours
Affected Components: Collaborative Documents
Aug 21, 20:36:00 GMT+0 - Resolved - This incident has been resolved. Aug 21, 10:22:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 25 days and 14 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>20:36: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'>10:22:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Mon, 21 Aug 2023 10:22:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cllm0vt7327912bbotyre1n55y</link>
<guid>https://status.fibery.io/incident/cllm0vt7327912bbotyre1n55y</guid>
</item>
<item>
<title>Fibery is down due to expired SSL certificate (Embarrassing…)</title>
<description>
Type: Incident
Duration: 19 minutes
Affected Components: API, Live Updates, Collaborative Documents, Application, API, Integrations, Application, Automations, Website, Integrations, Search, Search, Collaborative Documents, Live Updates, Automations
May 5, 06:52:09 GMT+0 - Resolved - All should be fine now.
This was a humiliating incident for us.
We&#039;ll take actions to not repeat it for sure, but the embarrassment will live in us forever. May 5, 06:32:51 GMT+0 - Investigating - We are currently working on it. Should be up in 10 mins.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 19 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>May <var data-var='date'> 5</var>, <var data-var='time'>06:52:09</var> GMT+0</small><br><strong>Resolved</strong> -
All should be fine now.
This was a humiliating incident for us.
We&#039;ll take actions to not repeat it for sure, but the embarrassment will live in us forever. .</p>
<p><small>May <var data-var='date'> 5</var>, <var data-var='time'>06:32:51</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently working on it. Should be up in 10 mins..</p>
]]>
</content:encoded>
<pubDate>Fri, 5 May 2023 06:32:51 +0000</pubDate>
<link>https://status.fibery.io/incident/clha6j0ey357800brn1gvi3pcai</link>
<guid>https://status.fibery.io/incident/clha6j0ey357800brn1gvi3pcai</guid>
</item>
<item>
<title>Search doesn&#039;t return results for some workspaces</title>
<description>
Type: Incident
Duration: 2 hours and 54 minutes
Affected Components: Search
Mar 27, 20:35:58 GMT+0 - Resolved - This incident has been resolved. Mar 27, 17:41:56 GMT+0 - Identified - 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 54 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>20:35:58</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>17:41:56</var> GMT+0</small><br><strong>Identified</strong> -
We are continuing to work on a fix for this incident..</p>
]]>
</content:encoded>
<pubDate>Mon, 27 Mar 2023 17:41:56 +0000</pubDate>
<link>https://status.fibery.io/incident/clfr497t042663406ontp6v0ufk</link>
<guid>https://status.fibery.io/incident/clfr497t042663406ontp6v0ufk</guid>
</item>
<item>
<title>Performance is degraded for some requests</title>
<description>
Type: Incident
Affected Components: Application
Feb 22, 16:12:51 GMT+0 - Resolved - We just resolved the issue!
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>16:12:51</var> GMT+0</small><br><strong>Resolved</strong> -
We just resolved the issue!.</p>
]]>
</content:encoded>
<pubDate>Wed, 22 Feb 2023 16:12:51 +0000</pubDate>
<link>https://status.fibery.io/incident/clefvjj0w32811845mx2kvipv2o</link>
<guid>https://status.fibery.io/incident/clefvjj0w32811845mx2kvipv2o</guid>
</item>
<item>
<title>Linked fields updates are delayed</title>
<description>
Type: Incident
Duration: 2 days, 11 hours and 4 minutes
Affected Components: Automations
Jan 27, 10:24:00 GMT+0 - Resolved - We just resolved the issue!
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 2 days, 11 hours and 4 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>10:24:00</var> GMT+0</small><br><strong>Resolved</strong> -
We just resolved the issue!.</p>
]]>
</content:encoded>
<pubDate>Fri, 27 Jan 2023 10:24:00 +0000</pubDate>
<link>https://status.fibery.io/incident/cldebitfi436212inn11g1qn3x1</link>
<guid>https://status.fibery.io/incident/cldebitfi436212inn11g1qn3x1</guid>
</item>
<item>
<title>Search is down</title>
<description>
Type: Incident
Duration: 3 hours and 18 minutes
Affected Components: Search
Jan 9, 20:11:34 GMT+0 - Resolved - We just resolved the issue! Jan 9, 20:10:22 GMT+0 - Resolved - We just resolved the issue! Jan 9, 16:52:22 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 18 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>20:11:34</var> GMT+0</small><br><strong>Resolved</strong> -
We just resolved the issue!.</p>
<p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>20:10:22</var> GMT+0</small><br><strong>Resolved</strong> -
We just resolved the issue!.</p>
<p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>16:52:22</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Mon, 9 Jan 2023 16:52:22 +0000</pubDate>
<link>https://status.fibery.io/incident/clcp1kw5o2251hmokz9l8f2wq</link>
<guid>https://status.fibery.io/incident/clcp1kw5o2251hmokz9l8f2wq</guid>
</item>
</channel>
</rss>