mastodon.social Status - Incident history https://status.mastodon.social mastodon.social Wed, 25 Feb 2026 21:08:32 +0000 Hetzner Outage Type: Incident Duration: 27 minutes Affected Components: Website & API, Streaming API, Background queues Feb 25, 21:08:32 GMT+0 - Investigating - Hetzner, our cloud provider, appears to be having a significant outage, leaving many of our resources unavailable. We are monitoring the issue. Feb 25, 21:16:30 GMT+0 - Monitoring - Services have been restored and Hetzner connectivity seems to have returned. Will continue to monitor the situation. Feb 25, 21:35:12 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 27 minutes

Affected Components: , ,

<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:08:32</var> GMT+0</small><br><strong>Investigating</strong> - Hetzner, our cloud provider, appears to be having a significant outage, leaving many of our resources unavailable. We are monitoring the issue..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:16:30</var> GMT+0</small><br><strong>Monitoring</strong> - Services have been restored and Hetzner connectivity seems to have returned. Will continue to monitor the situation..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:35:12</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 25 Feb 2026 21:08:32 +0000 https://status.mastodon.social/incident/cmm2j0zlx0hkf9d6cvtyjzqe6 https://status.mastodon.social/incident/cmm2j0zlx0hkf9d6cvtyjzqe6 Connectivity/timeout issues with sidekiq Type: Incident Duration: 12 days, 18 hours and 22 minutes Affected Components: Website & API, Background queues Dec 17, 14:00:00 GMT+0 - Investigating - There appears to be an issue with connection timeouts to our Sidekiq runners, causing some operations to take longer than expected, or require multiple tries. We are currently investigating this issue. Jan 7, 06:42:57 GMT+0 - Monitoring - We found out the cause for this issue (within a dependency) and we deployed a fix 8 hours ago. So far, it seems to have completely fixed the issue. Mar 30, 08:22:20 GMT+0 - Resolved - Sidekiq has been stable, so considering this incident resolved. Type: Incident

Duration: 12 days, 18 hours and 22 minutes

Affected Components: ,

<p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Investigating</strong> - There appears to be an issue with connection timeouts to our Sidekiq runners, causing some operations to take longer than expected, or require multiple tries. We are currently investigating this issue..</p> <p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>06:42:57</var> GMT+0</small><br><strong>Monitoring</strong> - We found out the cause for this issue (within a dependency) and we deployed a fix 8 hours ago. So far, it seems to have completely fixed the issue..</p> <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>08:22:20</var> GMT+0</small><br><strong>Resolved</strong> - Sidekiq has been stable, so considering this incident resolved..</p> ]]> Wed, 17 Dec 2025 14:00:00 +0000 https://status.mastodon.social/incident/cmk1b5pf4026zxderxh5yval0 https://status.mastodon.social/incident/cmk1b5pf4026zxderxh5yval0 Website is down due to database issue Type: Incident Duration: 8 minutes Affected Components: Website & API, Background queues Nov 3, 17:20:27 GMT+0 - Identified - [mastodon.social](http://mastodon.social) is currently unresponsive to a database issue. We identified the problem and are working on fixing it. Nov 3, 17:28:47 GMT+0 - Resolved - This incident has been resolved, everything is now operational again. Type: Incident

Duration: 8 minutes

Affected Components: ,

