SwimTopia Outage History

There were 5 SwimTopia outages since April 23, 2026 totaling 10h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://swimtopia.statuspage.io

Major May 2, 2026

Meet Maestro performance issues

Detected by Pingoru: May 02, 2026, 04:35 PM UTC
Resolved: May 02, 2026, 05:45 PM UTC
Duration: 1h 9m

Affected: Meet Maestro

Timeline · 5 updates

investigating May 02, 2026, 04:35 PM UTC

We are investigating reports of issues with Meet Maestro performing slowly for various actions like transferring times, updating scores, etc. In some cases these actions are timing out.
identified May 02, 2026, 04:49 PM UTC

We have identified the issue and are currently testing a fix.
monitoring May 02, 2026, 04:59 PM UTC

We have deployed a fix and performance appears to be returning to normal levels. We are continuing to monitor for now.
monitoring May 02, 2026, 05:13 PM UTC

Performance appears to be stabilized. We are continuing to look into a few reports of data saving issues in Maestro that may not be directly related to the performance issue and related fix we just rolled out.
resolved May 02, 2026, 05:45 PM UTC

We believe the Meet Maestro Performance issues are resolved. If customers are still experiencing issues, we suggest refreshing the browser or quit/relaunch the Meet Maestro desktop to reset. It is possible the earlier errors require a restart of Meet Maestro to resolve.

Read the full incident report →

Minor May 1, 2026

Meet Maestro errors on some meets

Detected by Pingoru: May 01, 2026, 04:54 PM UTC
Resolved: May 01, 2026, 06:03 PM UTC
Duration: 1h 8m

Affected: Meet Maestro

Timeline · 3 updates

investigating May 01, 2026, 04:54 PM UTC

We are looking into errors that may be affecting some Meet Maestro meets. This is not a widespread outage, but we do see errors occurring for some meets and not others. We're currently investigating the cause.
identified May 01, 2026, 05:26 PM UTC

We have identified an issue that affects the way some meets load event data. We are currently working on a fix.
resolved May 01, 2026, 06:03 PM UTC

Confirmed that this only impacted a small number of meets. The issue is now resolved.

Read the full incident report →

Major April 25, 2026

Custom Domains: Cloudflare Invalid SSL certificate Error

Detected by Pingoru: Apr 25, 2026, 09:36 PM UTC
Resolved: Apr 26, 2026, 02:15 AM UTC
Duration: 4h 38m

Affected: SwimTopia customer sites

Timeline · 3 updates

investigating Apr 25, 2026, 09:36 PM UTC

We've received reports from multiple customers that their custom domains are now displaying a Cloudflare Invalid SSL Certificate Error message. We are investigating this issue.
identified Apr 25, 2026, 10:54 PM UTC

Customer sites encountering this Invalid SSL Certificate error are using custom domain names and appear to be set to a "Full (Strict)" encryption mode in their Cloudflare account. All customers with custom domains use a Cloudflare account to forward the traffic via their custom domain to their SwimTopia site. This Cloudflare account is controlled by the team (not SwimTopia) and we are unable to make changes to the Cloudflare configuration on our customer's behalf. ## To fix this issue: 1. Login to your team/league Cloudflare account at https://dash.cloudflare.com 2. Select your custom domain 3. Select "SSL/TLS > Overview" 4. Confirm "Current Encryption Mode" is set to "Full" and not "Full (Strict)" 5. If the current setting is "Full (Strict)" click "Configure" 6. Select "Custom SSL/TLS" then "Full" and click "Save" 7. Wait a few minutes for the change to take effect. 8. Access your custom domain to ensure it working correctly If you need additional assistance, please open a support ticket on https://help.swimtopia.com ## How did this happen? We are not 100% certain, but we believe Cloudflare's Automatic SSL/TLS[1] feature incorrectly updated the encryption mode setting for customer sites from "Full" to "Full (Strict)" even though it is supposed to automatically detect errors. We are in contact with Cloudflare to determine the root cause and to avoid future repeat incidents. [1] https://developers.cloudflare.com/ssl/origin-configuration/ssl-modes/#automatic-ssltls-default
resolved Apr 26, 2026, 02:15 AM UTC

We have implemented a fix to mitigate this issue. This issue is now resolved.

Read the full incident report →

Minor April 25, 2026

Delayed processing of background jobs

Detected by Pingoru: Apr 25, 2026, 04:14 PM UTC
Resolved: Apr 25, 2026, 07:44 PM UTC
Duration: 3h 29m

Affected: Email processingBackground data processing

Timeline · 8 updates

investigating Apr 25, 2026, 04:14 PM UTC

We are currently investigating background task performance issues that may cause degraded performance with certain actions like meet merging, file imports, email sending, etc.
investigating Apr 25, 2026, 04:52 PM UTC

Some performance has recovered and new tasks should be processing normally, but we are still investigating the root cause.
monitoring Apr 25, 2026, 05:13 PM UTC

We have identified the likely cause and are working on a long-term fix. Performance has returned to normal levels, and we are continuing to monitor for now.
monitoring Apr 25, 2026, 05:40 PM UTC

We have deployed a fix and will continue to monitor systems.
monitoring Apr 25, 2026, 07:41 PM UTC

We are continuing to monitor for any further issues.
monitoring Apr 25, 2026, 07:42 PM UTC

Normal operations have been restored and monitoring is complete.
monitoring Apr 25, 2026, 07:42 PM UTC

We are continuing to monitor for any further issues.
resolved Apr 25, 2026, 07:44 PM UTC

This incident has been resolved.

Read the full incident report →

Major April 23, 2026

Delayed Background Job Processing

Detected by Pingoru: Apr 23, 2026, 07:00 PM UTC
Resolved: Apr 23, 2026, 07:00 PM UTC
Duration: —

Timeline · 1 update

resolved Apr 24, 2026, 01:40 PM UTC

Some customers reported symptoms of severely delayed message deliveries and slow to start meet merge operations. These issues were traced back to much slower than usual processing of meet-related notifications to mobile app subscribers. Those slower jobs were delaying other background jobs in the same queue. Automated scaling increased capacity as expected, but took some time to catch up with the backlog. The root cause for this incident was traced back to a change deployed the previous day to expand the automatic favoriting of athletes to include all members of the same account on any team. That change, while well tested, proved to be non-performant in a production environment. That change has been rolled back, and work on a performant version to add the same functionality is in-progress using a different approach.

Read the full incident report →

Looking to track SwimTopia downtime and outages?

Pingoru polls SwimTopia's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when SwimTopia reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track SwimTopia alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring SwimTopia for free

5 free monitors · No credit card required