<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.pingcord.xyz,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz"/>
  <link rel="self" type="application/atom+xml" href="https://status.pingcord.xyz/history.atom"/>
  <title>Pingcord Status - Incident history</title>
  <updated>2026-11-05T16:16:33.380+00:00</updated>
  <author>
    <name>Pingcord</name>
  </author>
  
<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmw3r00p600l80wo5toicbebf</id>
  <published>2026-11-05T16:16:33.380+00:00</published>
  <updated>2026-11-05T16:38:24.603+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmw3r00p600l80wo5toicbebf"/>
  <title>Events are not processing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 minutes</p>
    <p><strong>Affected Components:</strong> IRIS Ingest, Posting Service</p>
    <p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>16:38:24</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our monitoring systems alerted us prematurely. There has not been any impact to the Pingcord platform. We will keep a closer eye for a short time out of caution. Thanks!.</p>
<p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>16:16:33</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmvmg6gtw0mgt1mlng87sbye5</id>
  <published>2026-10-24T12:45:00.000+00:00</published>
  <updated>2026-10-24T14:45:30.159+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmvmg6gtw0mgt1mlng87sbye5"/>
  <title>Event processing delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> Posting Service</p>
    <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>14:45:30</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>13:10:33</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have returned service to normal and are currently monitoring. Thank you for your patience..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>12:45:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating event processing delays with the Pingcord service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmvie8mvi06hh13mkvq0z4vmu</id>
  <published>2026-10-21T17:36:11.211+00:00</published>
  <updated>2026-10-21T23:13:23.752+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmvie8mvi06hh13mkvq0z4vmu"/>
  <title>Pingcord is under maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> Website</p>
    <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>23:13:23</var> GMT+0</small><br /><strong>Resolved</strong> -
  Maintenance has now completed and service is restored. Thank you for your patience.  
  
Further maintenance will be necessary over the next few days, but this will not have any impact on website availability or service uptime. Notices for those will be published soon..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>21:51:13</var> GMT+0</small><br /><strong>Resolved</strong> -
  &lt;p&gt;Pingcord is beginning the recovery process, and pings should slowly start to come through. Pingcord will suppress mentions for events that have happened &amp;gt; 2 hours ago, to prevent annoying users. Thank you for your patience while we work through these issues.&lt;/p&gt;
&lt;p&gt;We are monitoring the situation closely and will provide updates soon.&lt;/p&gt;.</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>20:17:07</var> GMT+0</small><br /><strong>Investigating</strong> -
  Hello everyone,  

The Dashboard is offline while we perform urgent maintenance upgrades to protect the security and stability of our platform. Further updates will be provided in the next hour or so. Please note Pingcord core services are still functional. Thank you for your patience..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>17:36:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  The Pingcord website is currently undergoing maintenance. We will update this page with further updates. **Pings will continue to work as normal.**.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmus19u5j02pe0wtdvycmw7b1</id>
  <published>2026-10-03T06:51:11.717+00:00</published>
  <updated>2026-10-03T09:36:08.156+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmus19u5j02pe0wtdvycmw7b1"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> Website, IRIS Ingest</p>
    <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>09:36:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  &lt;p&gt;Pingcord is beginning the recovery process, and pings should slowly start to come through. Pingcord will suppress mentions for events that have happened &amp;gt; 2 hours ago, to prevent annoying users. Thank you for your patience while we work through these issues.&lt;/p&gt;
&lt;p&gt;We are monitoring the situation closely and will provide updates soon.&lt;/p&gt;.</p>
<p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>06:51:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  &lt;p&gt;The Pingcord website is currently down. We are investigating the root cause of the issue and will update this page with further updates.&lt;/p&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmu5zmc560a7w0wklofx1k5im</id>
  <published>2026-09-17T20:33:59.407+00:00</published>
  <updated>2026-09-17T20:59:50.692+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmu5zmc560a7w0wklofx1k5im"/>
  <title>Event processing delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 26 minutes</p>
    <p><strong>Affected Components:</strong> Posting Service, IRIS Ingest</p>
    <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>20:59:50</var> GMT+0</small><br /><strong>Resolved</strong> -
  This issue has been resolved..</p>