<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>17:20:27</var> GMT+0</small><br><strong>Identified</strong> - [mastodon.social](http://mastodon.social) is currently unresponsive to a database issue. We identified the problem and are working on fixing it..</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>17:28:47</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved, everything is now operational again..</p> ]]> Mon, 3 Nov 2025 17:20:27 +0000 https://status.mastodon.social/incident/cmhjeojvb01fo8zjj8t4tysee https://status.mastodon.social/incident/cmhjeojvb01fo8zjj8t4tysee Emails from mastodon.social are paused Type: Incident Duration: 6 days, 2 hours and 35 minutes Jun 17, 13:50:20 GMT+0 - Identified - We paused sending emails from [mastodon.social](http://mastodon.social) (including password recovery and account confirmation emails) due to an identified issue that sent duplicate emails about our upcoming Terms of Service changes to some users. We are working on fixing this and avoiding more duplicate emails to be sent. Jun 17, 17:42:30 GMT+0 - Monitoring - Email sending has been removed. Servers are working through the backlog, and any pending email should arrive in the next few hours. Jun 18, 05:40:36 GMT+0 - Identified - The backlog of emails has been sent, and emails are reaching out their recipients now. Some emails sent in the last 12 hours are stuck with our email provider and we are working with them to fix this situation. Jun 23, 16:25:19 GMT+0 - Resolved - This incident has been resolved last Thursday, and email have been delivered correctly since then. Type: Incident

Duration: 6 days, 2 hours and 35 minutes

<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>13:50:20</var> GMT+0</small><br><strong>Identified</strong> - We paused sending emails from [mastodon.social](http://mastodon.social) (including password recovery and account confirmation emails) due to an identified issue that sent duplicate emails about our upcoming Terms of Service changes to some users. We are working on fixing this and avoiding more duplicate emails to be sent..</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>17:42:30</var> GMT+0</small><br><strong>Monitoring</strong> - Email sending has been removed. Servers are working through the backlog, and any pending email should arrive in the next few hours..</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>05:40:36</var> GMT+0</small><br><strong>Identified</strong> - The backlog of emails has been sent, and emails are reaching out their recipients now. Some emails sent in the last 12 hours are stuck with our email provider and we are working with them to fix this situation..</p> <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>16:25:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved last Thursday, and email have been delivered correctly since then..</p> ]]> Tue, 17 Jun 2025 13:50:20 +0000 https://status.mastodon.social/incident/cmc0kyye700073b4lbd7st2rs https://status.mastodon.social/incident/cmc0kyye700073b4lbd7st2rs Backend outage Type: Incident Duration: 2 hours and 40 minutes Affected Components: Website & API, Background queues Jun 11, 22:33:26 GMT+0 - Investigating - We are experiencing issues with our redis caching system, as well as kubernetes node errors. We are currently investigating the issue. Jun 11, 22:42:52 GMT+0 - Identified - Website is operative again. Issue seems to be related to kubernetes pods becoming completely unresponsive. Continuing to investigate. Jun 12, 01:13:29 GMT+0 - Resolved - Kubernetes node issues have been resolved, and service is now fully restored. Type: Incident

Duration: 2 hours and 40 minutes

Affected Components: ,

<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>22:33:26</var> GMT+0</small><br><strong>Investigating</strong> - We are experiencing issues with our redis caching system, as well as kubernetes node errors. We are currently investigating the issue..</p> <p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>22:42:52</var> GMT+0</small><br><strong>Identified</strong> - Website is operative again. Issue seems to be related to kubernetes pods becoming completely unresponsive. Continuing to investigate..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>01:13:29</var> GMT+0</small><br><strong>Resolved</strong> - Kubernetes node issues have been resolved, and service is now fully restored..</p> ]]> Wed, 11 Jun 2025 22:33:26 +0000 https://status.mastodon.social/incident/cmbsj0lyj001vk18tyxzcm5jd https://status.mastodon.social/incident/cmbsj0lyj001vk18tyxzcm5jd Database minor upgrade Type: Maintenance Duration: 16 minutes Affected Components: Background queues, Website & API May 28, 06:30:01 GMT+0 - Identified - Maintenance is now in progress May 28, 06:30:00 GMT+0 - Identified - We will be updating the database to the next minor version, as well as some OS components that will require a restart. Minor downtime of roughly a minute is expected. May 28, 06:46:24 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 16 minutes

Affected Components: ,

<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>06:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>06:30:00</var> GMT+0</small><br><strong>Identified</strong> - We will be updating the database to the next minor version, as well as some OS components that will require a restart. Minor downtime of roughly a minute is expected..</p> <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>06:46:24</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Wed, 28 May 2025 06:30:00 +0000 https://status.mastodon.social/maintenance/cmb6pa33o0003biacj5vv3l9x https://status.mastodon.social/maintenance/cmb6pa33o0003biacj5vv3l9x Degraded performance Type: Incident Duration: 11 days, 20 hours and 41 minutes Affected Components: Website & API Jan 29, 16:49:03 GMT+0 - Investigating - We are currently investigating this incident. Jan 29, 17:30:58 GMT+0 - Identified - We've experienced an issue with our recent cache storage upgrade, causing some ephermal data loss (e.g. home feeds losing scrollback or showing the number of active users as "0"). We are working on fixing the underlying issue and restoring/regenerating the lost data. Feb 10, 13:30:27 GMT+0 - Resolved - Data has been restored, and performance issues have been mitigated. Type: Incident

Duration: 11 days, 20 hours and 41 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>16:49:03</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>17:30:58</var> GMT+0</small><br><strong>Identified</strong> - We've experienced an issue with our recent cache storage upgrade, causing some ephermal data loss (e.g. home feeds losing scrollback or showing the number of active users as "0"). We are working on fixing the underlying issue and restoring/regenerating the lost data..</p> <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>13:30:27</var> GMT+0</small><br><strong>Resolved</strong> - Data has been restored, and performance issues have been mitigated..</p> ]]> Wed, 29 Jan 2025 16:49:03 +0000 https://status.mastodon.social/incident/cm6i55duu000ijwc2g6f4t3kx https://status.mastodon.social/incident/cm6i55duu000ijwc2g6f4t3kx Timelines are not updating with some clients Type: Incident Duration: 8 days, 1 hour and 45 minutes Affected Components: Website & API Feb 5, 14:39:41 GMT+0 - Resolved - This incident has been resolved. Jan 28, 12:55:00 GMT+0 - Identified - Last week, we switched our Redis database to another software. This led to user reports of timelines not updating anymore with using some clients, like Ivory or Pachli. After investigating the issue, we discovered that this new software returns invalid data in some specific cases, which are triggered by the API those Mastodon clients use. We have reached out to the software developers to troubleshoot this and are hopeful it will get fixed soon. In the meantime, we are also working on a way to roll back to our previous software in case we can not get this fixed quickly. We will post more details on this incident when possible. Feb 4, 17:06:12 GMT+0 - Monitoring - The database software developer has been very responsive about this issue. They helped us troubleshoot it and provided us with a new version that solved the problem. We are currently monitoring the system closely, but everything seems to work fine now. Type: Incident

