<?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.rain.xyz/"/>
    <title>Core API on Rain Platform Status</title>
    <link>https://status.rain.xyz/affected/core-api/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2026-09-28T18:53:00+00:00</lastBuildDate>
    <updated>2026-09-28T18:53:00+00:00</updated>
    
    
    <copyright>Signify Holdings, Inc. &#34;Rain&#34;</copyright>
    
      <atom:link href="https://status.rain.xyz/affected/core-api/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] API issues and unexpected declines</title>
        <link>https://status.rain.xyz/issues/2026-09-28-api-issues-unexpected-declines/</link>
        <pubDate>Mon, 28 Sep 2026 18:53:00 +0000</pubDate>
        <guid>https://status.rain.xyz/issues/2026-09-28-api-issues-unexpected-declines/</guid>
        <category>2026-09-28T19:35:00Z</category>
        <description>&lt;span class=&#34;faded&#34;&gt;(19:35 UTC — Sep 28)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/em&gt; - Between 18:53 and 19:35 UTC today (September 28, 2026), the Rain API experienced an issue that affected service for some partners. The issue has been resolved, and systems are operating normally.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re investigating the root cause. We apologize for any disruption this may have caused.&lt;/p&gt;

  &lt;span class=&#34;faded&#34;&gt;(19:20 UTC — Sep 28)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/em&gt; - We have isolated the issue and have applied a fix. We are observing improved API responsiveness and transaction authorizations.&lt;/p&gt;</description>
        <content type="html">
  &lt;span class=&#34;faded&#34;&gt;(19:35 UTC — Sep 28)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/em&gt; - Between 18:53 and 19:35 UTC today (September 28, 2026), the Rain API experienced an issue that affected service for some partners. The issue has been resolved, and systems are operating normally.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re investigating the root cause. We apologize for any disruption this may have caused.&lt;/p&gt;

  &lt;span class=&#34;faded&#34;&gt;(19:20 UTC — Sep 28)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/em&gt; - We have isolated the issue and have applied a fix. We are observing improved API responsiveness and transaction authorizations.&lt;/p&gt;

  &lt;span class=&#34;faded&#34;&gt;(18:53 UTC — Sep 28)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/em&gt; - We are investigating an issue that is causing unexpected declines for transactions starting at 18:53 UTC. We are also observing issues with API responsiveness.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Elevated error rate across API endpoints</title>
        <link>https://status.rain.xyz/issues/2026-06-25-elevated-api-error-rate/</link>
        <pubDate>Thu, 25 Jun 2026 08:57:48 +0000</pubDate>
        <guid>https://status.rain.xyz/issues/2026-06-25-elevated-api-error-rate/</guid>
        <category>2026-06-25T12:30:00Z</category>
        <description>&lt;span class=&#34;faded&#34;&gt;(12:30 UTC — Jun 25)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/em&gt; - API error rates have returned to normal. The issue was caused by an expired encryption certificate. Once the appropriate certificate was provided and updated, traffic resolved. The incident was initially raised at 08:57 UTC and was resolved by 12:30 UTC.&lt;/p&gt;</description>
        <content type="html">
  &lt;span class=&#34;faded&#34;&gt;(12:30 UTC — Jun 25)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/em&gt; - API error rates have returned to normal. The issue was caused by an expired encryption certificate. Once the appropriate certificate was provided and updated, traffic resolved. The incident was initially raised at 08:57 UTC and was resolved by 12:30 UTC.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Partial outage of API processing</title>
        <link>https://status.rain.xyz/issues/2026-04-24-api-partial-outage/</link>
        <pubDate>Fri, 24 Apr 2026 07:08:00 +0000</pubDate>
        <guid>https://status.rain.xyz/issues/2026-04-24-api-partial-outage/</guid>
        <category>2026-04-24T07:18:00Z</category>
        <description>&lt;span class=&#34;faded&#34;&gt;(07:18 UTC — Apr 24)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/em&gt; - API processing has fully recovered following restoration of service at our upstream API provider. Authorizations were not affected at any point during this incident.&lt;/p&gt;</description>
        <content type="html">
  &lt;span class=&#34;faded&#34;&gt;(07:18 UTC — Apr 24)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/em&gt; - API processing has fully recovered following restoration of service at our upstream API provider. Authorizations were not affected at any point during this incident.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Elevated 500 errors on API endpoints</title>
        <link>https://status.rain.xyz/issues/2026-04-22-api-500-errors/</link>
        <pubDate>Wed, 22 Apr 2026 18:28:00 +0000</pubDate>
        <guid>https://status.rain.xyz/issues/2026-04-22-api-500-errors/</guid>
        <category>2026-04-22T18:32:00Z</category>
        <description>&lt;span class=&#34;faded&#34;&gt;(18:32 UTC — Apr 22)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/em&gt; - API error rates have returned to normal. The issue was isolated to our API endpoints and did not impact authorizations.&lt;/p&gt;

  &lt;span class=&#34;faded&#34;&gt;(18:28 UTC — Apr 22)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/em&gt; - We are seeing an elevated rate of 500 errors on our API endpoints due to an issue with our underlying cloud services. Authorizations are not affected. Our team is investigating.&lt;/p&gt;</description>
        <content type="html">
  &lt;span class=&#34;faded&#34;&gt;(18:32 UTC — Apr 22)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/em&gt; - API error rates have returned to normal. The issue was isolated to our API endpoints and did not impact authorizations.&lt;/p&gt;

  &lt;span class=&#34;faded&#34;&gt;(18:28 UTC — Apr 22)&lt;/span&gt;


