4 ms·

I got the same error.

• surgomat 1y ago
  Yes totally unexpected! It is fixed right now. Traffic spiked and my backend rate limits kicked in too hard. Thanks so much for trying it out
  • gonzalohm 1y ago
    I'm still getting the same error
    • surgomat 1y ago
      maybe some weird cache?? sorry about that é_è... cannot see the error anymore in the logs
      • entropie 1y ago
        Still.
        • surgomat 1y ago
          We recently (a few hours ago) switched providers to handle the traffic/databse better. Everything should be back to normal now Really appreciate your patience and thanks again for giving the app a try and sorry again guys.
      • ElijahLynn 1y ago
        I'm seeing the error too as of now.
• lucasverra 1y ago
  same for me >> Error loading exercises
  • surgomat 1y ago
    Thanks for flagging it should be fixed now !