Duration: 8 days, 1 hour and 45 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>14:39:41</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>12:55:00</var> GMT+0</small><br><strong>Identified</strong> - Last week, we switched our Redis database to another software. This led to user reports of timelines not updating anymore with using some clients, like Ivory or Pachli. After investigating the issue, we discovered that this new software returns invalid data in some specific cases, which are triggered by the API those Mastodon clients use. We have reached out to the software developers to troubleshoot this and are hopeful it will get fixed soon. In the meantime, we are also working on a way to roll back to our previous software in case we can not get this fixed quickly. We will post more details on this incident when possible..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>17:06:12</var> GMT+0</small><br><strong>Monitoring</strong> - The database software developer has been very responsive about this issue. They helped us troubleshoot it and provided us with a new version that solved the problem. We are currently monitoring the system closely, but everything seems to work fine now..</p> ]]> Tue, 28 Jan 2025 12:55:00 +0000 https://status.mastodon.social/incident/cm6pd181500253mteulhfvsbu https://status.mastodon.social/incident/cm6pd181500253mteulhfvsbu Website inaccessible Type: Incident Duration: 30 minutes Affected Components: Website & API Jan 25, 08:43:04 GMT+0 - Resolved - This incident has been resolved. Jan 25, 08:12:40 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 30 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 25</var>, <var data-var='time'>08:43:04</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 25</var>, <var data-var='time'>08:12:40</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Sat, 25 Jan 2025 08:12:40 +0000 https://status.mastodon.social/incident/cm6bwxw860009uenp4biudu3w https://status.mastodon.social/incident/cm6bwxw860009uenp4biudu3w Database upgrade Type: Maintenance Duration: 2 hours and 44 minutes Affected Components: Streaming API, Media storage, Background queues, Website & API Jan 21, 09:00:00 GMT+0 - Identified - We will be upgrading the database systems to new hardware, as well as a new major version of PostgreSQL. The upgrade should be very quick, but some small downtime will still occur for around a minute. Jan 21, 09:31:23 GMT+0 - Identified - Maintenance is now in progress. Jan 21, 09:57:20 GMT+0 - Identified - We encountered a configuration issue while performing the update. We are working on a fix and the service should be back online soon. Jan 21, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 21, 11:00:54 GMT+0 - Identified - The upgrade was successful and [mastodon.social](http://mastodon.social) is now running on the newer database servers. There is a small delay in processing due to the backlog of request accumulated during our downtime, but everything should be back to real-time soon. We are closely monitoring the servers and will update this status once everything is back to normal. Jan 21, 11:44:00 GMT+0 - Completed - Database is successfully upgraded, all configuration errors have been cleaned up. Thank you to everyone for your patience. Type: Maintenance

Duration: 2 hours and 44 minutes

Affected Components: , , ,

<p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - We will be upgrading the database systems to new hardware, as well as a new major version of PostgreSQL. The upgrade should be very quick, but some small downtime will still occur for around a minute..</p> <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>09:31:23</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>09:57:20</var> GMT+0</small><br><strong>Identified</strong> - We encountered a configuration issue while performing the update. We are working on a fix and the service should be back online soon..</p> <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>11:00:54</var> GMT+0</small><br><strong>Identified</strong> - The upgrade was successful and [mastodon.social](http://mastodon.social) is now running on the newer database servers. There is a small delay in processing due to the backlog of request accumulated during our downtime, but everything should be back to real-time soon. We are closely monitoring the servers and will update this status once everything is back to normal..</p> <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>11:44:00</var> GMT+0</small><br><strong>Completed</strong> - Database is successfully upgraded, all configuration errors have been cleaned up. Thank you to everyone for your patience..</p> ]]> Tue, 21 Jan 2025 09:00:00 +0000 https://status.mastodon.social/maintenance/cm657sgnf000lbclskf50nowh https://status.mastodon.social/maintenance/cm657sgnf000lbclskf50nowh Backend DB connection issues Type: Incident Duration: 2 hours and 55 minutes Affected Components: Website & API Jan 16, 07:13:58 GMT+0 - Investigating - There appears to be an issue with our nodes connecting to the DB reliably. We are currently investigating the issue. Jan 16, 07:18:39 GMT+0 - Monitoring - DB connections are stable again. Current suspect is a Hetzner networking issue somewhere in the backend. Currently monitoring. Jan 16, 10:09:20 GMT+0 - Resolved - No acknowledgement from Hetzner, but everything remains stable. Considering this closed. Type: Incident

Duration: 2 hours and 55 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 16</var>, <var data-var='time'>07:13:58</var> GMT+0</small><br><strong>Investigating</strong> - There appears to be an issue with our nodes connecting to the DB reliably. We are currently investigating the issue..</p> <p><small>Jan <var data-var='date'> 16</var>, <var data-var='time'>07:18:39</var> GMT+0</small><br><strong>Monitoring</strong> - DB connections are stable again. Current suspect is a Hetzner networking issue somewhere in the backend. Currently monitoring..</p> <p><small>Jan <var data-var='date'> 16</var>, <var data-var='time'>10:09:20</var> GMT+0</small><br><strong>Resolved</strong> - No acknowledgement from Hetzner, but everything remains stable. Considering this closed..</p> ]]> Thu, 16 Jan 2025 07:13:58 +0000 https://status.mastodon.social/incident/cm5yzvq3z0074125f369yguvr https://status.mastodon.social/incident/cm5yzvq3z0074125f369yguvr Server autoscaling/capacity issues Type: Incident Duration: 18 hours and 31 minutes Affected Components: Streaming API, Background queues, Website & API Nov 13, 16:17:05 GMT+0 - Identified - There was an issue with our cluster autoscaler where it seems to have scaled down the number of nodes we have for our cluster, resulting in strained resources. We are trying to scale back up, but Hetzner is having availability issues in the region we are deployed in. We are working to resolve the issue as quickly as possible. Nov 14, 10:48:00 GMT+0 - Resolved - Capacity issues have been resolved, and the autoscaler has been adjusted. Type: Incident