<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>20:33:59</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating delays with our event processing pipeline..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmtm2kf6703lv13qq0otqy0yn</id>
  <published>2026-09-03T22:01:05.109+00:00</published>
  <updated>2026-10-16T15:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmtm2kf6703lv13qq0otqy0yn"/>
  <title>YouTube API Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 days, 16 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> YouTube</p>
    <p><small>Oct <var data-var='date'> 16</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>02:58:23</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Following a fix by Google Engineering last week, all YouTube trackers have been re-established over the last few days.

We will continue to run the backup system while monitoring traffic to ensure we are seeing a similar level of activity from before the issues started. Once we&#039;re happy, we&#039;ll switch off the backup system..</p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>19:45:00</var> GMT+0</small><br /><strong>Identified</strong> -
  **Update:** We apologise that the backup system had malfunctioned since earlier today. The backup system&#039;s issue has now been resolved and pings are recovering.

We are \* **still\*** waiting on updates from Google Engineering regarding the main issue that has caused us to rely on the backup system. 

**Original issue:**  
  
We have identified an issue relating to trackers for YouTube channels. The issue is caused by an internal Google service. Google Engineering are aware of the issue and are actively looking into it.

Existing channels tracked by Pingcord have now been moved to a backup system until the issue is resolved. Newly-added channels are also now being tracked by the backup system. Pings may be delayed by up to 10 minutes as a result of this..</p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  **Update:** We apologise that the backup system had malfunctioned since earlier today. The backup system&#039;s issue has now been resolved and pings are recovering.

We are \* **still\*** waiting on updates from Google Engineering regarding the main issue that has caused us to rely on the backup system.   

**Original issue:**  
  
We have identified an issue relating to trackers for YouTube channels. The issue is caused by an internal Google service. Google Engineering are aware of the issue and are actively looking into it.

Existing channels tracked by Pingcord have now been moved to a backup system until the issue is resolved. Newly-added channels are also now being tracked by the backup system. Pings may be delayed by up to 10 minutes as a result of this..</p>
<p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>11:56:09</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified an issue relating to trackers for YouTube channels. The issue is caused by an internal Google service. Google Engineering are aware of the issue and are actively looking into it.

Existing channels tracked by Pingcord have now been moved to a backup system until the issue is resolved. Newly-added channels are also now being tracked by the backup system. Pings may be delayed by up to 10 minutes as a result of this.

We will provide further updates when we receive them from Google..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>05:50:47</var> GMT+0</small><br /><strong>Identified</strong> -
  **Current estimated impact:** 5% of YouTube channels affected

While we await updates from Google, we are continuing to identify and setup mitigations to reduce any impact to notifications. Any affected **existing** YouTube channel trackers are being moved to a temporary system. Once this is complete, we will be able to support new YouTube channel registrations..</p>
<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>22:01:05</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified an issue relating to trackers for YouTube channels. The issue is caused by an internal Google service and has been reported to Google Engineering. We are awaiting their response.

Trackers for new YouTube channels will fail to create and will be stuck as &quot;Creating tracker...&quot;

Existing channels will be unaffected until their trackers expire.

We are exploring any mitigations we can implement to minimise the impact..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmsw9qcs70c3b0rmkv40wgvn6</id>
  <published>2026-08-16T18:30:00.000+00:00</published>
  <updated>2026-08-16T21:38:30.946+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmsw9qcs70c3b0rmkv40wgvn6"/>
  <title>Platform Stability Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 9 minutes</p>
    <p><strong>Affected Components:</strong> Website, IRIS Ingest, Posting Service</p>
    <p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>21:38:30</var> GMT+0</small><br /><strong>Resolved</strong> -
  We are closing this incident but will continue to monitor ongoing. Our incident monitoring stack will also be reconfigured to generate an urgent alert to the team for the specific issue that occurred this evening..</p>
