Pipe Platform Status - Incident history https://addpipe.instatus.com Pipe Platform Tue, 10 Mar 2026 08:15:00 +0000 Maintenance window announced by our upstream cloud provider (Hetzner) Type: Maintenance Duration: 4 days, 11 hours and 46 minutes Affected Components: EU2 Ingestion Server, US1 Ingestion Server, US2 Ingestion Server, REST API V1, CA1 Ingestion Server, Recording Client, CA1 Processing Server, US2 Processing Server, , US1 Processing Server, , EU2 Processing Server, Account Dashboard, Database, Ingestion Servers → Processing Servers → Mar 10, 08:15:00 GMT+0 - Identified - We have been notified by one of our core cloud infrastructure providers, [Hetzner](https://www.hetzner.com/), about a scheduled maintenance operation affecting central network components in their cloud environment. During their maintenance period, cloud servers and volumes connected to the respective network component will be unreachable. Unfortunately, this will impact the database that powers the Pipe Platform making it unavailable during the operation. As a result, the Pipe Platform will be temporarily unavailable during the separate maintenance window below. **Maintenance window** Start: Tuesday, March 10, 2026 – 08:15 UTC Estimated end: Tuesday, March 10, 2026 – 10:15 UTC **Expected impact** During this window: • The Pipe recording client will display a temporarily unavailable message. • The Pipe account dashboard will be inaccessible. • The Pipe REST API will not be available. Our previous scheduled downtime occurred in July 2025. We apologize for the inconvenience and appreciate your understanding while this maintenance is carried out by our supplier. If you have any questions or concerns, please contact our support team at [support@addpipe.com](mailto:support@addpipe.com). PS: our provider's status report for this maintenance window can be followed [here](https://status.hetzner.com/incident/4faff75c-3f38-4f9d-962c-a52273dc841a). Mar 10, 08:15:01 GMT+0 - Identified - Maintenance is now in progress Mar 10, 10:02:45 GMT+0 - Completed - Maintenance has completed successfully. All systems are live. Type: Maintenance

Duration: 4 days, 11 hours and 46 minutes

Affected Components: , , , , , , , , , , , , ,