Duration: 18 hours and 31 minutes

Affected Components: , ,

<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>16:17:05</var> GMT+0</small><br><strong>Identified</strong> - There was an issue with our cluster autoscaler where it seems to have scaled down the number of nodes we have for our cluster, resulting in strained resources. We are trying to scale back up, but Hetzner is having availability issues in the region we are deployed in. We are working to resolve the issue as quickly as possible..</p> <p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>10:48:00</var> GMT+0</small><br><strong>Resolved</strong> - Capacity issues have been resolved, and the autoscaler has been adjusted..</p> ]]> Wed, 13 Nov 2024 16:17:05 +0000 https://status.mastodon.social/incident/cm3g33nly000c16ctjz2hvrd9 https://status.mastodon.social/incident/cm3g33nly000c16ctjz2hvrd9 Email sending unavailable Type: Incident Duration: 3 hours and 13 minutes Affected Components: Background queues Sep 16, 06:50:00 GMT+0 - Investigating - We are currently unable to send emails to users due to issues with Postmark. We are currently investigating the issue. Sep 16, 10:02:51 GMT+0 - Resolved - Issue was identified as an SSL error on Postmark's side. This has now been resolved, and emails are working again. Type: Incident

Duration: 3 hours and 13 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>06:50:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently unable to send emails to users due to issues with Postmark. We are currently investigating the issue..</p> <p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>10:02:51</var> GMT+0</small><br><strong>Resolved</strong> - Issue was identified as an SSL error on Postmark's side. This has now been resolved, and emails are working again..</p> ]]> Mon, 16 Sep 2024 06:50:00 +0000 https://status.mastodon.social/incident/cm14naznz003ef63gke9k0zes https://status.mastodon.social/incident/cm14naznz003ef63gke9k0zes Degraded performance Type: Incident Duration: 4 minutes Affected Components: Website & API Mar 15, 19:11:51 GMT+0 - Identified - We've identified an inefficient database query in the most recent update and are performing a rollback to last good version. Sorry for the inconvenience. Mar 15, 19:15:52 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 4 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>19:11:51</var> GMT+0</small><br><strong>Identified</strong> - We've identified an inefficient database query in the most recent update and are performing a rollback to last good version. Sorry for the inconvenience..</p> <p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>19:15:52</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 15 Mar 2024 19:11:51 +0000 https://status.mastodon.social/incident/cltt1cfl193555b3mu0h0osn8u https://status.mastodon.social/incident/cltt1cfl193555b3mu0h0osn8u Database connection issue Type: Incident Duration: 7 hours and 48 minutes Affected Components: Background queues, Website & API Mar 12, 12:20:54 GMT+0 - Investigating - We are currently experiencing an issue connecting to the database. Investigation is ongoing. Mar 12, 12:31:04 GMT+0 - Identified - Confirmed that Hetzner is experiencing an outage with their vSwitches, which we are using for our database connection. We will continue to monitor. <https://status.hetzner.com/incident/9406c500-9c8b-48be-9591-a73691134096> Mar 12, 12:44:58 GMT+0 - Monitoring - Database connectivity is restored. Continuing to monitor the situation while the Hetzner status remains open. Mar 12, 15:06:13 GMT+0 - Identified - Our hosting provider is having a network issue again, causing [mastodon.social](http://mastodon.social) to be unavailable. We are monitoring the situation to ensure everything comes back online as soon as the network is working again. Mar 12, 15:39:56 GMT+0 - Monitoring - The network issue has been fixed by our provider and all services are back online. We are monitoring the situation, but Hetzner has not yet announced that the underlying issue is fixed, so it may break again. Mar 12, 20:08:41 GMT+0 - Resolved - Our provider identified the source of the network issues. It was caused by a router bug, and they have been able to update them to a new version that fixes the issue. Type: Incident

Duration: 7 hours and 48 minutes

Affected Components: ,

