<?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-04-04T03:30:00.000+00:00</updated>
  <author>
    <name>Pingcord</name>
  </author>
  
<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cmnjzgc0e05irtga72hihagwk</id>
  <published>2026-04-04T03:30:00.000+00:00</published>
  <updated>2026-04-04T03:30: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'>03:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</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'>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>

        ]]>
  </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:19:42.312+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: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>
<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>

        ]]>
  </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:05:50.525+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: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>
<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>

        ]]>
  </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-13T03:50:45.855+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'>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>
<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>

        ]]>
  </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:35:20.493+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: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>
<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>

        ]]>
  </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:25:29.448+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:25:29</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</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>

        ]]>
  </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-04T22:21:23.470+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'> 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>
<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>

        ]]>
  </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:20:11.995+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: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>
<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>

        ]]>
  </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-12T18:41:22.272+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'>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>
<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'>21:37:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</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:38:31.186+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: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>
<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>

        ]]>
  </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-03T13:50:13.477+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'>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'>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'>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'>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>
<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>

        ]]>
  </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:12:58.983+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: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>
<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>

        ]]>
  </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-08T22:36:29.618+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'> 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'> 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'> 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-14T18:28:49.721+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'> 14</var>, <var data-var='time'>18:28:49</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</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'>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'> 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>

        ]]>
  </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-22T20:00: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'> 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'> 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'>15:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an issue with Reddit pings from earlier today..</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>

        ]]>
  </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-01T04:15: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'>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>
<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>

        ]]>
  </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'> 12</var>, <var data-var='time'>13:46:43</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/clv1u5nah33463bbo9erspq63j</id>
  <published>2024-04-16T03:40:15.892+00:00</published>
  <updated>2024-04-16T03:40:15.892+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/clv1u5nah33463bbo9erspq63j"/>
  <title>YouTube Trackers</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> YouTube</p>
    <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>03:40:15</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified an issue with tracker connections to YouTube for some channels.

We have deployed a fix and are currently renewing all trackers as a precautionary measure. This process will take a few hours to get through all of the trackers. Once your channel&#039;s tracker is fixed, YouTube may send us any queued events which will cause Pingcord to post the alerts. However, we appreciate you may have already posted a message yourself so Pingcord will &quot;suppress&quot; the @ mention tags for any video uploads over 3 hours ago. This means they will still appear in Discord like a mention but it has not notified your users..</p>
<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>13:52:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We are pleased to confirm all trackers have been renewed. Please report any issues as usual in our support server. Thank you for your continued patience!.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cluwxlxwn171364bpn8z5t88h4a</id>
  <published>2024-04-12T17:18:04.438+00:00</published>
  <updated>2024-04-12T17:18:04.438+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cluwxlxwn171364bpn8z5t88h4a"/>
  <title>Ongoing database issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> TikTok, Timer Alerts, Reddit, Facebook Pages, Mastodon, Kick.com, RSS Feeds, Instagram, Twitch, Spotify, YouTube, Posting Service, IRIS Ingest, Website, X / Twitter</p>
    <p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>17:18:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating issues related to our outage earlier this morning. It appears our database cluster has not recovered properly and as a result some integrations may be missing.

We are in the processing of confirming if this is the case. If so, we will reset our servers using a backup from before the outage this morning. To do this, we will take Pingcord offline temporarily to carry this out. We plan to do this by 7pm UTC (around 2 hours from this message at 8pm UK time, 3pm ET, 12 noon PT). The downtime will last a few hours but we will try and queue any incoming data and send the pings out afterwards.

Thank you for your continued patience while we sort out these issues..</p>
<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>04:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  As of now the service is restored. We will continue to monitor the service throughout the weekend..</p>
<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>03:00:19</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Emergency database maintenance has been completed successfully.

Unfortunately, due to the nature of the database crash, any changes made to pre-existing integrations will be **rolled back** to this morning. New servers that joined after the crash _should_ have their integrations preserved.

