<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cognizo Status Page Status - Incident history</title>
    <link>https://status.cognizo.ai</link>
    <description>Cognizo Status Page</description>
    <pubDate>Thu, 22 Oct 2026 13:44:58 +0000</pubDate>
    
<item>
  <title>Cloud-based Services</title>
  <description>
    Type: Incident
    

    Affected Components: PDF Service, Content Creation Service, Technical Audit Service, Ad Strategies Service, Traffic Analytics Service
    Oct 22, 19:39:06 GMT+0 - Monitoring - Posting last update. Cognizo has run a post-mortem in the incident and is waiting for the cloud provider Railway to come back with significant status updates. There will be no other updates until then. Interested parties can track the Railway outage here: &lt;https://status.railway.com/&gt; Oct 22, 18:30:43 GMT+0 - Monitoring - Cognizo is still monitoring the incident. You can read more about the incident and our response here: &lt;https://www.cognizo.ai/blog/post-mortem-railway-security-incident-oct-2026&gt; Oct 22, 17:43:21 GMT+0 - Monitoring - All services are now operational. Cognizo observed no impact from the incident caused by our third party provider. We will be monitoring this incident until its resolved on their end: &lt;https://status.railway.com/&gt;  
  
All services are operational and we have implemented all the necessary security protocols. Oct 22, 15:10:39 GMT+0 - Identified - Cognizo is continuing to work on a fix for this incident. Our cloud service provider (Railway) let us know of a security incident on their side. The analysis from the Cognizo team shows no malicious activity on our side, but the Cognizo team is working to investigate and implement additional security measures. Services will be intermittently out and users may experience unexpected sign-outs as we work through this incident. Oct 22, 13:44:58 GMT+0 - Identified - Cognizo is experiencing issues with our Cloud service provider (Railway). Cognizo team is working on updates to fix the issues currently. More info here: [Railway Status Page](https://status.railway.com/?utm%5Fcampaign=Security+Disclosure%3A+Wednesday+October+21st&amp;utm%5Fcontent=Security+Disclosure%3A+Wednesday+October+21st&amp;utm%5Fmedium=email%5Faction&amp;utm%5Fsource=customer.io) 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>19:39:06</var> GMT+0</small><br><strong>Monitoring</strong> -
  Posting last update. Cognizo has run a post-mortem in the incident and is waiting for the cloud provider Railway to come back with significant status updates. There will be no other updates until then. Interested parties can track the Railway outage here: &lt;https://status.railway.com/&gt;.</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>18:30:43</var> GMT+0</small><br><strong>Monitoring</strong> -
  Cognizo is still monitoring the incident. You can read more about the incident and our response here: &lt;https://www.cognizo.ai/blog/post-mortem-railway-security-incident-oct-2026&gt;.</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>17:43:21</var> GMT+0</small><br><strong>Monitoring</strong> -
  All services are now operational. Cognizo observed no impact from the incident caused by our third party provider. We will be monitoring this incident until its resolved on their end: &lt;https://status.railway.com/&gt;  
  
All services are operational and we have implemented all the necessary security protocols..</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>15:10:39</var> GMT+0</small><br><strong>Identified</strong> -
  Cognizo is continuing to work on a fix for this incident. Our cloud service provider (Railway) let us know of a security incident on their side. The analysis from the Cognizo team shows no malicious activity on our side, but the Cognizo team is working to investigate and implement additional security measures. Services will be intermittently out and users may experience unexpected sign-outs as we work through this incident..</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>13:44:58</var> GMT+0</small><br><strong>Identified</strong> -
  Cognizo is experiencing issues with our Cloud service provider (Railway). Cognizo team is working on updates to fix the issues currently. More info here: [Railway Status Page](https://status.railway.com/?utm%5Fcampaign=Security+Disclosure%3A+Wednesday+October+21st&amp;utm%5Fcontent=Security+Disclosure%3A+Wednesday+October+21st&amp;utm%5Fmedium=email%5Faction&amp;utm%5Fsource=customer.io).</p>
]]>
  </content:encoded>
  <pubDate>Thu, 22 Oct 2026 13:44:58 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmvjlf5o801y413n5am1schpe</link>
  <guid>https://status.cognizo.ai/incident/cmvjlf5o801y413n5am1schpe</guid>
</item>

