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: 

Increased GatewayTimeout errors 12/18 Noon PST

ANSWERED

‎12-18-2016 17:36

‎12-18-2016 17:36

Starting at noon PST Sunday December 18th we've been seeing a higher number of gateway timeout issues consuming all endpoints, including token refreshing. Just reporting. It's 5:35pm now, still expriencing them. So far retries eventually suceed.

 

--Aaron

Using Fitbits in Research? Check out Fitabase --www.fitabase.com
Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

‎12-18-2016 19:59

‎12-18-2016 19:59

I can confirm there is an increase in response times for the Web API. We are investigating. http://status.fitbit.com/incidents/2016-12-18

View best answer in original post

Best Answer
1 REPLY 1

‎12-18-2016 19:59

‎12-18-2016 19:59

I can confirm there is an increase in response times for the Web API. We are investigating. http://status.fitbit.com/incidents/2016-12-18

Best Answer