<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>12:20:54</var> GMT+0</small><br><strong>Investigating</strong> - We are currently experiencing an issue connecting to the database. Investigation is ongoing..</p> <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>12:31:04</var> GMT+0</small><br><strong>Identified</strong> - Confirmed that Hetzner is experiencing an outage with their vSwitches, which we are using for our database connection. We will continue to monitor. <https://status.hetzner.com/incident/9406c500-9c8b-48be-9591-a73691134096>.</p> <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>12:44:58</var> GMT+0</small><br><strong>Monitoring</strong> - Database connectivity is restored. Continuing to monitor the situation while the Hetzner status remains open..</p> <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>15:06:13</var> GMT+0</small><br><strong>Identified</strong> - Our hosting provider is having a network issue again, causing [mastodon.social](http://mastodon.social) to be unavailable. We are monitoring the situation to ensure everything comes back online as soon as the network is working again..</p> <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>15:39:56</var> GMT+0</small><br><strong>Monitoring</strong> - The network issue has been fixed by our provider and all services are back online. We are monitoring the situation, but Hetzner has not yet announced that the underlying issue is fixed, so it may break again..</p> <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>20:08:41</var> GMT+0</small><br><strong>Resolved</strong> - Our provider identified the source of the network issues. It was caused by a router bug, and they have been able to update them to a new version that fixes the issue..</p> ]]> Tue, 12 Mar 2024 12:20:54 +0000 https://status.mastodon.social/incident/cltoccdbh80789b4od4h0vq10f https://status.mastodon.social/incident/cltoccdbh80789b4od4h0vq10f Switch fault Type: Incident Duration: 3 minutes Affected Components: Streaming API, Background queues, Website & API Jan 22, 23:13:23 GMT+0 - Resolved - The fault has been fixed. Jan 22, 23:10:41 GMT+0 - Investigating - We were notified of a switch fault in the data center of our hosting provider. Type: Incident

Duration: 3 minutes

Affected Components: , ,

<p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>23:13:23</var> GMT+0</small><br><strong>Resolved</strong> - The fault has been fixed..</p> <p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>23:10:41</var> GMT+0</small><br><strong>Investigating</strong> - We were notified of a switch fault in the data center of our hosting provider..</p> ]]> Mon, 22 Jan 2024 23:10:41 +0000 https://status.mastodon.social/incident/clrpjjeke80192asoepc8bbo9e https://status.mastodon.social/incident/clrpjjeke80192asoepc8bbo9e Search is temporarily unavailable Type: Incident Duration: 4 hours and 37 minutes Affected Components: Website & API Jan 15, 05:42:06 GMT+0 - Investigating - We are currently investigating this incident. Jan 15, 09:02:24 GMT+0 - Identified - Issues has been discovered; one of the indexes was behaving in strange ways and causing regular errors/retries. After recreating the index, cluster is now behaving as expected. Index is currently rebuilding from current data. Jan 15, 10:18:43 GMT+0 - Resolved - Elasticsearch indexes have rebuilt and search is working as intended. Type: Incident

Duration: 4 hours and 37 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>05:42:06</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>09:02:24</var> GMT+0</small><br><strong>Identified</strong> - Issues has been discovered; one of the indexes was behaving in strange ways and causing regular errors/retries. After recreating the index, cluster is now behaving as expected. Index is currently rebuilding from current data..</p> <p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>10:18:43</var> GMT+0</small><br><strong>Resolved</strong> - Elasticsearch indexes have rebuilt and search is working as intended..</p> ]]> Mon, 15 Jan 2024 05:42:06 +0000 https://status.mastodon.social/incident/clrehzyo9270166brn5o8ei9z2b https://status.mastodon.social/incident/clrehzyo9270166brn5o8ei9z2b Degraded performance Type: Incident Duration: 6 hours and 52 minutes Affected Components: Website & API Jan 3, 05:53:52 GMT+0 - Investigating - We are currently investigating this incident. Jan 3, 12:46:10 GMT+0 - Resolved - Performance issues were a combination of a suspected spam attack, and some imbalance with the kubernetes nodes. Spam sources have been blocked and nodes have been rebalanced. Type: Incident

Duration: 6 hours and 52 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>05:53:52</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>12:46:10</var> GMT+0</small><br><strong>Resolved</strong> - Performance issues were a combination of a suspected spam attack, and some imbalance with the kubernetes nodes. Spam sources have been blocked and nodes have been rebalanced..</p> ]]> Wed, 3 Jan 2024 05:53:52 +0000 https://status.mastodon.social/incident/clqxd4vkv196186brojhlyognrm https://status.mastodon.social/incident/clqxd4vkv196186brojhlyognrm Degrated performance Type: Incident Duration: 15 days, 23 hours and 33 minutes Affected Components: Background queues, Website & API Oct 27, 10:56:45 GMT+0 - Identified - The situation is now stable and services are working, but the performance is not back to the previous levels. The problem seems to be tied to the kernel version we are running, which may not have full support for the new hardware we deployed. We are working on updating our systems to a newer OS version and tuning the various system settings to ensure everything goes back to expected levels of performance. Dec 12, 14:52:41 GMT+0 - Resolved - Performance has improved after upgrading various OS packages, and upgrading kubernetes to more recent versions with performance improvements. Additional work is still ongoing to identify other areas where performance can be improved, but current performance is now better than it was. Oct 26, 15:19:35 GMT+0 - Investigating - There appears to be degraded performance after a move away from deprecated Hetzner nodes types. Currently investigating. Oct 26, 18:54:43 GMT+0 - Investigating - Definite cause of the degradation has yet to be identified, however moving to more powerful nodes for the time being seems to have mitigated the issue. Sidekiq queues are still behind, but are no longer growing, and additional workers have been deployed to help it catch up. A ticket has been submitted with Hetzner to see if this could be an issue on their side. Waiting to hear back. Type: Incident