<item>
  <title>Microsoft Copilot Scraping is not available</title>
  <description>
    Type: Incident
    

    Affected Components: Copilot Service
    Oct 15, 20:26:01 GMT+0 - Identified - We are continuing to work on a fix for this incident. The primary issue is around the auth wall Microsoft presents. Oct 13, 19:30:01 GMT+0 - Investigating - We are investigating an issue with Copilot data. [copilot.microsoft.com](http://copilot.microsoft.com) hits an auth wall every time, meaning scraping is not available.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>20:26:01</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident. The primary issue is around the auth wall Microsoft presents..</p>
<p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>19:30:01</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating an issue with Copilot data. [copilot.microsoft.com](http://copilot.microsoft.com) hits an auth wall every time, meaning scraping is not available. .</p>
]]>
  </content:encoded>
  <pubDate>Tue, 13 Oct 2026 19:30:01 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmva0syui00790wk0vmgyaarc</link>
  <guid>https://status.cognizo.ai/incident/cmva0syui00790wk0vmgyaarc</guid>
</item>

<item>
  <title>Perplexity data collection is partial</title>
  <description>
    Type: Incident
    Duration: 14 days, 1 hour and 20 minutes

    Affected Components: Perplexity Service
    Sep 15, 17:20:00 GMT+0 - Resolved - We implemented a fix for Perplexity scraping where API collection will any authwalls. The team is also working with several scraping providers to bring scraping functions fully online.  Sep 7, 17:20:00 GMT+0 - Identified - We have identified the issue related to Perplexity data collection, specifically captcha issues and timing out. The issue has furthered as Perplexity built new bot detection mechanisms blocking our data collection. We have implemented a fallback methodology that will go into effect tonight. Sep 1, 16:50:00 GMT+0 - Identified - We have identified the issue related to Perplexity data collection. The issue is caused by a problem with one of our service providers who does the data collection for Perplexity. We are working with the provider currently and working to resolve it as soon as possible. Sep 1, 16:00:00 GMT+0 - Investigating - We are investigating an issue with Perplexity data collection.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 days, 1 hour and 20 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>17:20:00</var> GMT+0</small><br><strong>Resolved</strong> -
  We implemented a fix for Perplexity scraping where API collection will any authwalls. The team is also working with several scraping providers to bring scraping functions fully online. .</p>
<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>17:20:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue related to Perplexity data collection, specifically captcha issues and timing out. The issue has furthered as Perplexity built new bot detection mechanisms blocking our data collection. We have implemented a fallback methodology that will go into effect tonight..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>16:50:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue related to Perplexity data collection. The issue is caused by a problem with one of our service providers who does the data collection for Perplexity. We are working with the provider currently and working to resolve it as soon as possible..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating an issue with Perplexity data collection. .</p>
]]>
  </content:encoded>
  <pubDate>Tue, 1 Sep 2026 16:00:00 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmtsxw8y309vz1fpqlerpupb2</link>
  <guid>https://status.cognizo.ai/incident/cmtsxw8y309vz1fpqlerpupb2</guid>
</item>

<item>
  <title>Content Studio has a degraded performance</title>
  <description>
    Type: Incident
    Duration: 1 hour and 21 minutes

    Affected Components: , 
Cognizo App →
    Aug 5, 14:42:01 GMT+0 - Resolved - This incident has been resolved. Aug 5, 13:47:17 GMT+0 - Monitoring - We are observing full recovery from our third party provider, Antrophic.   
  
Monitoring results. Aug 5, 13:21:19 GMT+0 - Identified - Our third party provider, Antrophic, has an on-going incident causing issues on content generation. You can follow the incident here: &lt;https://status.claude.com/&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>14:42:01</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>13:47:17</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are observing full recovery from our third party provider, Antrophic.   
  
Monitoring results..</p>
<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>13:21:19</var> GMT+0</small><br><strong>Identified</strong> -
  Our third party provider, Antrophic, has an on-going incident causing issues on content generation. You can follow the incident here: &lt;https://status.claude.com/&gt;.</p>
]]>
  </content:encoded>
  <pubDate>Wed, 5 Aug 2026 13:21:19 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmsg48a6303he0ro3k8mysxz1</link>
  <guid>https://status.cognizo.ai/incident/cmsg48a6303he0ro3k8mysxz1</guid>
</item>

<item>
  <title>Prompt Volumes not displaying correctly. </title>
  <description>
    Type: Incident
    Duration: 21 hours and 12 minutes

    Affected Components: , 
Cognizo App →
    Jun 4, 13:28:37 GMT+0 - Resolved - This incident has been resolved. Jun 3, 21:06:08 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Prompt volumes should be visibile. Jun 3, 17:17:45 GMT+0 - Identified - We identified the root cause of the problem and the engineering team will issue a fix by end of day today.  Jun 3, 16:17:00 GMT+0 - Investigating - We are currently investigating this incident. Users may see all volumes are &lt;10 at the time.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>13:28:37</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>21:06:08</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result. Prompt volumes should be visibile..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>17:17:45</var> GMT+0</small><br><strong>Identified</strong> -
  We identified the root cause of the problem and the engineering team will issue a fix by end of day today. .</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>16:17:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident. Users may see all volumes are &lt;10 at the time. .</p>
]]>
  </content:encoded>
  <pubDate>Wed, 3 Jun 2026 16:17:00 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmpybwuav03f8quljf6mobh4v</link>
  <guid>https://status.cognizo.ai/incident/cmpybwuav03f8quljf6mobh4v</guid>