<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>08:15:00</var> GMT+0</small><br><strong>Identified</strong> - We have been notified by one of our core cloud infrastructure providers, [Hetzner](https://www.hetzner.com/), about a scheduled maintenance operation affecting central network components in their cloud environment. During their maintenance period, cloud servers and volumes connected to the respective network component will be unreachable. Unfortunately, this will impact the database that powers the Pipe Platform making it unavailable during the operation. As a result, the Pipe Platform will be temporarily unavailable during the separate maintenance window below. **Maintenance window** Start: Tuesday, March 10, 2026 – 08:15 UTC Estimated end: Tuesday, March 10, 2026 – 10:15 UTC **Expected impact** During this window: • The Pipe recording client will display a temporarily unavailable message. • The Pipe account dashboard will be inaccessible. • The Pipe REST API will not be available. Our previous scheduled downtime occurred in July 2025. We apologize for the inconvenience and appreciate your understanding while this maintenance is carried out by our supplier. If you have any questions or concerns, please contact our support team at [support@addpipe.com](mailto:support@addpipe.com). PS: our provider's status report for this maintenance window can be followed [here](https://status.hetzner.com/incident/4faff75c-3f38-4f9d-962c-a52273dc841a)..</p> <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>08:15:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>10:02:45</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully. All systems are live..</p> ]]> Tue, 10 Mar 2026 08:15:00 +0000 https://addpipe.instatus.com/maintenance/cmmk9otjm07u6k5jd9bt9b0f9 https://addpipe.instatus.com/maintenance/cmmk9otjm07u6k5jd9bt9b0f9 Network issues with our cloud provider Type: Incident Duration: 1 hour and 13 minutes Affected Components: EU2 Ingestion Server, US1 Ingestion Server, CA1 Processing Server, US2 Ingestion Server, Recording Client, CA1 Ingestion Server, US2 Processing Server, , US1 Processing Server, , EU2 Processing Server, Account Dashboard, Database, Ingestion Servers → Processing Servers → Oct 27, 10:23:33 GMT+0 - Identified - Our cloud provider is experiencing network issues, which may hinder the performance of the Pipe platform Oct 27, 10:25:59 GMT+0 - Monitoring - We've contacted the cloud provider's support, and are continuing to monitor the situation Oct 27, 11:36:51 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 13 minutes

Affected Components: , , , , , , , , , , , ,

<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>10:23:33</var> GMT+0</small><br><strong>Identified</strong> - Our cloud provider is experiencing network issues, which may hinder the performance of the Pipe platform.</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>10:25:59</var> GMT+0</small><br><strong>Monitoring</strong> - We've contacted the cloud provider's support, and are continuing to monitor the situation.</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>11:36:51</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 27 Oct 2025 10:23:33 +0000 https://addpipe.instatus.com/incident/cmh8zpgnt00uxsfsgxly0isbn https://addpipe.instatus.com/incident/cmh8zpgnt00uxsfsgxly0isbn We are currently experiencing issues with our cloud provider Hetzner. Type: Incident Duration: 16 minutes Affected Components: , CA1 Processing Server, , US1 Processing Server, EU2 Ingestion Server, US1 Ingestion Server, EU2 Processing Server, US2 Processing Server, US2 Ingestion Server, REST API V1, Recording Client, Database, CA1 Ingestion Server, Account Dashboard, Ingestion Servers → Processing Servers → Oct 15, 08:46:45 GMT+0 - Resolved - Hetzner announced that the issue has been resolved. All systems should be operational again. Oct 15, 08:33:22 GMT+0 - Monitoring - Monitoring the situation Oct 15, 08:30:30 GMT+0 - Identified - We are in direct communication with them and monitoring the situation. Please bear with us. As soon as more information is available will update. Recording client will be put into maintenance to avoid issues with a huge backlog of recordings. Type: Incident

Duration: 16 minutes

Affected Components: , , , , , , , , , , , , ,

<p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>08:46:45</var> GMT+0</small><br><strong>Resolved</strong> - Hetzner announced that the issue has been resolved. All systems should be operational again..</p> <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>08:33:22</var> GMT+0</small><br><strong>Monitoring</strong> - Monitoring the situation.</p> <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>08:30:30</var> GMT+0</small><br><strong>Identified</strong> - We are in direct communication with them and monitoring the situation. Please bear with us. As soon as more information is available will update. Recording client will be put into maintenance to avoid issues with a huge backlog of recordings..</p> ]]> Wed, 15 Oct 2025 08:30:30 +0000 https://addpipe.instatus.com/incident/cmgrqdusz00o42jfxnqccct1s https://addpipe.instatus.com/incident/cmgrqdusz00o42jfxnqccct1s There is currently a network disruption at the cloud location of our Hetzner provider Type: Incident Duration: 3 hours and 46 minutes Affected Components: , CA1 Processing Server, , US1 Processing Server, EU2 Ingestion Server, US1 Ingestion Server, EU2 Processing Server, US2 Processing Server, US2 Ingestion Server, REST API V1, Recording Client, Database, CA1 Ingestion Server, Account Dashboard, Ingestion Servers → Processing Servers → Oct 14, 07:52:00 GMT+0 - Monitoring - We are currently monitoring the incident. Oct 14, 08:52:00 GMT+0 - Monitoring - Hetzner cloud servers and load balancers are affected. Networks of the affected cloud servers were also unavailable. As a result, we're forced to put our recording client into maintenance to avoid a huge backlog of recordings being created Oct 14, 09:01:03 GMT+0 - Monitoring - Systems are accessible again. Still monitoring the situation Oct 14, 09:20:51 GMT+0 - Monitoring - Still experiencing degraded performance. Monitoring the situation Oct 14, 10:01:04 GMT+0 - Monitoring - Some of the cloud resources of our Hetzner provider are still affected by the outage. Some of our systems may continue to experience degraded performance. Oct 14, 11:37:47 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 46 minutes

Affected Components: , , , , , , , , , , , , ,