<p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>20:30:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A critical internal service handling communication to Discord restarted due to a fault. The restart was successful but it did not report to our other services that it was back online. An internal incident was raised automatically by our monitoring stack but was misclassified as a minor severity issue.

We have restored service currently. Pingcord is now recovering pings and data from prior to the incident..</p>
<p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmnjzgc0e05irtga72hihagwk</id>
  <published>2026-04-04T03:30:00.000+00:00</published>
  <updated>2026-04-04T07:15:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmnjzgc0e05irtga72hihagwk"/>
  <title>Event processing delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> IRIS Ingest, Posting Service, 
Main Services →</p>
    <p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>07:15:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Our investigation revealed an issue with a CloudFlare API led to internal service discovery problems which caused services to stop talking to each other. This has now been resolved by eliminating sole reliance on this API. Thank you for your patience..</p>
<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>06:45:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have identified the cause of the issue and are in the process of recovering pings. Pings will start to come through over the next hour or so. Any pings where the event occurred more than 2 hours ago will have their notifications silenced but will still be posted. Thank you for your patience while this was resolved..</p>
<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>03:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmmye47dp005b144n1ysgylc7</id>
  <published>2026-03-20T04:19:42.300+00:00</published>
  <updated>2026-03-20T04:34:48.005+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmmye47dp005b144n1ysgylc7"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> Website, IRIS Ingest</p>
    <p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>04:34:48</var> GMT+0</small><br /><strong>Resolved</strong> -
  &lt;p&gt;Pingcord is beginning the recovery process, and pings should slowly start to come through. Pingcord will suppress mentions for events that have happened &amp;gt; 2 hours ago, to prevent annoying users. Thank you for your patience while we work through these issues.&lt;/p&gt;
&lt;p&gt;We are monitoring the situation closely and will provide updates soon.&lt;/p&gt;.</p>
<p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>04:19:42</var> GMT+0</small><br /><strong>Investigating</strong> -
  &lt;p&gt;The Pingcord website is currently down. We are investigating the root cause of the issue and will update this page with further updates.&lt;/p&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmmr8f48l0j0sf6zwrxgf782f</id>
  <published>2026-03-15T04:05:50.517+00:00</published>
  <updated>2026-03-15T04:15:19.540+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmmr8f48l0j0sf6zwrxgf782f"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> Website, IRIS Ingest</p>
    <p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>04:15:19</var> GMT+0</small><br /><strong>Resolved</strong> -
  &lt;p&gt;Pingcord is beginning the recovery process, and pings should slowly start to come through. Pingcord will suppress mentions for events that have happened &amp;gt; 2 hours ago, to prevent annoying users. Thank you for your patience while we work through these issues.&lt;/p&gt;
&lt;p&gt;We are monitoring the situation closely and will provide updates soon.&lt;/p&gt;.</p>
<p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>04:05:50</var> GMT+0</small><br /><strong>Investigating</strong> -
  &lt;p&gt;The Pingcord website is currently down. We are investigating the root cause of the issue and will update this page with further updates.&lt;/p&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmlkco66q0c2710hxq6is1pse</id>
  <published>2026-02-13T03:50:45.841+00:00</published>
  <updated>2026-02-13T04:04:53.128+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmlkco66q0c2710hxq6is1pse"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> Website, IRIS Ingest</p>
    <p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>04:04:53</var> GMT+0</small><br /><strong>Resolved</strong> -
  &lt;p&gt;Pingcord is beginning the recovery process, and pings should slowly start to come through. Pingcord will suppress mentions for events that have happened &amp;gt; 2 hours ago, to prevent annoying users. Thank you for your patience while we work through these issues.&lt;/p&gt;