</item>

<item>
  <title>Issues with authentication</title>
  <description>
    Type: Incident
    Duration: 1 hour and 40 minutes

    Affected Components: , 
Cognizo App →
    May 26, 23:10:35 GMT+0 - Resolved - This incident has been resolved by our authentication provider. May 26, 22:06:03 GMT+0 - Monitoring - Our authentication has implemented a fix and the platform has now fully recovered. We will be monitoring this incident for the next hour for any degradation.  May 26, 21:44:10 GMT+0 - Identified - We are continuing to work on a fix for this incident. Our third party service (Clerk) is currently working on a fix to enable access to the platform. May 26, 21:30:14 GMT+0 - Investigating - We are currently investigating this incident. The issue is stemming from our authentication provider and updates can be tracked here:  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 40 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>23:10:35</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved by our authentication provider..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>22:06:03</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our authentication has implemented a fix and the platform has now fully recovered. We will be monitoring this incident for the next hour for any degradation. .</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>21:44:10</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident. Our third party service (Clerk) is currently working on a fix to enable access to the platform..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>21:30:14</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident. The issue is stemming from our authentication provider and updates can be tracked here: .</p>
]]>
  </content:encoded>
  <pubDate>Tue, 26 May 2026 21:30:14 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmpn5fk89047dpfp5c1k3gsle</link>
  <guid>https://status.cognizo.ai/incident/cmpn5fk89047dpfp5c1k3gsle</guid>
</item>

<item>
  <title>Degraded performance affecting the platform.</title>
  <description>
    Type: Incident
    Duration: 6 hours and 8 minutes

    Affected Components: , 
Cognizo App →
    May 20, 05:08:00 GMT+0 - Resolved - This incident has been resolved. May 20, 04:08:01 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. This outage was primarily derived by our cloud provider, Railway and GCP. They have since fixed the problem and we have taken the necessary steps to recover the platform.  May 20, 02:19:11 GMT+0 - Identified - We are continuing to work on a fix for this incident, as the fix is being rolled out platform will be unavailable for our users. May 20, 02:11:49 GMT+0 - Identified - We are continuing to work on a fix for this incident which is stemming from our cloud providers outage. Updates can be tracked via &lt;https://status.railway.com/&gt; May 20, 01:00:00 GMT+0 - Identified - We are continuing to work on a fix for this incident with our cloud providers May 20, 00:00:00 GMT+0 - Identified - We are continuing to work on a fix for this incident with our cloud providers. May 19, 23:00:00 GMT+0 - Investigating - We are currently investigating this incident. Some users may be unable to access the platform at this time.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>05:08:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>04:08:01</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result. This outage was primarily derived by our cloud provider, Railway and GCP. They have since fixed the problem and we have taken the necessary steps to recover the platform. .</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>02:19:11</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident, as the fix is being rolled out platform will be unavailable for our users..</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>02:11:49</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident which is stemming from our cloud providers outage. Updates can be tracked via &lt;https://status.railway.com/&gt;.</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident with our cloud providers.</p>
<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident with our cloud providers..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident. Some users may be unable to access the platform at this time. .</p>
]]>
  </content:encoded>
  <pubDate>Tue, 19 May 2026 23:00:00 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmpdfaxuz06muqj6zr6ng0cpx</link>
  <guid>https://status.cognizo.ai/incident/cmpdfaxuz06muqj6zr6ng0cpx</guid>
</item>

<item>
  <title>Issues with Suggestions</title>
  <description>
    Type: Incident
    Duration: 10 hours and 33 minutes

    Affected Components: , 
Cognizo App →
    May 16, 22:33:04 GMT+0 - Resolved - This incident has been resolved. May 16, 12:00:00 GMT+0 - Investigating - We are investigating an issue with topic and prompt generation. Users may be unable to get suggestions at this time.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 33 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 16</var>, <var data-var='time'>22:33:04</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 16</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating an issue with topic and prompt generation. Users may be unable to get suggestions at this time. .</p>
]]>
  </content:encoded>
  <pubDate>Sat, 16 May 2026 12:00:00 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmp8ycvkm06o6qkml4jkh62ry</link>
  <guid>https://status.cognizo.ai/incident/cmp8ycvkm06o6qkml4jkh62ry</guid>
</item>