&lt;p&gt;&lt;em&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/em&gt; - We are seeing an elevated rate of 500 errors on our API endpoints due to an issue with our underlying cloud services. Authorizations are not affected. Our team is investigating.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] System Degradation</title>
        <link>https://status.rain.xyz/issues/2026-03-06-system-degradation/</link>
        <pubDate>Fri, 06 Mar 2026 18:36:00 +0000</pubDate>
        <guid>https://status.rain.xyz/issues/2026-03-06-system-degradation/</guid>
        <category>2026-03-06 19:45:00</category>
        <description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - During a platform update, some in-flight requests failed due to connections not being properly refreshed. We performed a rolling restart of our services to resolve the issue with no downtime incurred. We will use this experience to further improve our platform. All services are fully restored and operating normally. 
  &lt;span class=&#34;faded&#34;&gt;(19:45 UTC — Mar 6)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - The system has stabilized and requests are processing normally. We are continuing to investigate root cause and will provide updates as we have more information. 
  &lt;span class=&#34;faded&#34;&gt;(19:15 UTC — Mar 6)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - During a platform update, some in-flight requests failed due to connections not being properly refreshed. We performed a rolling restart of our services to resolve the issue with no downtime incurred. We will use this experience to further improve our platform. All services are fully restored and operating normally. 
  &lt;span class=&#34;faded&#34;&gt;(19:45 UTC — Mar 6)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - The system has stabilized and requests are processing normally. We are continuing to investigate root cause and will provide updates as we have more information. 
  &lt;span class=&#34;faded&#34;&gt;(19:15 UTC — Mar 6)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are aware of degraded system performance with some requests failing. Our team is actively investigating. Funds are safe and we are working to restore full stability. 
  &lt;span class=&#34;faded&#34;&gt;(18:36 UTC — Mar 6)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Platform Impact</title>
        <link>https://status.rain.xyz/issues/2025-10-20-outage-google-cloud/</link>
        <pubDate>Mon, 20 Oct 2025 15:05:00 +0000</pubDate>
        <guid>https://status.rain.xyz/issues/2025-10-20-outage-google-cloud/</guid>
        <category>2025-10-22 12:38:00</category>
        <description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - The issue has been resolved. While our platform continued to handle authorizations and API calls, we experienced repeated failed requests to external services. All services are now operating normally. 
  &lt;span class=&#34;faded&#34;&gt;(12:38 UTC — Oct 22)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We&amp;rsquo;re continuing to look into any remaining performance issues and assessing potential impacts from external services. 
  &lt;span class=&#34;faded&#34;&gt;(19:51 UTC — Oct 20)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - The issue has been resolved. While our platform continued to handle authorizations and API calls, we experienced repeated failed requests to external services. All services are now operating normally. 
  &lt;span class=&#34;faded&#34;&gt;(12:38 UTC — Oct 22)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We&amp;rsquo;re continuing to look into any remaining performance issues and assessing potential impacts from external services. 
  &lt;span class=&#34;faded&#34;&gt;(19:51 UTC — Oct 20)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Elevated Latencies in Outgoing Webhooks</title>
        <link>https://status.rain.xyz/issues/2025-09-16-elevated-webhook-latencies/</link>
        <pubDate>Tue, 16 Sep 2025 20:01:00 +0000</pubDate>
        <guid>https://status.rain.xyz/issues/2025-09-16-elevated-webhook-latencies/</guid>
        <category>2025-09-16 20:59:00</category>
        <description>&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We&amp;rsquo;re currently experiencing elevated latencies in our outgoing webhook delivery system. Some webhook notifications may be delayed. We&amp;rsquo;re actively investigating the root cause and working to restore normal delivery times. 
  &lt;span class=&#34;faded&#34;&gt;(20:01 UTC — Sep 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Services are restored and we&amp;rsquo;ve identified root cause. Webhook delivery should be back to normal. We continue to observe and will provide a final update once investigation is complete.
  &lt;span class=&#34;faded&#34;&gt;(20:59 UTC — Sep 16)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We&amp;rsquo;re currently experiencing elevated latencies in our outgoing webhook delivery system. Some webhook notifications may be delayed. We&amp;rsquo;re actively investigating the root cause and working to restore normal delivery times. 
  &lt;span class=&#34;faded&#34;&gt;(20:01 UTC — Sep 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Services are restored and we&amp;rsquo;ve identified root cause. Webhook delivery should be back to normal. We continue to observe and will provide a final update once investigation is complete.
  &lt;span class=&#34;faded&#34;&gt;(20:59 UTC — Sep 16)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Platform Degraded During Cloud Provider Outage</title>
        <link>https://status.rain.xyz/issues/2025-06-12-outage-google-cloud/</link>
        <pubDate>Thu, 12 Jun 2025 18:01:00 +0000</pubDate>
        <guid>https://status.rain.xyz/issues/2025-06-12-outage-google-cloud/</guid>
        <category>2025-06-12 20:15:00</category>
        <description>&lt;p&gt;&lt;em&gt;Post-mortem&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Our public cloud provider had an incident on June 12, 2025 at 17:45 UTC taking large portions of their control plane offline.
Our services were degraded with longer than normal response times and some of our observability tools were impacted.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Post-mortem&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Our public cloud provider had an incident on June 12, 2025 at 17:45 UTC taking large portions of their control plane offline.
Our services were degraded with longer than normal response times and some of our observability tools were impacted.&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
