<?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.jumbo.live/"/><title>Registration &amp; Payments on Jumbo Status</title><link>https://status.jumbo.live/affected/registration--payments/</link><description>Incident history</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2025-11-18T13:00:32+00:00</lastBuildDate><updated>2025-11-18T13:00:32+00:00</updated><atom:link href="https://status.jumbo.live/affected/registration--payments/index.xml" rel="self" type="application/rss+xml"/><item><title>[Resolved] Registration errors on event sites</title><link>https://status.jumbo.live/issues/2025-11-18-registration-errors/</link><pubDate>Tue, 18 Nov 2025 13:00:32 +0000</pubDate><guid>https://status.jumbo.live/issues/2025-11-18-registration-errors/</guid><category>2025-11-18 14:36:31</category><description>&lt;!-- Body copy pending final narrative from Justin. Primary outage
window per UptimeRobot export for opusadvisors.events:
13:00:32 → 14:36:31 UTC = 1h 35m 59s of sustained 500 errors.
Three shorter precursor windows occurred earlier in the day
(11:35–11:53, 12:26–12:31, 12:40–12:50) and are covered by
the "Investigating" update below. --&gt;
&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - Registration service fully recovered. Monitoring confirms normal operation.
&lt;span class="faded"&gt;(Nov 18, 2025)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - Mitigation applied. Watching for recurrence.
&lt;span class="faded"&gt;(Nov 18, 2025)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;!-- Body copy pending final narrative from Justin. Primary outage
window per UptimeRobot export for opusadvisors.events:
13:00:32 → 14:36:31 UTC = 1h 35m 59s of sustained 500 errors.
Three shorter precursor windows occurred earlier in the day
(11:35–11:53, 12:26–12:31, 12:40–12:50) and are covered by
the "Investigating" update below. --&gt;
&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - Registration service fully recovered. Monitoring confirms normal operation.
&lt;span class="faded"&gt;(Nov 18, 2025)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - Mitigation applied. Watching for recurrence.
&lt;span class="faded"&gt;(Nov 18, 2025)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - Investigating elevated 500 errors affecting registration flows on event sites. Earlier this morning there were three shorter windows of the same behavior; this most recent window is sustained. Session, streaming, and attendee-facing content are unaffected.
&lt;span class="faded"&gt;(Nov 18, 2025)&lt;/span&gt;
&lt;/p&gt;
&lt;div class="jumbo-rca" markdown="1"&gt;
&lt;h2 id="post-incident-report"&gt;Post-incident report&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Published
&lt;span class="faded"&gt;(Nov 19, 2025)&lt;/span&gt;
&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;On November 18, 2025, a subset of event sites running on our managed hosting provider’s legacy network experienced an issue in which automated cron jobs stopped executing. This disrupted registration flows on the affected sites, producing intermittent errors for attendees attempting normally functioning activities such as completing registration or payment. The longest sustained window lasted approximately 1 hour 36 minutes.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sites on the Cloudflare Advanced Network were not affected.&lt;/strong&gt; Only sites still running on the provider’s legacy network were impacted. Session playback, channels, and other attendee-facing surfaces continued to operate normally throughout.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;No data loss was detected.&lt;/strong&gt; Backup registration capture kept all submitted attendee records intact and they were reconciled into the primary registration system once service was restored.&lt;/p&gt;
&lt;/div&gt;</content></item></channel></rss>