<item>
  <title>Degraded performance with the Perplexity Scraper</title>
  <description>
    Type: Incident
    Duration: 1 day, 22 hours and 37 minutes

    Affected Components: Perplexity Service
    May 14, 12:07:07 GMT+0 - Resolved - The issue with Perplexity data collection has been resolved. It was caused by a problem with one of our service providers. We worked with them to fix it, and everything is now back to normal. Thanks for your patience. May 14, 12:06:46 GMT+0 - Monitoring - We have resolved the issue related to Perplexity data collection at this time for all users.  May 12, 16:20:00 GMT+0 - Identified - We have identified the issue related to Perplexity data collection. The issue is caused by a problem with one of our service providers who does the data collection for perplexity. We are working with the provider currently and working to resolve it as soon as possible. May 12, 13:30:00 GMT+0 - Investigating - We are investigating an issue with Perplexity data collection. Perplexity data may be missing while the team is working on this issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 22 hours and 37 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>12:07:07</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue with Perplexity data collection has been resolved. It was caused by a problem with one of our service providers. We worked with them to fix it, and everything is now back to normal. Thanks for your patience..</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>12:06:46</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have resolved the issue related to Perplexity data collection at this time for all users. .</p>
<p><small>May <var data-var='date'> 12</var>, <var data-var='time'>16:20:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue related to Perplexity data collection. The issue is caused by a problem with one of our service providers who does the data collection for perplexity. We are working with the provider currently and working to resolve it as soon as possible..</p>
<p><small>May <var data-var='date'> 12</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating an issue with Perplexity data collection. Perplexity data may be missing while the team is working on this issue..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 12 May 2026 13:30:00 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmp4arvkt0112p9klz59qgb3q</link>
  <guid>https://status.cognizo.ai/incident/cmp4arvkt0112p9klz59qgb3q</guid>
</item>

<item>
  <title>Cognizo release maintenance.</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: , 
Cognizo App →
    May 3, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully May 3, 20:00:01 GMT+0 - Identified - Maintenance is now in progress May 3, 20:00:00 GMT+0 - Identified - Users may encounter errors during this time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Users may encounter errors during this time..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 3 May 2026 20:00:00 +0000</pubDate>
  <link>https://status.cognizo.ai/maintenance/cmoq6saox00pd7q598arxxszz</link>
  <guid>https://status.cognizo.ai/maintenance/cmoq6saox00pd7q598arxxszz</guid>
</item>

<item>
  <title>Cognizo is experiencing failures due to a hardware outage</title>
  <description>
    Type: Incident
    Duration: 20 minutes

    Affected Components: , 
Cognizo App →
    Apr 30, 20:09:22 GMT+0 - Resolved - This incident has been resolved. We are seeing a complete recovery across all services. Apr 30, 19:58:04 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. All systems should now be operational. Apr 30, 19:57:51 GMT+0 - Identified - We identified the issue to be a hardware failure from our cloud provider: Railway/AWS. The team is working on a fix. Apr 30, 19:48:58 GMT+0 - Investigating - We are currently investigating this incident. Incident appears to be coming from our cloud provider (Railway, AWS) having a hardware outage. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>20:09:22</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. We are seeing a complete recovery across all services..</p>
<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>19:58:04</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result. All systems should now be operational..</p>
<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>19:57:51</var> GMT+0</small><br><strong>Identified</strong> -
  We identified the issue to be a hardware failure from our cloud provider: Railway/AWS. The team is working on a fix..</p>
<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>19:48:58</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident. Incident appears to be coming from our cloud provider (Railway, AWS) having a hardware outage..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 30 Apr 2026 19:48:58 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmolwd6qd0aybyqv334o1suis</link>
  <guid>https://status.cognizo.ai/incident/cmolwd6qd0aybyqv334o1suis</guid>
</item>

<item>
  <title>Logging in and load times is experiencing a partial outage</title>
  <description>
    Type: Incident
    Duration: 29 minutes

    Affected Components: , 
Cognizo App →
    Mar 10, 16:42:00 GMT+0 - Resolved - This incident has been resolved. We are seeing a complete recovery across all services. Mar 10, 16:32:46 GMT+0 - Monitoring - Our third party provider has fixed the downstream problem and we are observing increased performance and all logins should now be operational. Mar 10, 16:26:34 GMT+0 - Identified - Issue has been identified by the third party provider and a fix is being implemented. For more information: &lt;https://status.clerk.com/incidents/01KHVBF47Q3SDK1VX7ZNHQ316R&gt; Mar 10, 16:13:20 GMT+0 - Investigating - Our auth provider (Clerk) is experiencing a degraded performance. We are seeing elevated loading times on Cognizo and issues with logging in. For more information, follow: &lt;https://status.clerk.com/incidents/01KHVBF47Q3SDK1VX7ZNHQ316R&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 29 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>16:42:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. We are seeing a complete recovery across all services..</p>
