<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:addpipe.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://addpipe.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://addpipe.instatus.com/history.atom"/>
  <title>Pipe Platform Status - Incident history</title>
  <updated>2026-08-03T09:00:00.000+00:00</updated>
  <author>
    <name>Pipe Platform</name>
  </author>
  
<entry>
  <id>tag:addpipe.instatus.com,2005:Maintenance/cms379jmc0lk40zml4lvagtb0</id>
  <published>2026-08-03T09:00:00.000+00:00</published>
  <updated>2026-08-05T11:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://addpipe.instatus.com/maintenance/cms379jmc0lk40zml4lvagtb0"/>
  <title>Cloud Provider Scheduled Networking Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 days and 2 hours</p>
    <p><strong>Affected Components:</strong> US2 Ingestion Server, US2 Processing Server</p>
    <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>12:25:16</var> GMT+0</small><br /><strong>Identified</strong> -
  One of our cloud providers will be making changes to the core networking infrastructure to improve performance and scalability

This maintenance will be carried out in three phases as outlined below:  
  
August 3, 09:00 to 11:00 UTC  
August 4, 09:00 to 11:00 UTC  
August 5, 09:00 to 11:00 UTC.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:addpipe.instatus.com,2005:Maintenance/cmmk9otjm07u6k5jd9bt9b0f9</id>
  <published>2026-03-10T08:15:00.000+00:00</published>
  <updated>2026-03-10T10:02:45.326+00:00</updated>
  <link rel="alternate" type="text/html" href="https://addpipe.instatus.com/maintenance/cmmk9otjm07u6k5jd9bt9b0f9"/>
  <title>Maintenance window announced by our upstream cloud provider (Hetzner)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 days, 11 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> EU2 Ingestion Server, US1 Ingestion Server, US2 Ingestion Server, REST API V1, Recording Client, US2 Processing Server, , US1 Processing Server, , EU2 Processing Server, Account Dashboard, Database, 
Ingestion Servers → 
Processing Servers →</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>
<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'>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&#039;s status report for this maintenance window can be followed [here](https://status.hetzner.com/incident/4faff75c-3f38-4f9d-962c-a52273dc841a)..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:addpipe.instatus.com,2005:Incident/cmh8zpgnt00uxsfsgxly0isbn</id>
  <published>2025-10-27T10:23:33.166+00:00</published>
  <updated>2025-10-27T11:36:51.804+00:00</updated>
  <link rel="alternate" type="text/html" href="https://addpipe.instatus.com/incident/cmh8zpgnt00uxsfsgxly0isbn"/>
  <title>Network issues with our cloud provider</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 13 minutes</p>
    <p><strong>Affected Components:</strong> EU2 Ingestion Server, US1 Ingestion Server, US2 Ingestion Server, Recording Client, US2 Processing Server, , US1 Processing Server, , EU2 Processing Server, Account Dashboard, Database, 
Ingestion Servers → 
Processing Servers →</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>
<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&#039;ve contacted the cloud provider&#039;s support, and are continuing to monitor the situation.</p>
<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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:addpipe.instatus.com,2005:Incident/cmgrqdusz00o42jfxnqccct1s</id>
  <published>2025-10-15T08:30:30.392+00:00</published>
  <updated>2025-10-15T08:46:45.981+00:00</updated>
  <link rel="alternate" type="text/html" href="https://addpipe.instatus.com/incident/cmgrqdusz00o42jfxnqccct1s"/>
  <title>We are currently experiencing issues with our cloud provider Hetzner.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 16 minutes</p>
    <p><strong>Affected Components:</strong> , , US1 Processing Server, EU2 Ingestion Server, US1 Ingestion Server, EU2 Processing Server, US2 Processing Server, US2 Ingestion Server, REST API V1, Recording Client, Database, Account Dashboard, 
Ingestion Servers → 
Processing Servers →</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:addpipe.instatus.com,2005:Incident/cmgqahtwt0119nxed3ageoyub</id>
  <published>2025-10-14T07:52:00.000+00:00</published>
  <updated>2025-10-14T11:37:47.701+00:00</updated>
  <link rel="alternate" type="text/html" href="https://addpipe.instatus.com/incident/cmgqahtwt0119nxed3ageoyub"/>
  <title>There is currently a network disruption at the cloud location of our Hetzner provider</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> , , US1 Processing Server, EU2 Ingestion Server, US1 Ingestion Server, EU2 Processing Server, US2 Processing Server, US2 Ingestion Server, REST API V1, Recording Client, Database, Account Dashboard, 
Ingestion Servers → 
Processing Servers →</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>
<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'>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'>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'>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&#039;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'>07:52:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are currently monitoring the incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:addpipe.instatus.com,2005:Maintenance/cmcx9txzb001411ae7p8cna4f</id>
  <published>2025-07-14T07:00:00.000+00:00</published>
  <updated>2025-07-14T09:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://addpipe.instatus.com/maintenance/cmcx9txzb001411ae7p8cna4f"/>
  <title>Proactive software upgrades on database server</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> REST API V1, Database, Recording Client, Account Dashboard</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>
<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&#039;s infrastructure. More specifically, we&#039;re updating the database software.

**Expected Impact:** During the specified window, end users will see a &#039;temporarily unavailable&#039; message when accessing the desktop and mobile recording clients. The Pipe account dashboard and REST API will also be unavailable..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:addpipe.instatus.com,2005:Incident/cm7n78770000otz6veoj0l8wz</id>
  <published>2025-02-25T16:54:00.000+00:00</published>
  <updated>2025-02-26T04:20:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://addpipe.instatus.com/incident/cm7n78770000otz6veoj0l8wz"/>
  <title>High Load on the US2 Region</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 26 minutes</p>
    <p><strong>Affected Components:</strong> US2 Processing Server</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>
<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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:addpipe.instatus.com,2005:Incident/cm1iupvrf000crierm74mkxgo</id>
  <published>2024-09-24T07:56:00.000+00:00</published>
  <updated>2024-09-24T09:45:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://addpipe.instatus.com/incident/cm1iupvrf000crierm74mkxgo"/>
  <title>Recording Client Failed to Send Data to Ingestion Servers</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 49 minutes</p>
    <p><strong>Affected Components:</strong> Recording Client</p>
    <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&#039;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 &quot;Buffering...&quot; message was displayed, but no playback occurred..</p>

        ]]>
  </content>
</entry>

</feed>