<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link rel="alternate" type="text/html" href="https://status.contentignite.com"/>
    <title>Logging-database on Content Ignite</title>
    <link>https://status.contentignite.com/affected/logging-database/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2020-08-21T08:10:41+00:00</lastBuildDate>
    <updated>2020-08-21T08:10:41+00:00</updated>
    
    
    
      <atom:link href="https://status.contentignite.com/affected/logging-database/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] Intermittent Logging Outages</title>
        <link>https://status.contentignite.com/issues/2020-08-21-intermittent-logging-outages/</link>
        <pubDate>Fri, 21 Aug 2020 08:10:41 +0000</pubDate>
        <guid>https://status.contentignite.com/issues/2020-08-21-intermittent-logging-outages/</guid>
        <category>2020-08-21T13:14:00.000Z</category>
        <description>Investigating - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.
Investigating - We are experiencing intermittent logging outages that last between 5 and 10 minutes. We are still investigating the cause. The outages are represented by the spikes in the graph below:</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are experiencing intermittent logging outages that last between 5 and 10 minutes. We are still investigating the cause. The outages are represented by the spikes in the graph below:&lt;/p&gt;

&lt;p&gt;&lt;img src=&#34;https://status.contentignite.com/img/screenshot-2020-08-21-at-14.36.43.png&#34; alt=&#34;Line graph showing outages as spikes&#34; title=&#34;Outages&#34; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We have only seen less than a handful of micro outages in the past two weeks, with measures to alleviate helping significantly. We are keeping this issue open as we have yet to receive a final verdict on the root cause from our infrastructure provider (Google). We will update once we receive further information.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Database Outage</title>
        <link>https://status.contentignite.com/issues/2020-08-06-database-outage/</link>
        <pubDate>Wed, 05 Aug 2020 12:29:00 +0000</pubDate>
        <guid>https://status.contentignite.com/issues/2020-08-06-database-outage/</guid>
        <category>2020-08-06T07:51:00.000Z</category>
        <description>Investigating - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.
Resolved - This incident has now been resolved. This issue would have effected impression reporting. We are continuing to look into the the cause of this issue, and will look to update you shortly on the cause and any consequences of the down time.</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - This incident has now been resolved. This issue would have effected impression reporting. We are continuing to look into the the cause of this issue, and will look to update you shortly on the cause and any consequences of the down time.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - We can confirm that all systems have been running stable since this issue was resolved. Customers will find a notice in the admin platform informing them of this incident.&lt;/p&gt;

&lt;p&gt;SaaS customers will show no impressions during this outage, and will not be charged accordingly. P&amp;amp;P customers may see reporting discrepancies during this period, but earnings will not be effected.&lt;/p&gt;

&lt;p&gt;The cause seems to be a system failure in our DBaaS, where no single event source could be detected. We will be monitoring performance and looking for ways to protect against this type of incident going forwards.&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