&lt;p&gt;We are monitoring the situation closely and will provide updates soon.&lt;/p&gt;.</p>
<p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>03:50:45</var> GMT+0</small><br /><strong>Investigating</strong> -
  &lt;p&gt;The Pingcord website is currently down. We are investigating the root cause of the issue and will update this page with further updates.&lt;/p&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmjnqzg650uadu6oq20pdemj8</id>
  <published>2025-12-27T03:35:20.476+00:00</published>
  <updated>2025-12-27T03:49:28.886+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmjnqzg650uadu6oq20pdemj8"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> Website, IRIS Ingest</p>
    <p><small>Dec <var data-var='date'> 27</var>, <var data-var='time'>03:49:28</var> GMT+0</small><br /><strong>Resolved</strong> -
  &lt;p&gt;Pingcord is beginning the recovery process, and pings should slowly start to come through. Pingcord will suppress mentions for events that have happened &amp;gt; 2 hours ago, to prevent annoying users. Thank you for your patience while we work through these issues.&lt;/p&gt;
&lt;p&gt;We are monitoring the situation closely and will provide updates soon.&lt;/p&gt;.</p>
<p><small>Dec <var data-var='date'> 27</var>, <var data-var='time'>03:35:20</var> GMT+0</small><br /><strong>Investigating</strong> -
  &lt;p&gt;The Pingcord website is currently down. We are investigating the root cause of the issue and will update this page with further updates.&lt;/p&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmiyuppmb0p3mu8b0wpu5rn5e</id>
  <published>2025-12-09T17:25:29.448+00:00</published>
  <updated>2025-12-09T17:35:31.866+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmiyuppmb0p3mu8b0wpu5rn5e"/>
  <title>Event processing delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> IRIS Ingest, Posting Service</p>
    <p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>17:35:31</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>17:25:29</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmgcu803c01csjzccbquci9rk</id>
  <published>2025-10-04T22:21:23.447+00:00</published>
  <updated>2025-10-05T00:50:18.659+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmgcu803c01csjzccbquci9rk"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> Website, IRIS Ingest</p>
    <p><small>Oct <var data-var='date'> 5</var>, <var data-var='time'>00:50:18</var> GMT+0</small><br /><strong>Resolved</strong> -
  &lt;p&gt;Pingcord is beginning the recovery process, and pings should slowly start to come through. Pingcord will suppress mentions for events that have happened &amp;gt; 2 hours ago, to prevent annoying users. Thank you for your patience while we work through these issues.&lt;/p&gt;
&lt;p&gt;We are monitoring the situation closely and will provide updates soon.&lt;/p&gt;.</p>
<p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>22:21:23</var> GMT+0</small><br /><strong>Investigating</strong> -
  &lt;p&gt;The Pingcord website is currently down. We are investigating the root cause of the issue and will update this page with further updates.&lt;/p&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmgcs3hll00fqzvjmh7xojumm</id>
  <published>2025-10-04T21:21:53.624+00:00</published>
  <updated>2025-10-04T22:05:26.787+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmgcs3hll00fqzvjmh7xojumm"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 44 minutes</p>
    <p><strong>Affected Components:</strong> Website, IRIS Ingest</p>
    <p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>22:05:26</var> GMT+0</small><br /><strong>Resolved</strong> -
  &lt;p&gt;Pingcord is beginning the recovery process, and pings should slowly start to come through. Pingcord will suppress mentions for events that have happened &amp;gt; 2 hours ago, to prevent annoying users. Thank you for your patience while we work through these issues.&lt;/p&gt;
&lt;p&gt;We are monitoring the situation closely and will provide updates soon.&lt;/p&gt;.</p>
<p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>21:21:53</var> GMT+0</small><br /><strong>Investigating</strong> -
  &lt;p&gt;The Pingcord website is currently down. We are investigating the root cause of the issue and will update this page with further updates.&lt;/p&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmc8j3oi8003kcfqwuxbot49l</id>
  <published>2025-06-23T03:20:11.983+00:00</published>
  <updated>2025-06-23T03:34:06.742+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmc8j3oi8003kcfqwuxbot49l"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> Website, IRIS Ingest</p>
    <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>03:34:06</var> GMT+0</small><br /><strong>Resolved</strong> -
  &lt;p&gt;Pingcord is beginning the recovery process, and pings should slowly start to come through. Pingcord will suppress mentions for events that have happened &amp;gt; 2 hours ago, to prevent annoying users. Thank you for your patience while we work through these issues.&lt;/p&gt;