<p><small>Oct <var data-var='date'> 14</var>, <var data-var='time'>07:52:00</var> GMT+0</small><br><strong>Monitoring</strong> - We are currently monitoring the incident..</p> <p><small>Oct <var data-var='date'> 14</var>, <var data-var='time'>08:52:00</var> GMT+0</small><br><strong>Monitoring</strong> - Hetzner cloud servers and load balancers are affected. Networks of the affected cloud servers were also unavailable. As a result, we're forced to put our recording client into maintenance to avoid a huge backlog of recordings being created.</p> <p><small>Oct <var data-var='date'> 14</var>, <var data-var='time'>09:01:03</var> GMT+0</small><br><strong>Monitoring</strong> - Systems are accessible again. Still monitoring the situation.</p> <p><small>Oct <var data-var='date'> 14</var>, <var data-var='time'>09:20:51</var> GMT+0</small><br><strong>Monitoring</strong> - Still experiencing degraded performance. Monitoring the situation.</p> <p><small>Oct <var data-var='date'> 14</var>, <var data-var='time'>10:01:04</var> GMT+0</small><br><strong>Monitoring</strong> - Some of the cloud resources of our Hetzner provider are still affected by the outage. Some of our systems may continue to experience degraded performance..</p> <p><small>Oct <var data-var='date'> 14</var>, <var data-var='time'>11:37:47</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 14 Oct 2025 07:52:00 +0000 https://addpipe.instatus.com/incident/cmgqahtwt0119nxed3ageoyub https://addpipe.instatus.com/incident/cmgqahtwt0119nxed3ageoyub Proactive software upgrades on database server Type: Maintenance Duration: 2 hours Affected Components: REST API V1, Database, Recording Client, Account Dashboard Jul 14, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 14, 07:00:00 GMT+0 - Identified - During the specified window, the Pipe team will perform some proactive software upgrades on Pipe's infrastructure. More specifically, we're updating the database software. **Expected Impact:** During the specified window, end users will see a 'temporarily unavailable' message when accessing the desktop and mobile recording clients. The Pipe account dashboard and REST API will also be unavailable. Jul 14, 09:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 2 hours

Affected Components: , , ,

<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - During the specified window, the Pipe team will perform some proactive software upgrades on Pipe's infrastructure. More specifically, we're updating the database software. **Expected Impact:** During the specified window, end users will see a 'temporarily unavailable' message when accessing the desktop and mobile recording clients. The Pipe account dashboard and REST API will also be unavailable..</p> <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 14 Jul 2025 07:00:00 +0000 https://addpipe.instatus.com/maintenance/cmcx9txzb001411ae7p8cna4f https://addpipe.instatus.com/maintenance/cmcx9txzb001411ae7p8cna4f High Load on the US2 Region Type: Incident Duration: 11 hours and 26 minutes Affected Components: US2 Processing Server Feb 25, 16:54:00 GMT+0 - Identified - The US2 region is currently undergoing a high load. As a result, the recording processing time will be longer. Feb 26, 04:20:00 GMT+0 - Resolved - The US2 region usage load is now back to normal Type: Incident

Duration: 11 hours and 26 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>16:54:00</var> GMT+0</small><br><strong>Identified</strong> - The US2 region is currently undergoing a high load. As a result, the recording processing time will be longer..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>04:20:00</var> GMT+0</small><br><strong>Resolved</strong> - The US2 region usage load is now back to normal.</p> ]]> Tue, 25 Feb 2025 16:54:00 +0000 https://addpipe.instatus.com/incident/cm7n78770000otz6veoj0l8wz https://addpipe.instatus.com/incident/cm7n78770000otz6veoj0l8wz Recording Client Failed to Send Data to Ingestion Servers Type: Incident Duration: 1 hour and 49 minutes Affected Components: Recording Client Sep 24, 09:45:00 GMT+0 - Resolved - We've rolled back to a previous build while we investigate the cause. Data is now being correctly transmitted and processed by the server. All systems are functioning normally. Sep 24, 07:56:00 GMT+0 - Identified - We have identified an issue where a new desktop recording client build could not successfully stream recording data to the ingestion servers. This resulted in recordings not being received or processed by the server. While most the desktop recording client interface behaved normal, the issue became apparent after attempting to play back a completed recording, where a "Buffering..." message was displayed, but no playback occurred. Type: Incident

Duration: 1 hour and 49 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>09:45:00</var> GMT+0</small><br><strong>Resolved</strong> - We've rolled back to a previous build while we investigate the cause. Data is now being correctly transmitted and processed by the server. All systems are functioning normally..</p> <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>07:56:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified an issue where a new desktop recording client build could not successfully stream recording data to the ingestion servers. This resulted in recordings not being received or processed by the server. While most the desktop recording client interface behaved normal, the issue became apparent after attempting to play back a completed recording, where a "Buffering..." message was displayed, but no playback occurred..</p> ]]> Tue, 24 Sep 2024 07:56:00 +0000 https://addpipe.instatus.com/incident/cm1iupvrf000crierm74mkxgo https://addpipe.instatus.com/incident/cm1iupvrf000crierm74mkxgo