We’re currently experiencing a service disruption affecting StepSmash logins due to an issue with our authentication provider. We’re currently awaiting an update from them.
We appreciate your patience and will share updates as soon as we have more information. Thank you for bearing with us!
Update: our authentication provider has confirmed they’re impacted by an ongoing AWS issue, which is the root cause of the StepSmash login disruption. We’re continuing to monitor closely and will share more as soon as we have it. Thanks again for your patience!
https://health.aws.amazon.com/health/status
Update: our authentication provider has confirmed they’re impacted by an ongoing AWS issue, which is the root cause of the StepSmash login disruption. We’re continuing to monitor closely and will share more as soon as we have it. Thanks again for your patience!
Final Update: Service is fully restored! At 5:25 PM PDT on May 7, an incident in AWS’s us-east-1 region caused some underlying hardware in one of their datacenters to power down. Our authentication provider’s database was hosted on that hardware cluster, which meant logins were temporarily unavailable for StepSmash and many other services that rely on the same infrastructure.
The good news: if you use Fitbit or Garmin, your activity syncing kept humming along the whole time, since those integrations run through a separate authentication layer that wasn’t affected.
By 8:00 PM PDT, AWS started bringing services back online, and our authentication provider’s database was right there in the first wave of recoveries. Everything has been running smoothly since.
Thanks so much for your patience and for sticking with us. We’re grateful to have you in the StepSmash community, and we’re back to helping you crush your goals!