<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>16:32:46</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our third party provider has fixed the downstream problem and we are observing increased performance and all logins should now be operational..</p>
<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>16:26:34</var> GMT+0</small><br><strong>Identified</strong> -
  Issue has been identified by the third party provider and a fix is being implemented. For more information: &lt;https://status.clerk.com/incidents/01KHVBF47Q3SDK1VX7ZNHQ316R&gt;.</p>
<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>16:13:20</var> GMT+0</small><br><strong>Investigating</strong> -
  Our auth provider (Clerk) is experiencing a degraded performance. We are seeing elevated loading times on Cognizo and issues with logging in. For more information, follow: &lt;https://status.clerk.com/incidents/01KHVBF47Q3SDK1VX7ZNHQ316R&gt;.</p>
]]>
  </content:encoded>
  <pubDate>Tue, 10 Mar 2026 16:13:20 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmmkt7fn604qsdx0cy6kapf3y</link>
  <guid>https://status.cognizo.ai/incident/cmmkt7fn604qsdx0cy6kapf3y</guid>
</item>

<item>
  <title>Logging in and load times is experiencing degraded performance</title>
  <description>
    Type: Incident
    Duration: 2 hours and 13 minutes

    Affected Components: , 
Cognizo App →
    Feb 19, 18:41:14 GMT+0 - Resolved - This incident has been resolved. We are seeing a complete recovery across all services. Feb 19, 17:48:19 GMT+0 - Monitoring - Our third party provider has fixed the downstream problem and we are observing increased performance and all logins should now be operational.  Feb 19, 16:29:21 GMT+0 - Identified - Issue has been identified by the third party provider and a fix is being implemented. For more information: &lt;https://status.clerk.com/incidents/01KHVBF47Q3SDK1VX7ZNHQ316R&gt; Feb 19, 16:28:22 GMT+0 - Investigating - Our auth provider (Clerk) is experiencing a degraded performance. We are seeing elevated loading times on Cognizo and issues with logging in. For more information, follow: &lt;https://status.clerk.com/incidents/01KHVBF47Q3SDK1VX7ZNHQ316R&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>18:41:14</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. We are seeing a complete recovery across all services..</p>
<p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>17:48:19</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our third party provider has fixed the downstream problem and we are observing increased performance and all logins should now be operational. .</p>
<p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>16:29:21</var> GMT+0</small><br><strong>Identified</strong> -
  Issue has been identified by the third party provider and a fix is being implemented. For more information: &lt;https://status.clerk.com/incidents/01KHVBF47Q3SDK1VX7ZNHQ316R&gt;.</p>
<p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>16:28:22</var> GMT+0</small><br><strong>Investigating</strong> -
  Our auth provider (Clerk) is experiencing a degraded performance. We are seeing elevated loading times on Cognizo and issues with logging in. For more information, follow: &lt;https://status.clerk.com/incidents/01KHVBF47Q3SDK1VX7ZNHQ316R&gt;.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 19 Feb 2026 16:28:22 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmltodkwn06bce0oe0r5887lg</link>
  <guid>https://status.cognizo.ai/incident/cmltodkwn06bce0oe0r5887lg</guid>
</item>

<item>
  <title>Cognizo is experiencing failures due to a database outage</title>
  <description>
    Type: Incident
    Duration: 5 hours and 37 minutes

    Affected Components: , 
Cognizo App →
    Feb 13, 01:49:00 GMT+0 - Resolved - This incident has been resolved. Cognizo has been restored and is fully operational. Feb 13, 01:31:28 GMT+0 - Monitoring - Our servers are recovering as our database provider addresses the underlying issue. The platform should now be accessible for all users. We&#039;ll continue monitoring as the situation fully resolves. Feb 12, 22:01:40 GMT+0 - Identified - We have identified an issue impacting access to our platform, caused by an outage on our cloud database provider’s side (Supabase). Their team is actively engaged and working on a fix, and we are monitoring progress closely.  
  
Additional information can be found on their status page: &lt;https://status.supabase.com/&gt; Feb 12, 21:47:32 GMT+0 - Investigating - We are currently investigating this incident. This is related to our database provider having increased problems and details can be tracked here: &lt;https://status.supabase.com/&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 37 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>01:49:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. Cognizo has been restored and is fully operational..</p>
<p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>01:31:28</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our servers are recovering as our database provider addresses the underlying issue. The platform should now be accessible for all users. We&#039;ll continue monitoring as the situation fully resolves..</p>
<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>22:01:40</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified an issue impacting access to our platform, caused by an outage on our cloud database provider’s side (Supabase). Their team is actively engaged and working on a fix, and we are monitoring progress closely.  
  