&lt;p&gt;We are monitoring the situation closely and will provide updates soon.&lt;/p&gt;.</p>
<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>03:20:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  &lt;p&gt;The Pingcord website is currently down. We are investigating the root cause of the issue and will update this page with further updates.&lt;/p&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmbtpxifv001fk8s6282sgig3</id>
  <published>2025-06-12T18:34:48.681+00:00</published>
  <updated>2025-06-12T21:37:05.596+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmbtpxifv001fk8s6282sgig3"/>
  <title>YouTube API is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> YouTube</p>
    <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>21:37:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:31:34</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The YouTube API is currently working as expected however Google services are still experiencing widespread downtime issues. Pingcord is continuing to process YouTube events at this time but we will monitor the situation closely in case of any further downtime from YouTube..</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:41:22</var> GMT+0</small><br /><strong>Identified</strong> -
  We are seeing multiple reports from other apps &amp; services that Google Cloud APIs (incl. YouTube API) are experiencing an outage at this time. We will save YouTube events and will hold them in our event queue until Google resolve their outage..</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:34:48</var> GMT+0</small><br /><strong>Investigating</strong> -
  The YouTube API is returning a server error which is preventing Pingcord from processing YouTube events. Please note this is not an issue with Pingcord and we are attempting to identify a workaround until YouTube API services are working again..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmbju9nhs000brd855kbehmk1</id>
  <published>2025-06-05T20:38:31.186+00:00</published>
  <updated>2025-06-05T20:58:00.402+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmbju9nhs000brd855kbehmk1"/>
  <title>Event processing delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 minutes</p>
    <p><strong>Affected Components:</strong> IRIS Ingest</p>
    <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>20:58:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Event processing has returned to normal service without intervention. We will monitor the situation closely..</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>20:38:31</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently reduced performance in the event processing pipeline. Pingcord is still online however pings may be delayed by up to 30 minutes..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmbgg7ec5002912glljjgdu76</id>
  <published>2025-06-03T11:41:33.653+00:00</published>
  <updated>2025-06-03T15:50:57.644+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cmbgg7ec5002912glljjgdu76"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 9 minutes</p>
    <p><strong>Affected Components:</strong> Website, TikTok, IRIS Ingest</p>
    <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>15:50:57</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. We are monitoring the service closely and will be investigating the root cause leading to the downtime. Thank you for your patience!.</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>15:14:46</var> GMT+0</small><br /><strong>Monitoring</strong> -
  TikTok services are now being brought back online. Thank you for your patience..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>14:12:22</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Pingcord is back online, and we are currently monitoring the situation. TikTok pings will remain offline for the time being to ensure full system stability..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>13:50:13</var> GMT+0</small><br /><strong>Identified</strong> -
  We have resolved the root cause of the problem and are bringing Pingcord services back online..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>11:41:33</var> GMT+0</small><br /><strong>Investigating</strong> -
  &lt;p&gt;The Pingcord website is currently down. We are investigating the root cause of the issue and will update this page with further updates.&lt;/p&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cm9e23w7500g6o33i36bdlj3g</id>
  <published>2025-04-12T03:26:00.000+00:00</published>
  <updated>2025-04-12T10:42:05.628+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cm9e23w7500g6o33i36bdlj3g"/>
  <title>Event processing delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 16 minutes</p>
    <p><strong>Affected Components:</strong> Posting Service, IRIS Ingest</p>
    <p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>10:42:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  The event processing system has returned to normal. We are continuing to monitor the situation closely. We will investigate the root cause of this problem shortly..</p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>10:12:58</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified and events are now processing normally. Events will be cleared from our queue system within the next 20 minutes. Thank you for your patience..</p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>03:26:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating this issue..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cm95w3z170039c8vuo4suufhr</id>
  <published>2025-04-06T17:01:51.834+00:00</published>
  <updated>2025-04-09T00:38:00.113+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cm95w3z170039c8vuo4suufhr"/>
  <title>Facebook Pages issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 7 hours and 36 minutes</p>
    <p><strong>Affected Components:</strong> Facebook Pages</p>
    <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>00:38:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>22:36:29</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The issue has been resolved and we are now receiving events from Facebook Pages as normal. Pingcord will attempt to recover any missed pings during the down period though some may be missed unfortunately. We are monitoring the situation closely for any further changes.