Thank you for your continued patience..</p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have now started the database backup process. During this time, we are reconciling any changes made from this morning&#039;s outage. This may take some time to process all of the records.

We will attempt to save any data received from Twitch, YouTube, etc. to recover pings after the downtime.

Please keep an eye out here, or join our Discord server at &lt;https://discord.gg/QKwDHGy&gt; for further information..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cluwb0sej18698bpmxzwdz20xs</id>
  <published>2024-04-12T06:45:46.164+00:00</published>
  <updated>2024-04-12T06:45:46.164+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cluwb0sej18698bpmxzwdz20xs"/>
  <title>Database issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 26 minutes</p>
    <p><strong>Affected Components:</strong> IRIS Ingest, Website</p>
    <p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>06:45:46</var> GMT+0</small><br /><strong>Investigating</strong> -
  The Pingcord website is currently down. We are investigating the root cause of the issue and will update this page with further updates..</p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>10:11:29</var> GMT+0</small><br /><strong>Resolved</strong> -
  The affected issues have been resolved. We will continue to monitor the services closely. We apologise for any inconvenience caused..</p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>07:10:04</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Pingcord is beginning the recovery process, and pings should slowly start to come through. Pingcord will suppress mentions for events that have happened &gt; 2 hours ago, to prevent annoying users. Thank you for your patience while we work through these issues.

We are monitoring the situation closely and will provide updates soon..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/clqxx4bz3144850cemw7u51m16r</id>
  <published>2024-01-03T15:13:19.420+00:00</published>
  <updated>2024-01-03T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/clqxx4bz3144850cemw7u51m16r"/>
  <title>Event processing delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 47 minutes</p>
    <p><strong>Affected Components:</strong> Posting Service, IRIS Ingest</p>
    <p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>15:13:19</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an increased event delay rate..</p>
<p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>18:28:01</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The root issue has been identified and events are now processing normally. We expect all events to be cleared from our queue system within the next few minutes. Thank you for your patience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/clqr4zcdg254871uon3cmhh9xz3</id>
  <published>2023-12-29T21:19:00.963+00:00</published>
  <updated>2023-12-29T21:19:00.983+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/clqr4zcdg254871uon3cmhh9xz3"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 21 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> IRIS Ingest, Website</p>
    <p><small>Dec <var data-var='date'> 29</var>, <var data-var='time'>21:19:00</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>
<p><small>Dec <var data-var='date'> 29</var>, <var data-var='time'>22:04:01</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/clnmijxks18791bzndk8ppnz56</id>
  <published>2023-10-12T01:40:57.798+00:00</published>
  <updated>2023-10-12T01:40:57.798+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/clnmijxks18791bzndk8ppnz56"/>
  <title>Event processing delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> YouTube, IRIS Ingest</p>
    <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>01:40:57</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an increased event error rate..</p>
<p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>06:40:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This issue has been resolved. Some pings may have been missed or delayed. The root cause of the issue was identified and we are working towards implementing a solution to prevent it happening again. We apologise for the inconvience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.pingcord.xyz,2005:Incident/cll3kfq3u35621iroifwr5e559</id>
  <published>2023-08-09T10:06:39.593+00:00</published>
  <updated>2023-08-09T10:06:39.630+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.pingcord.xyz/incident/cll3kfq3u35621iroifwr5e559"/>
  <title>Pingcord is down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> IRIS Ingest, Website</p>
    <p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>10:06:39</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>
<p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>11:20:00</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>Aug <var data-var='date'> 10</var>, <var data-var='time'>14:59:28</var> GMT+0</small><br /><strong>Resolved</strong> -
  A networking issue with our cloud server provider resulted in connection drops between our own services. The issue was resolved quickly but recurred later that day for a few hours. Since the second fix, networking has remained stable and we are not expecting any further impact.

Please see: https://status.digitalocean.com/incidents/q4b09b022nmh for further information.</p>

        ]]>
  </content>
</entry>

</feed>