Duration: 15 days, 23 hours and 33 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>10:56:45</var> GMT+0</small><br><strong>Identified</strong> - The situation is now stable and services are working, but the performance is not back to the previous levels. The problem seems to be tied to the kernel version we are running, which may not have full support for the new hardware we deployed. We are working on updating our systems to a newer OS version and tuning the various system settings to ensure everything goes back to expected levels of performance..</p> <p><small>Dec <var data-var='date'> 12</var>, <var data-var='time'>14:52:41</var> GMT+0</small><br><strong>Resolved</strong> - Performance has improved after upgrading various OS packages, and upgrading kubernetes to more recent versions with performance improvements. Additional work is still ongoing to identify other areas where performance can be improved, but current performance is now better than it was..</p> <p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>15:19:35</var> GMT+0</small><br><strong>Investigating</strong> - There appears to be degraded performance after a move away from deprecated Hetzner nodes types. Currently investigating. .</p> <p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>18:54:43</var> GMT+0</small><br><strong>Investigating</strong> - Definite cause of the degradation has yet to be identified, however moving to more powerful nodes for the time being seems to have mitigated the issue. Sidekiq queues are still behind, but are no longer growing, and additional workers have been deployed to help it catch up. A ticket has been submitted with Hetzner to see if this could be an issue on their side. Waiting to hear back..</p> ]]> Thu, 26 Oct 2023 15:19:35 +0000 https://status.mastodon.social/incident/clo7bym1333504b8mvbbwiphcn https://status.mastodon.social/incident/clo7bym1333504b8mvbbwiphcn Database hardware switch Type: Maintenance Duration: 16 minutes Affected Components: Background queues, Website & API Aug 8, 10:30:01 GMT+0 - Identified - Maintenance is now in progress Aug 8, 10:30:00 GMT+0 - Identified - We will be switching the database over to newer, more powerful hardware. This is a simple connection switch, so there should be minimal downtime. Aug 8, 10:45:57 GMT+0 - Completed - Database switch is finished. New hardware is working nicely. Type: Maintenance

Duration: 16 minutes

Affected Components: ,

<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>10:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>10:30:00</var> GMT+0</small><br><strong>Identified</strong> - We will be switching the database over to newer, more powerful hardware. This is a simple connection switch, so there should be minimal downtime..</p> <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>10:45:57</var> GMT+0</small><br><strong>Completed</strong> - Database switch is finished. New hardware is working nicely..</p> ]]> Tue, 8 Aug 2023 10:30:00 +0000 https://status.mastodon.social/maintenance/cll0vf4dz4048beoe4sl7ar91 https://status.mastodon.social/maintenance/cll0vf4dz4048beoe4sl7ar91 High database load Type: Incident Duration: 1 hour Affected Components: Background queues, Website & API Aug 5, 18:59:23 GMT+0 - Investigating - We are experiencing an abnormal database load. We are currently investigating this incident. Aug 5, 19:14:42 GMT+0 - Identified - The drive array on our main database server seems to be having issues. You may experience some pages failing to load. Posts from other instances are also experiencing some delay as we are limiting their processing to get the database back at full speed. Aug 5, 19:59:49 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour

Affected Components: ,

<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>18:59:23</var> GMT+0</small><br><strong>Investigating</strong> - We are experiencing an abnormal database load. We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>19:14:42</var> GMT+0</small><br><strong>Identified</strong> - The drive array on our main database server seems to be having issues. You may experience some pages failing to load. Posts from other instances are also experiencing some delay as we are limiting their processing to get the database back at full speed..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>19:59:49</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 5 Aug 2023 18:59:23 +0000 https://status.mastodon.social/incident/clkydpfbp5859bnomvmgihs0z https://status.mastodon.social/incident/clkydpfbp5859bnomvmgihs0z Search is temporarily unavailable Type: Incident Duration: 1 day Affected Components: Website & API Aug 3, 15:14:00 GMT+0 - Resolved - This incident has been resolved. Aug 2, 15:14:05 GMT+0 - Identified - We've identified an issue with our search engine. While autocomplete still works, searching for posts currently doesn't. We're working on a solution. Aug 2, 19:16:14 GMT+0 - Monitoring - The search feature is back after a recovery procedure, but we will deploy a new infrastructure for it tomorrow to avoid any future issues. Type: Incident

Duration: 1 day

Affected Components:

