urn:noticeable:projects:1VJrRqr3h4VWkFv4IWkhipregistry.co2021-12-12T22:47:34.268ZCopyright © Product UpdatesNoticeablehttps://storage.noticeable.io/projects/1VJrRqr3h4VWkFv4IWkh/newspages/jT8z6s2X1NBdTeejkUBW/01h55ta3gs2tb38cewvncbbc5h-header-logo.pnghttps://storage.noticeable.io/projects/1VJrRqr3h4VWkFv4IWkh/newspages/jT8z6s2X1NBdTeejkUBW/01h55ta3gs2tb38cewvncbbc5h-header-logo.png#de007affurn:noticeable:publications:R3H1Cnywat35lBmACdiq2021-12-02T17:10:05.063Z2021-12-12T22:47:34.268Z

Starting 12:30pm UTC and until 5:15 UTC on December 2, 2021, usage reporting was delayed for some accounts. This incident was not affecting the API. However, the usage displayed on the dashboard was incorrect during the incident. The cause

<p>Starting 12:30pm UTC and until 5:15 UTC on December 2, 2021, usage reporting was delayed for some accounts. </p><p><strong>This incident was not affecting the API</strong>. However, the usage displayed on the dashboard was incorrect during the incident.</p><p>The cause of the issue has been identified. The incident is resolved and the usage reported on your dashboard is now correct (including the period that was under issue).</p><p></p><p></p>Ipregistry Team[email protected]urn:noticeable:publications:NL2x3hgiITmYIzISK8oh2021-08-14T08:16:46.833Z2021-08-31T16:35:44.884Z

The issue is now fully resolved. Customers impacted by automatic renewal have been contacted by email. The disruption was caused by a corruption of our main database storing API keys and credits balance. We are sorry and apologize for what

<p>The issue is now fully resolved. Customers impacted by automatic renewal have been contacted by email. The disruption was caused by a corruption of our main database storing API keys and credits balance. We are sorry and apologize for what you experienced. Again, thanks for your patience and trust in these hard times. </p><p>Do not hesitate to <a href="mailto:[email protected]" rel="noopener nofollow" target="_blank">drop us a line</a> if you have any questions or concerns.</p><p><strong><span style="text-decoration: underline">15/08/2021, 00:10am (UTC+2)</span></strong>: <br>Historical usage has been restored and usage reporting is now working in near real-time. We will send an email to customers who got impacted by automatic renewal within the next 24 hours. </p><p><strong><span style="text-decoration: underline">14/08/2021, 01:00pm (UTC+2)</span></strong>: <br>The issue we experienced this morning was caused by a database corruption. A backup from early this morning has been used to restore data. Historical usage is aggregated internally but not yet displaying on the Ipregistry dashboard. We’re working on fixing it. We are sorry and apologize about what you experience. Thanks for your patience and trust in these hard times. </p><p><strong><span style="text-decoration: underline">14/08/2021, 10:38am (UTC+2)</span></strong>: <br>The API is working again from all locations. There is still an issue with usage reported in the dashboard but we are on it. Customers affected by automatic renewal will be contacted soon.</p><p><strong><span style="text-decoration: underline">14/08/2021, 10:00am (UTC+2)</span></strong>: <br>We’re experiencing a service disruption and are investigating the issue. We are doing our best to restore everything as soon as possible. Thanks for your patience and trust. We will keep you updated as soon as possible.</p>Ipregistry Team[email protected]