SwimTopia Outage History

SwimTopia is up right now

Pingoru has recorded 10 incidents for SwimTopia: 9 in the last 12 months and 1 in the last 90 days.

Source: swimtopia.statuspage.io

10incidents recorded
9last 12 months
1last 90 days
22 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking SwimTopia in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202638 of 720 (1%)
May 20264114 of 744 (15%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202617 of 744 (1%)
September 202600 of 720 (0%)
October 202600 of 578 (0%)

Incidents, newest first

Notice August 7, 2026 Outdated Invoice Payment Confirmation Deliveries/Payment Issues 6h 42m

Started Aug 07, 2026, 05:47 PM UTC· resolved Aug 08, 2026, 12:30 AM UTC

  1. monitoring Aug 07, 2026, 05:47 PM UTC

    Email notifications for invoices long since paid were re-delivered to customers, some dating as far back as 2018, and in some cases with multiple deliveries per invoice. These notifications were delivered by our invoicing portal provider in error. We have notified them of this issue, and at their recommendation, we have disconnected our accounting systems from their platform. As a result, the flood of duplicate invoice paid emails should now have stopped, but previously sent open invoices now cannot be paid via the platform. We are monitoring the situation and will update as soon as we have resolution.

  2. resolved Aug 08, 2026, 12:30 AM UTC

    We have re-issued all open invoices via QuickBooks, enabling online payment again. We have also updated our domain configuration to prevent additional emails from being sent from our previous invoicing portal provider.

Read the full incident report →

Minor May 16, 2026 Error detected when synchronizing data with USA Swimming API 3d 23h USA Swimming SWIMS API

Started May 16, 2026, 01:24 PM UTC· resolved May 20, 2026, 12:26 PM UTC

  1. investigating May 16, 2026, 01:24 PM UTC

    An increased rate of errors has been detected in our USA Swimming SWIMS API data synchronization background process. These errors are likely to prevent or delay data synchronization of member data with the USA Swimming SWIMS database. We are investigating the root cause of this issue.

  2. investigating May 16, 2026, 04:52 PM UTC

    We have reached out to our contacts at USA Swimming and are awaiting their response for an update on this issue.

  3. resolved May 20, 2026, 12:26 PM UTC

    We have resolved this issue.

Read the full incident report →

Notice May 15, 2026 Registration error: "The change you wanted was rejected" 3d 8h

Started May 15, 2026, 08:30 PM UTC· resolved May 19, 2026, 04:45 AM UTC

  1. resolved May 18, 2026, 05:12 AM UTC

    An update deployed Friday May 15 around 3:30 PM Central time resulted in some registrations being reject with the error message "The change you wanted was rejected." This root cause of this issue was identified and this code change was rolled back at approximately 11:45 PM on Sunday May 18.

Read the full incident report →

Major May 2, 2026 Meet Maestro performance issues 1h 9m Meet Maestro

Started May 02, 2026, 04:35 PM UTC· resolved May 02, 2026, 05:45 PM UTC

  1. 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.

  2. identified May 02, 2026, 04:49 PM UTC

    We have identified the issue and are currently testing a fix.

  3. 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.

  4. 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.

  5. 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 1h 8m Meet Maestro

Started May 01, 2026, 04:54 PM UTC· resolved May 01, 2026, 06:03 PM UTC

  1. 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.

  2. 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.

  3. 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 4h 38m SwimTopia customer sites

Started Apr 25, 2026, 09:36 PM UTC· resolved Apr 26, 2026, 02:15 AM UTC

  1. 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.

  2. 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

  3. 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 3h 29m Email processing, Background data processing

Started Apr 25, 2026, 04:14 PM UTC· resolved Apr 25, 2026, 07:44 PM UTC

  1. 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.

  2. 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.

  3. 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.

  4. monitoring Apr 25, 2026, 05:40 PM UTC

    We have deployed a fix and will continue to monitor systems.

  5. monitoring Apr 25, 2026, 07:41 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Apr 25, 2026, 07:42 PM UTC

    Normal operations have been restored and monitoring is complete.

  7. monitoring Apr 25, 2026, 07:42 PM UTC

    We are continuing to monitor for any further issues.

  8. 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 –

Started Apr 23, 2026, 07:00 PM UTC· resolved Apr 23, 2026, 07:00 PM UTC

  1. 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 →

Critical November 18, 2025 Network provider outage (Cloudflare) 3h 15m SwimTopia customer sites, Background data processing, Meet Maestro, SwimTopia Mobile and 2 more

Started Nov 18, 2025, 11:56 AM UTC· resolved Nov 18, 2025, 03:12 PM UTC

  1. investigating Nov 18, 2025, 11:56 AM UTC

    We are investigating reports of connection failures via Cloudflare, a service we use for security and network performance. Connectivity to affected sites is sporadic.

  2. investigating Nov 18, 2025, 12:09 PM UTC

    Cloudflare has acknowledged this incident and is posting updates to this page: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 We are monitoring this situation and are working on mitigation strategies.

  3. investigating Nov 18, 2025, 12:12 PM UTC

    We are continuing to investigate this issue.

  4. investigating Nov 18, 2025, 12:38 PM UTC

    Access to services appears to be restored in some parts of the network. We continue to monitor the situation.

  5. investigating Nov 18, 2025, 01:11 PM UTC

    Access to services remains sporadic for different parts of the network. We are continually monitoring the situation.

  6. monitoring Nov 18, 2025, 01:20 PM UTC

    Cloudflare is reporting that the issue has been identified and a fix is being deployed. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 We are continually monitoring the situation.

  7. monitoring Nov 18, 2025, 01:36 PM UTC

    We are continuing to monitor for any further issues.

  8. monitoring Nov 18, 2025, 02:39 PM UTC

    Cloudflare is reporting that they have deployed a change that has restored some services. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 We can confirm access to most of our services have improved significantly. We continue to monitor this situation closely.

  9. resolved Nov 18, 2025, 03:12 PM UTC

    Cloudflare is reporting that this issue is now resolved. We can confirm that access to our services appears to be fully restored, and we consider this issue resolved.

Read the full incident report →

Critical October 20, 2025 Team sites not loading 5h 26m SwimTopia customer sites

Started Oct 20, 2025, 02:37 PM UTC· resolved Oct 20, 2025, 08:04 PM UTC

  1. investigating Oct 20, 2025, 02:37 PM UTC

    We are currently investigating issues with our customer team sites not loading. We will update when we have more information.

  2. investigating Oct 20, 2025, 02:51 PM UTC

    We have identified the root issue as an upstream issue with our service provider Salesforce (https://status.salesforce.com/incidents/20003370) related to a broader Amazon AWS outage (https://health.aws.amazon.com/health/status). We'll update again once we have more detailed information.

  3. investigating Oct 20, 2025, 03:15 PM UTC

    We are continuing to investigate this issue.

  4. investigating Oct 20, 2025, 04:19 PM UTC

    We are still waiting on more information from Heroku / AWS. We are also exploring ways to mitigate this issue on our end, still in progress. We'll update again once we have an update.

  5. investigating Oct 20, 2025, 05:44 PM UTC

    We have indications that AWS is slowly starting to recover, and some of our team sites have begun to load intermittently. We are continuing to monitor the situation.

  6. monitoring Oct 20, 2025, 05:55 PM UTC

    It looks like our sites are steadily recovering after AWS deployed their fixes. Performance might still be slower than normal for a period, but our sites appear to be generally back online now. We will continue monitoring and will update again if anything changes.

  7. resolved Oct 20, 2025, 08:04 PM UTC

    Everything seems back to normal. We will continue monitoring, but it looks like things are recovered now.

Read the full incident report →