help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Seeing timeouts on GetReg Token and Get Devices

ANSWERED

‎03-23-2015 13:56

‎03-23-2015 13:56

I see there was an incident on 3/19 or 3/20 about a fitbit database failover.  Since that time, our calls to the fitbit API are extremely slow or timeout.  Are ther still issues related to this incedent that are present?

 

 

Best Answer
Labels:
0 Votes
1 BEST ANSWER

Accepted Solutions

‎03-23-2015 14:15

‎03-23-2015 14:15

Nope we don't currently have any issues. If we had we would not had closed the accident. 

The Fitbit API performance is currently at good working condition.

Ivan Bahdanau
Senior Software Developer at Fitbit

View best answer in original post

Best Answer
0 Votes
1 REPLY 1

‎03-23-2015 14:15

‎03-23-2015 14:15

Nope we don't currently have any issues. If we had we would not had closed the accident. 

The Fitbit API performance is currently at good working condition.

Ivan Bahdanau
Senior Software Developer at Fitbit
Best Answer
0 Votes