Additional information can be found on their status page: &lt;https://status.supabase.com/&gt;.</p>
<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>21:47:32</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident. This is related to our database provider having increased problems and details can be tracked here: &lt;https://status.supabase.com/&gt;.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 12 Feb 2026 21:47:32 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmljzp2ay06c610hxqn3rgbiy</link>
  <guid>https://status.cognizo.ai/incident/cmljzp2ay06c610hxqn3rgbiy</guid>
</item>

<item>
  <title>Prompt visibility numbers are degraded for some users</title>
  <description>
    Type: Incident
    Duration: 14 hours and 30 minutes

    Affected Components: , 
Cognizo App →
    Nov 20, 21:29:47 GMT+0 - Resolved - The issue with Perplexity data collection has been resolved. It was caused by a problem with our most recent change. We worked to fix it, and took internal measures to make sure this won&#039;t repeat. Thanks for your patience. Nov 20, 14:42:51 GMT+0 - Monitoring - We have resolved the issue related to degraded prompt visibility numbers at this time for all users. Users may observe that the main scores on visibility, share of voice and sentiment is not visible on line graphs as we are monitoring the platform. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo App. Nov 20, 08:30:00 GMT+0 - Identified - We have identified the problem and the team is working on a fix.  Nov 20, 07:00:00 GMT+0 - Investigating - We are currently investigating an incident where prompt visibility numbers are reflecting the same values as overall visibility numbers. This should impact visibility graphs on prompt details.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>21:29:47</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue with Perplexity data collection has been resolved. It was caused by a problem with our most recent change. We worked to fix it, and took internal measures to make sure this won&#039;t repeat. Thanks for your patience..</p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>14:42:51</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have resolved the issue related to degraded prompt visibility numbers at this time for all users. Users may observe that the main scores on visibility, share of voice and sentiment is not visible on line graphs as we are monitoring the platform. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo App..</p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the problem and the team is working on a fix. .</p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating an incident where prompt visibility numbers are reflecting the same values as overall visibility numbers. This should impact visibility graphs on prompt details. .</p>
]]>
  </content:encoded>
  <pubDate>Thu, 20 Nov 2025 07:00:00 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmi7c4aab04kipccwkqyceeae</link>
  <guid>https://status.cognizo.ai/incident/cmi7c4aab04kipccwkqyceeae</guid>
</item>

<item>
  <title>Degraded Search Performance with ChatGPT Scraper</title>
  <description>
    Type: Incident
    Duration: 14 days, 8 hours and 5 minutes

    Affected Components: ChatGPT Service
    Oct 23, 20:17:00 GMT+0 - Resolved - We have resolved the issue related to ChatGPT data collection at this time for all users. However, there may still be some delays as we work with the provider to finalize the fix. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo App. Oct 23, 16:17:00 GMT+0 - Monitoring - We have resolved the issue related to ChatGPT data collection at this time for all users. However, there may still be some delays as we work with the provider to finalize the fix. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo App. Oct 23, 15:17:57 GMT+0 - Identified - We have identified the issue related to ChatGPT data collection. The issue was caused by a problem with one of our service providers who does the data collection for ChatGPT. We are working with the provider currently and working to resolve it as soon as possible. Oct 9, 12:11:48 GMT+0 - Investigating - We’re investigating an issue affecting ChatGPT data collection. This is causing some AI Search queries to bypass data retrieval and default to direct model responses. As a result, users may notice fewer citations and missing source references in certain outputs. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 days, 8 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>20:17:00</var> GMT+0</small><br><strong>Resolved</strong> -
  We have resolved the issue related to ChatGPT data collection at this time for all users. However, there may still be some delays as we work with the provider to finalize the fix. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo App..</p>
<p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>16:17:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have resolved the issue related to ChatGPT data collection at this time for all users. However, there may still be some delays as we work with the provider to finalize the fix. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo App..</p>
<p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>15:17:57</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue related to ChatGPT data collection. The issue was caused by a problem with one of our service providers who does the data collection for ChatGPT. We are working with the provider currently and working to resolve it as soon as possible..</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>12:11:48</var> GMT+0</small><br><strong>Investigating</strong> -
  We’re investigating an issue affecting ChatGPT data collection. This is causing some AI Search queries to bypass data retrieval and default to direct model responses. As a result, users may notice fewer citations and missing source references in certain outputs..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 9 Oct 2025 12:11:48 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmgjdnbw4009izypneffne42r</link>
  <guid>https://status.cognizo.ai/incident/cmgjdnbw4009izypneffne42r</guid>
</item>

<item>
  <title>Degraded performance with the Perplexity Scraper</title>
  <description>
    Type: Incident
    Duration: 4 days, 22 hours and 23 minutes

    Affected Components: , Perplexity Service, ChatGPT Service, Google AI Overviews Service, 