This issue is a recurrence of a previous issue in March. We are continuing discussion with Meta to prevent this issue from happening in the future.

Thank you for your patience!.</p>
<p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>17:01:51</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified a recurrence of an issue last month with Facebook Pages connections. Instagram remains unaffected. We are working with Meta to resolve these issues promptly..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cm89435ss000srs5twedpfr51</id>
  <published>2025-03-14T18:28:49.721+00:00</published>
  <updated>2025-03-15T06:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cm89435ss000srs5twedpfr51"/>
  <title>Facebook Pages issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> Facebook Pages</p>
    <p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>05:02:48</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The problem has been resolved and we are now receiving events from Facebook as usual. We will monitor the situation closely. Thank you for your patience!.</p>
<p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>00:29:21</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the problem and are working with Meta to resolve a connection issue with our application. Thank you for your patience while we work on resolving this issue..</p>
<p><small>Mar <var data-var='date'> 14</var>, <var data-var='time'>18:28:49</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cm689o8hy007cnt1b4gr94g4w</id>
  <published>2025-01-22T15:00:00.000+00:00</published>
  <updated>2025-01-23T01:01:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cm689o8hy007cnt1b4gr94g4w"/>
  <title>Reddit pings not working</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> Reddit</p>
    <p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>01:01:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>00:18:50</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The issue has been resolved and we are monitoring closely for any recurrences..</p>
<p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  The cause of the issue has been found and work is underway to resolve the problem..</p>
<p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an issue with Reddit pings from earlier today..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cm5d97p0q00azb1q4jrgp7tot</id>
  <published>2025-01-01T02:03:00.000+00:00</published>
  <updated>2025-01-01T08:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cm5d97p0q00azb1q4jrgp7tot"/>
  <title>Event processing delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 27 minutes</p>
    <p><strong>Affected Components:</strong> Posting Service, IRIS Ingest</p>
    <p><small>Jan <var data-var='date'> 1</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 1</var>, <var data-var='time'>04:15:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jan <var data-var='date'> 1</var>, <var data-var='time'>03:57:52</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Service has been restored and our system is now processing the backlog of events. Pings should not be missed. Pingcord will post them unless they are related to livestreams which have already ended. We are monitoring the situation closely, thank you for your patience and happy new year!.</p>
<p><small>Jan <var data-var='date'> 1</var>, <var data-var='time'>02:03:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The Pingcord service is experience severe delays to notification processing. We are investigating the root cause of the issue and will update this page with further updates..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/clw3l9pxg104560s7ofy2ee38oc</id>
  <published>2024-05-12T13:46:43.826+00:00</published>
  <updated>2024-05-14T01:01:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/clw3l9pxg104560s7ofy2ee38oc"/>
  <title>Meta connection issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 11 hours and 14 minutes</p>
    <p><strong>Affected Components:</strong> Facebook Pages, Instagram</p>
    <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>01:01:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>21:01:59</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have resolved the issue with our access to Meta&#039;s APIs. Facebook and Instagram integrations should begin to work again as usual. We will monitor the situation closely to ensure it has been resolved..</p>
<p><small>May <var data-var='date'> 12</var>, <var data-var='time'>13:46:43</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

</feed>