
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      
      <title>AcoustID Status</title>
      <link>https://status.acoustid.org/</link>
      <description>Incident history</description>
      <generator>github.com/cstate</generator>
      <language>en</language>
      
      <lastBuildDate>Sat, 29 Aug 2026 11:20:00 +0000</lastBuildDate>
      
      
      
        <atom:link href="https://status.acoustid.org/index.xml" rel="self" type="application/rss+xml" />
      
      
      
        <item>
          <title>[Resolved] Submissions Failing</title>
          <link>https://status.acoustid.org/issues/2026-08-29-submissions-failing/</link>
          <pubDate>Sat, 29 Aug 2026 11:20:00 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2026-08-29-submissions-failing/</guid>
          <category>2026-08-30 04:43:37</category>
          <description>&lt;p&gt;Fingerprint submissions failed for about 17 hours, from 11:20 UTC on 29 August
until 04:43 UTC on 30 August. Lookups and the website were unaffected
throughout.&lt;/p&gt;
&lt;p&gt;Submissions made during that window were rejected with an error and were not
stored. Submissions have been accepted normally since 04:43 UTC. If you
submitted fingerprints during the window, they will need to be submitted again.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Lookup errors</title>
          <link>https://status.acoustid.org/issues/2026-08-11-lookup-errors/</link>
          <pubDate>Tue, 11 Aug 2026 22:15:00 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2026-08-11-lookup-errors/</guid>
          <category>2026-08-11 22:21:00</category>
          <description>&lt;p&gt;Fingerprint lookups returned errors for about five minutes late on 11 August,
after a network switch failure at our hosting provider took one of our servers
offline. Submissions were affected to a much smaller degree over the same
window.&lt;/p&gt;
&lt;p&gt;The service recovered on its own and lookups have been working normally since
22:21 UTC. Affected requests failed outright rather than returning a wrong
answer, so they can simply be retried. No data was lost.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Fingerprint database maintenance</title>
          <link>https://status.acoustid.org/issues/2026-07-28-fingerprint-db-migration/</link>
          <pubDate>Tue, 28 Jul 2026 06:40:00 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2026-07-28-fingerprint-db-migration/</guid>
          <category>2026-07-28 22:55:00</category>
          <description>&lt;p&gt;&lt;strong&gt;Resolved.&lt;/strong&gt; The maintenance is complete and the backlog of submissions has been fully processed. Lookups, the website, submissions and indexing are all working normally, and newly submitted fingerprints are being indexed as they arrive.&lt;/p&gt;
&lt;p&gt;Nothing was lost — fingerprints submitted while indexing was paused have all been processed.&lt;/p&gt;
&lt;p&gt;Earlier updates:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;19:25 UTC&lt;/strong&gt; — indexing resumed; a backlog remained to be worked through.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;17:50 UTC&lt;/strong&gt; — maintenance largely complete; site and lookups working, indexing still paused.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;15:05 UTC&lt;/strong&gt; — running longer than expected, continuing into the evening.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;08:05 UTC&lt;/strong&gt; — maintenance began, estimated at around 10 hours.&lt;/li&gt;
&lt;/ul&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Ingest database migration</title>
          <link>https://status.acoustid.org/issues/2026-07-27-ingest-db-migration/</link>
          <pubDate>Mon, 27 Jul 2026 13:45:00 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2026-07-27-ingest-db-migration/</guid>
          <category>2026-07-27 15:10:00</category>
          <description>&lt;p&gt;&lt;strong&gt;Complete.&lt;/strong&gt; The ingest database has been moved to a new cluster. Submissions
are being accepted and processed normally and the queue is clear.&lt;/p&gt;
&lt;p&gt;Submissions made during the maintenance window were queued rather than
processed, and have since all been processed — if you submitted fingerprints
this afternoon and they did not appear straight away, they are indexed now.
Nothing was lost.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;One brief interruption, at 14:53 UTC&lt;/strong&gt;, affected about eight requests across
the API and the website while the database was restarted. Service was restored
within a minute.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Delayed processing of submitted fingerprints</title>
          <link>https://status.acoustid.org/issues/2026-07-26-import-backlog/</link>
          <pubDate>Sun, 26 Jul 2026 20:50:00 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2026-07-26-import-backlog/</guid>
          <category>2026-07-27 14:41:00</category>
          <description>&lt;p&gt;&lt;strong&gt;Resolved.&lt;/strong&gt; The backlog cleared at 14:41 UTC. It peaked at around 473,000