Data Collection Services →
    Oct 8, 12:09:00 GMT+0 - Resolved - The issue with Perplexity data collection has been resolved. It was caused by a problem with one of our service providers. We worked with them to fix it, and everything is now back to normal. Thanks for your patience. Oct 7, 17:08:14 GMT+0 - Monitoring - We have resolved the issue related to Perplexity data collection at this time for all users. However, there may still be some delays as we work with the provider to finalize the fix. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo App. Oct 5, 13:46:00 GMT+0 - Identified - We have identified the issue related to Perplexity data collection. The issue was caused by a problem with one of our service providers who does the data collection for perplexity. We are working with the provider currently and working to resolve it as soon as possible. Oct 4, 13:46:00 GMT+0 - Investigating - We are investigating an issue with Perplexity data collection. This is affecting some users when they make changes to their brands, keywords, and prompts and will cause extended loading screens in the Cognizo Platform. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 22 hours and 23 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>12:09:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue with Perplexity data collection has been resolved. It was caused by a problem with one of our service providers. We worked with them to fix it, and everything is now back to normal. Thanks for your patience..</p>
<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>17:08:14</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have resolved the issue related to Perplexity data collection at this time for all users. However, there may still be some delays as we work with the provider to finalize the fix. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo App..</p>
<p><small>Oct <var data-var='date'> 5</var>, <var data-var='time'>13:46:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue related to Perplexity data collection. The issue was caused by a problem with one of our service providers who does the data collection for perplexity. We are working with the provider currently and working to resolve it as soon as possible..</p>
<p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>13:46:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating an issue with Perplexity data collection. This is affecting some users when they make changes to their brands, keywords, and prompts and will cause extended loading screens in the Cognizo Platform..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 4 Oct 2025 13:46:00 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmgdra17x0a3jjzcc1wumgtx8</link>
  <guid>https://status.cognizo.ai/incident/cmgdra17x0a3jjzcc1wumgtx8</guid>
</item>

<item>
  <title>Partial outage caused by cloud hosting provider</title>
  <description>
    Type: Incident
    Duration: 1 hour and 45 minutes

    Affected Components: , 
Cognizo App →
    Sep 18, 04:03:14 GMT+0 - Resolved - The issue impacting access to our platform has been resolved. It was caused by an outage with our cloud hosting provider. Their team implemented a fix, and full access has now been restored.

Thank you for your patience. Sep 18, 02:27:31 GMT+0 - Monitoring - We are seeing recovery following the outage with our cloud hosting provider (Railway). Their team has implemented a fix and we are monitoring platform access to ensure stability. Some users may continue to experience intermittent issues as the fix is finalized. Sep 18, 02:23:58 GMT+0 - Identified - We have identified an issue impacting access to our platform, caused by an outage on our cloud hosting provider’s side (Railway). Their team is actively engaged and working on a fix, and we are monitoring progress closely. Sep 18, 02:18:41 GMT+0 - Investigating - We are observing an issue with our server provider. This is impacting access to our platform for some users. We are working with the team to resolve the issue as quickly as possible. For additional information, please refer to: &lt;https://status.railway.com/&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>04:03:14</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue impacting access to our platform has been resolved. It was caused by an outage with our cloud hosting provider. Their team implemented a fix, and full access has now been restored.

Thank you for your patience..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>02:27:31</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are seeing recovery following the outage with our cloud hosting provider (Railway). Their team has implemented a fix and we are monitoring platform access to ensure stability. Some users may continue to experience intermittent issues as the fix is finalized..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>02:23:58</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified an issue impacting access to our platform, caused by an outage on our cloud hosting provider’s side (Railway). Their team is actively engaged and working on a fix, and we are monitoring progress closely..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>02:18:41</var> GMT+0</small><br><strong>Investigating</strong> -
  We are observing an issue with our server provider. This is impacting access to our platform for some users. We are working with the team to resolve the issue as quickly as possible. For additional information, please refer to: &lt;https://status.railway.com/&gt;.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 18 Sep 2025 02:18:41 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmfos7oqe00fytnxca6vfoatm</link>
  <guid>https://status.cognizo.ai/incident/cmfos7oqe00fytnxca6vfoatm</guid>
</item>

<item>
  <title>Degraded Performance on Prompts and Citations</title>
  <description>
    Type: Incident
    Duration: 5 days, 1 hour and 5 minutes

    Affected Components: Landing Page, , ChatGPT Service, Perplexity Service, Google AI Overviews Service, 