<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>15:14:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>15:14:05</var> GMT+0</small><br><strong>Identified</strong> - We've identified an issue with our search engine. While autocomplete still works, searching for posts currently doesn't. We're working on a solution..</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>19:16:14</var> GMT+0</small><br><strong>Monitoring</strong> - The search feature is back after a recovery procedure, but we will deploy a new infrastructure for it tomorrow to avoid any future issues..</p> ]]> Wed, 2 Aug 2023 15:14:05 +0000 https://status.mastodon.social/incident/clktvc5hm15169beoc641mb1pl https://status.mastodon.social/incident/clktvc5hm15169beoc641mb1pl Database upgrade Type: Maintenance Duration: 1 hour and 7 minutes Affected Components: Background queues, Website & API Jul 12, 13:52:41 GMT+0 - Identified - Starting a little earlier, as the old database is having some issues anyway. Jul 12, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Jul 12, 14:00:00 GMT+0 - Identified - We will be performing a major database upgrade on the backend. We've created a process to minimize downtime, however there will still be some downtime during the process (est. 15-20 minutes). Type: Maintenance

Duration: 1 hour and 7 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>13:52:41</var> GMT+0</small><br><strong>Identified</strong> - Starting a little earlier, as the old database is having some issues anyway..</p> <p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> - We will be performing a major database upgrade on the backend. We've created a process to minimize downtime, however there will still be some downtime during the process (est. 15-20 minutes)..</p> ]]> Wed, 12 Jul 2023 14:00:00 +0000 https://status.mastodon.social/maintenance/cljyh1es253594aelrzqqqwa0z https://status.mastodon.social/maintenance/cljyh1es253594aelrzqqqwa0z Website is down Type: Incident Duration: 2 hours and 10 minutes Affected Components: Streaming API, Website & API Jul 9, 12:24:18 GMT+0 - Investigating - We are currently investigating this incident. Jul 9, 12:30:02 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 9, 14:34:41 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 10 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>12:24:18</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>12:30:02</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'> 9</var>, <var data-var='time'>14:34:41</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 9 Jul 2023 12:24:18 +0000 https://status.mastodon.social/incident/cljvepcxg60590b3ohw0x07dqs https://status.mastodon.social/incident/cljvepcxg60590b3ohw0x07dqs Website is down Type: Incident Duration: 3 hours and 1 minute Affected Components: Streaming API, Website & API Jul 8, 18:13:32 GMT+0 - Identified - We've identified an issue with the database server and are working on remedying it. Jul 8, 19:07:47 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 8, 21:14:11 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 1 minute

Affected Components: ,

<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>18:13:32</var> GMT+0</small><br><strong>Identified</strong> - We've identified an issue with the database server and are working on remedying it..</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>19:07:47</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'> 8</var>, <var data-var='time'>21:14:11</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 8 Jul 2023 18:13:32 +0000 https://status.mastodon.social/incident/cljubqlox70474bbn2r9op5wj4 https://status.mastodon.social/incident/cljubqlox70474bbn2r9op5wj4 High database load Type: Incident Duration: 5 hours and 56 minutes Affected Components: Background queues, Website & API Jul 6, 19:03:08 GMT+0 - Investigating - The database is currently experience extremely high load. We are currently investigating the cause. Jul 6, 19:42:34 GMT+0 - Identified - The increase in database load is likely the result of significantly increased user traffic over the last several days, revealing inefficiencies in some of our database background jobs. We are implementing fixes, both temporary and long-term. Jul 6, 19:59:21 GMT+0 - Monitoring - Database performance has returned to normal. Jul 7, 00:58:54 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 5 hours and 56 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>19:03:08</var> GMT+0</small><br><strong>Investigating</strong> - The database is currently experience extremely high load. We are currently investigating the cause..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>19:42:34</var> GMT+0</small><br><strong>Identified</strong> - The increase in database load is likely the result of significantly increased user traffic over the last several days, revealing inefficiencies in some of our database background jobs. We are implementing fixes, both temporary and long-term..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>19:59:21</var> GMT+0</small><br><strong>Monitoring</strong> - Database performance has returned to normal..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>00:58:54</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 6 Jul 2023 19:03:08 +0000 https://status.mastodon.social/incident/cljrimp0g421786bdolk3fxa85e https://status.mastodon.social/incident/cljrimp0g421786bdolk3fxa85e Database server experiencing issues Type: Incident Duration: 1 hour and 45 minutes Affected Components: Background queues, Website & API Jul 6, 05:29:06 GMT+0 - Resolved - This incident has been resolved. Jul 6, 03:44:15 GMT+0 - Investigating - The database server appears to be experiencing an issue. Active investigation is underway. Jul 6, 03:48:10 GMT+0 - Monitoring - Database is back up & running. Type: Incident