queued submissions and was worked down over the course of the day, at times
processing more than 85,000 per hour. Nothing was lost — every submission was
queued and has been processed.&lt;/p&gt;
&lt;p&gt;Progress during the day:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;14:30 UTC&lt;/strong&gt; — about 17,000 remaining, processing around 75,000 per hour.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;13:30 UTC&lt;/strong&gt; — about 80,000 remaining, processing around 85,000 per hour.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;12:30 UTC&lt;/strong&gt; — about 143,000 remaining, processing around 55,000 per hour.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;11:10 UTC&lt;/strong&gt; — about 190,000 remaining, processing around 68,000 per hour.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Lookups and the website were not affected at any point.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Brief burst of API errors during database maintenance</title>
          <link>https://status.acoustid.org/issues/2026-07-26-api-errors-evening/</link>
          <pubDate>Sun, 26 Jul 2026 18:24:00 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2026-07-26-api-errors-evening/</guid>
          <category>2026-07-26 18:26:00</category>
          <description>&lt;p&gt;A brief burst of API requests failed during planned database maintenance,
lasting under a minute. No data was lost — affected requests failed outright and
could be retried.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] API errors during database maintenance</title>
          <link>https://status.acoustid.org/issues/2026-07-26-api-errors-morning/</link>
          <pubDate>Sun, 26 Jul 2026 10:45:00 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2026-07-26-api-errors-morning/</guid>
          <category>2026-07-26 11:05:00</category>
          <description>&lt;p&gt;A subset of API requests failed for about 20 minutes during planned database
maintenance. No data was lost — affected requests failed outright and could be
retried.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] All AcoustID services are unavailable</title>
          <link>https://status.acoustid.org/issues/2021-03-02-global-downtime/</link>
          <pubDate>Tue, 02 Mar 2021 15:00:00 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2021-03-02-global-downtime/</guid>
          <category>2021-03-05 12:00:00</category>
          <description>&lt;p&gt;All services are having problems due to a large-scale incident. We are working on resolving the problem as soon as possible.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] App DB Connection Errors</title>
          <link>https://status.acoustid.org/issues/2020-01-24-app-db-connection-errors/</link>
          <pubDate>Fri, 24 Jan 2020 07:24:25 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2020-01-24-app-db-connection-errors/</guid>
          <category>2020-01-24 07:28:31</category>
          <description>&lt;p&gt;Most services are having problems due to failing connections to the PostgreSQL database (app).&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Redis Down</title>
          <link>https://status.acoustid.org/issues/2020-01-22-redis-downtime/</link>
          <pubDate>Wed, 22 Jan 2020 15:56:09 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2020-01-22-redis-downtime/</guid>
          <category>2020-01-22 15:01:21</category>
          <description>&lt;p&gt;Most services are having problems because of our Redis DB cluster unexpectedly restarting.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Import Stopped</title>
          <link>https://status.acoustid.org/issues/2019-10-24-import-stopped/</link>
          <pubDate>Thu, 24 Oct 2019 16:24:00 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2019-10-24-import-stopped/</guid>
          <category>2019-10-30 12:00:00</category>
          <description>&lt;p&gt;While we are migrating the master database to our new Kubernetes cluster, submission import process is stopped. It will be restored in a few days.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Post-Migration Website Issues</title>
          <link>https://status.acoustid.org/issues/2019-10-24-post-migration-website-issues/</link>
          <pubDate>Thu, 24 Oct 2019 16:24:00 +0000</pubDate>
          <guid>https://status.acoustid.org/issues/2019-10-24-post-migration-website-issues/</guid>
          <category>2019-10-27 15:20:00</category>
          <description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - All website issues have been resolved.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - After migration the rest of AcoustID&amp;rsquo;s infrastructure to Kubernetes, the website has a few known issues.&lt;/p&gt;
</description>
        </item>
      
    </channel>
  </rss>