Cognizo App →
    Sep 29, 16:52:37 GMT+0 - Resolved - This incident has been resolved. Sep 18, 02:15:13 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.  Sep 10, 14:41:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Some users may notice citation attributions showing incorrect results.  Sep 4, 07:20:00 GMT+0 - Identified - We have confirmed that the performance degradation is caused by an issue in how some providers we use capture citations. Our team is actively working on a resolution and addressing this with the highest priority. Sep 3, 15:47:00 GMT+0 - Investigating - We are currently investigating an issue that is causing slow performance and timeouts in the \_Prompts\_ and \_Citations\_ modules. Some users may experience degraded performance when accessing these areas. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 1 hour and 5 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>16:52:37</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>02:15:13</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result. .</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>14:41:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident. Some users may notice citation attributions showing incorrect results. .</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>07:20:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have confirmed that the performance degradation is caused by an issue in how some providers we use capture citations. Our team is actively working on a resolution and addressing this with the highest priority..</p>
<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>15:47:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating an issue that is causing slow performance and timeouts in the \_Prompts\_ and \_Citations\_ modules. Some users may experience degraded performance when accessing these areas..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 3 Sep 2025 15:47:00 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmepv45eg000113281ror4r8v</link>
  <guid>https://status.cognizo.ai/incident/cmepv45eg000113281ror4r8v</guid>
</item>

<item>
  <title>Degraded Experience in ChatGPT Data Collection</title>
  <description>
    Type: Incident
    Duration: 9 days, 23 hours and 41 minutes

    Affected Components: ChatGPT Service
    Jul 31, 12:40:42 GMT+0 - Resolved - The issue with ChatGPT data collection has been resolved. It was caused by a problem with one of our service providers. We worked with them to fix it, and everything is now back to normal.

Thanks for your patience. Jul 24, 12:39:20 GMT+0 - Monitoring - We have resolved the issue related to ChatGPT data collection at this time for all users. However, there may still be some delays as we work with the provider to finalize the fix. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo Platform. Jul 21, 13:00:00 GMT+0 - Investigating - We are investigating an issue with ChatGPT data collection. This is affecting some users when they make changes to their brands, keywords, and prompts and will cause extended loading screens in the Cognizo Platform. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 days, 23 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:40:42</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue with ChatGPT data collection has been resolved. It was caused by a problem with one of our service providers. We worked with them to fix it, and everything is now back to normal.

Thanks for your patience..</p>
<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>12:39:20</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have resolved the issue related to ChatGPT data collection at this time for all users. However, there may still be some delays as we work with the provider to finalize the fix. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo Platform..</p>
<p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating an issue with ChatGPT data collection. This is affecting some users when they make changes to their brands, keywords, and prompts and will cause extended loading screens in the Cognizo Platform..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 21 Jul 2025 13:00:00 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmdecxk5p00302ki5s170syte</link>
  <guid>https://status.cognizo.ai/incident/cmdecxk5p00302ki5s170syte</guid>
</item>

<item>
  <title>Degraded performance with the Perplexity Scraper</title>
  <description>
    Type: Incident
    Duration: 5 days, 11 hours and 57 minutes

    Affected Components: , Perplexity Service, 
Cognizo App →
    Jul 5, 22:56:36 GMT+0 - Resolved - The issue with Perplexity data collection has been resolved. It was caused by a problem with one of our service providers. We worked with them to fix it, and everything is now back to normal. Thanks for your patience. Jul 1, 17:23:05 GMT+0 - Monitoring - We have resolved the issue related to Perplexity data collection at this time for all users. However, there may still be some delays as we work with the provider to finalize the fix. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo App. Jul 1, 13:35:56 GMT+0 - Identified - We have identified the issue related to Perplexity data collection. The issue was caused by a problem with one of our service providers who does the data collection for perplexity. We are working with the provider currently and working to resolve it as soon as possible. Jun 30, 11:00:00 GMT+0 - Investigating - We are investigating an issue with Perplexity data collection. This is affecting some users when they make changes to their brands, keywords, and prompts and will cause extended loading screens in the Cognizo Platform. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 11 hours and 57 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>22:56:36</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue with Perplexity data collection has been resolved. It was caused by a problem with one of our service providers. We worked with them to fix it, and everything is now back to normal. Thanks for your patience..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>17:23:05</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have resolved the issue related to Perplexity data collection at this time for all users. However, there may still be some delays as we work with the provider to finalize the fix. If you are having issues please reach out to us via live chat in the bottom right corner of the Cognizo App..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>13:35:56</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue related to Perplexity data collection. The issue was caused by a problem with one of our service providers who does the data collection for perplexity. We are working with the provider currently and working to resolve it as soon as possible..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating an issue with Perplexity data collection. This is affecting some users when they make changes to their brands, keywords, and prompts and will cause extended loading screens in the Cognizo Platform..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 30 Jun 2025 11:00:00 +0000</pubDate>
  <link>https://status.cognizo.ai/incident/cmcklq8w9000eijk19bqkub3q</link>
  <guid>https://status.cognizo.ai/incident/cmcklq8w9000eijk19bqkub3q</guid>
</item>

  </channel>
  </rss>