Duration: 1 hour and 45 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>05:29:06</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>03:44:15</var> GMT+0</small><br><strong>Investigating</strong> - The database server appears to be experiencing an issue. Active investigation is underway..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>03:48:10</var> GMT+0</small><br><strong>Monitoring</strong> - Database is back up & running..</p> ]]> Thu, 6 Jul 2023 03:44:15 +0000 https://status.mastodon.social/incident/cljqlszx890732bhomzqu7trdg https://status.mastodon.social/incident/cljqlszx890732bhomzqu7trdg Under heavy load Type: Incident Duration: 1 day, 20 hours and 23 minutes Affected Components: Background queues, Website & API Jul 1, 19:51:01 GMT+0 - Monitoring - We are experiencing a higher-than-average number of active users, and performance may be slightly degraded as a result. Jul 2, 08:20:29 GMT+0 - Investigating - Additional DB resources have been added to help ease the load. Performance should steadily return to normal as background tasks catch up. The rapid influx of new users caused us to exceed our email sending limit, and as such emails are no longer being delivered. We are currently working on extending these limits. Jul 2, 15:28:18 GMT+0 - Monitoring - We switched to a new email provider and our backlog of emails (Subscription confirmation, password reset emails…) is shrinking and should be back to normal in the coming hours. Additional resources and optimisation have been deployed to help with the web services, we are still seeing some errors but the situation should be much better now. There is still a significant delay on statuses processing, but we hope the new resources will help getting it under control. Jul 2, 22:25:24 GMT+0 - Monitoring - All pending e-mails have now been delivered and new emails (on sign-up or password reset for example) are properly delivered. We are still lagging behind on ingesting content from other Mastodon servers, but this is resorbing and we expect to be back to normal in a few hours. The load on our infrastructure is closely monitored and we are working on various optimisations to better handle this newload, as well as adding more compute power to our infrastructure. Jul 3, 16:14:24 GMT+0 - Resolved - All queues are caught up, and performance is currently stable. Type: Incident

Duration: 1 day, 20 hours and 23 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>19:51:01</var> GMT+0</small><br><strong>Monitoring</strong> - We are experiencing a higher-than-average number of active users, and performance may be slightly degraded as a result..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>08:20:29</var> GMT+0</small><br><strong>Investigating</strong> - Additional DB resources have been added to help ease the load. Performance should steadily return to normal as background tasks catch up. The rapid influx of new users caused us to exceed our email sending limit, and as such emails are no longer being delivered. We are currently working on extending these limits..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>15:28:18</var> GMT+0</small><br><strong>Monitoring</strong> - We switched to a new email provider and our backlog of emails (Subscription confirmation, password reset emails…) is shrinking and should be back to normal in the coming hours. Additional resources and optimisation have been deployed to help with the web services, we are still seeing some errors but the situation should be much better now. There is still a significant delay on statuses processing, but we hope the new resources will help getting it under control..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>22:25:24</var> GMT+0</small><br><strong>Monitoring</strong> - All pending e-mails have now been delivered and new emails (on sign-up or password reset for example) are properly delivered. We are still lagging behind on ingesting content from other Mastodon servers, but this is resorbing and we expect to be back to normal in a few hours. The load on our infrastructure is closely monitored and we are working on various optimisations to better handle this newload, as well as adding more compute power to our infrastructure..</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>16:14:24</var> GMT+0</small><br><strong>Resolved</strong> - All queues are caught up, and performance is currently stable..</p> ]]> Sat, 1 Jul 2023 19:51:01 +0000 https://status.mastodon.social/incident/cljkf4zxl51738b8oig21tdd4r https://status.mastodon.social/incident/cljkf4zxl51738b8oig21tdd4r Processing backlog Type: Incident Duration: 33 minutes Affected Components: Background queues Jun 1, 19:52:59 GMT+0 - Identified - We've identified a backlog of items in our processing queue which means that some posts will appear only with a delay. We are working on resolving the issue. Jun 1, 20:26:17 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 33 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>19:52:59</var> GMT+0</small><br><strong>Identified</strong> - We've identified a backlog of items in our processing queue which means that some posts will appear only with a delay. We are working on resolving the issue..</p> <p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>20:26:17</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 1 Jun 2023 19:52:59 +0000 https://status.mastodon.social/incident/clidjzzf9206487byoi56k0vp74 https://status.mastodon.social/incident/clidjzzf9206487byoi56k0vp74 Media files will be moved to a new CDN Type: Maintenance Duration: 1 hour and 39 minutes Affected Components: Media storage Feb 3, 08:57:30 GMT+0 - Identified - DNS has been switched to the new provider. We are monitoring the service. Feb 3, 08:30:00 GMT+0 - Identified - We are moving our media files (files.mastodon.social) to a new CDN provider. There should be no downtime or visible impact. Feb 3, 10:08:42 GMT+0 - Completed - No issues have been observed, the migration is now complete. Type: Maintenance

Duration: 1 hour and 39 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>08:57:30</var> GMT+0</small><br><strong>Identified</strong> - DNS has been switched to the new provider. We are monitoring the service..</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are moving our media files (files.mastodon.social) to a new CDN provider. There should be no downtime or visible impact..</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>10:08:42</var> GMT+0</small><br><strong>Completed</strong> - No issues have been observed, the migration is now complete..</p> ]]> Fri, 3 Feb 2023 08:30:00 +0000 https://status.mastodon.social/maintenance/cldo9e6bk116753gmn3tj4sjy71 https://status.mastodon.social/maintenance/cldo9e6bk116753gmn3tj4sjy71