SwimTopia Outage History

SwimTopia is up right now

SwimTopia had 9 outages in the last 2 years totaling 194h 24m of downtime — averaging 0.4 incidents per month.

There were 9 SwimTopia outages since October 20, 2025 totaling 194h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://swimtopia.statuspage.io

Minor May 16, 2026

Error detected when synchronizing data with USA Swimming API

Detected by Pingoru
May 16, 2026, 01:24 PM UTC
Resolved
May 20, 2026, 12:26 PM UTC
Duration
3d 23h
Affected: USA Swimming SWIMS API
Timeline · 3 updates
  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"

Detected by Pingoru
May 15, 2026, 08:30 PM UTC
Resolved
May 19, 2026, 04:45 AM UTC
Duration
3d 8h
Timeline · 1 update
  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

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

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

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

Detected by Pingoru
Apr 23, 2026, 07:00 PM UTC
Resolved
Apr 23, 2026, 07:00 PM UTC
Duration
—
Timeline · 1 update
  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 October 20, 2025

Team sites not loading

Detected by Pingoru
Oct 20, 2025, 02:37 PM UTC
Resolved
Oct 20, 2025, 08:04 PM UTC
Duration
5h 26m
Affected: SwimTopia customer sites
Timeline · 7 updates
  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 →