API Exceptionally Slow

[+ecanderson]

As of the moment this is being written, API is exceptionally slow. Just plain slow, and timeouts occur when it manages to miss the window.

 

Anything in particular happening there this afternoon? Server taking Friday afternoon happy hour break?

[+ecanderson]

As of writing now, no delays. Transient issue, I guess.

[+Hynr]

At this time (for the past half hour) I am finding the API so slow as to be unusable.

Refreshing one cache (with GSAK) takes 40 to 120 seconds to get data back. Various tries simply time out.

 

Pulling the API help using browser (Firefox) also takes a minute or longer. Ditto for clicking on any link on that page.

 

For example, just now refreshing one cache, on the dialog I see:

SocketConnect: api.Groundspeak.com:443
HostnameResolve: api.Groundspeak.com
SocketConnected: api.Groundspeak.com:443
SslHandshake: Starting
... no response after 100 seconds

Sometime between 100 and 120 seconds it does complete. Perhaps the last lines of the API log reveal something to those who understand the lingo:

...   ---- Reading HTTP Response ----
     No transfer-encoding header field.
     sslContentLength: 15085
     extraLen: 12907
     readResponseTime: Elapsed time: 102516 millisec
     responseStatus: 200
   --sendRequestGetResponse_1
   Success.
 --PostXml
--ChilkatLog

Generally the request do complete but the process is too slow to be usable at this time.

Edited March 8, 2015 by Hynr

[+blindleader]

GSAK getting no response from [download pocket queries] and [refresh cache data]. [Get recent logs] crashes GSAK. I've been trying for twenty minutes.

[+Team Freeman]

GC iPhone app working but timing out with Geosphere. GSAK also timing out.

[+Bear and Ragged]

Slow? I wish!

Non-existent for GSAK

[+Twentse Mug]

Is this again a problem only in Europe?

[+Zop]

The API isn't working at all for me. Can't update GSAK, can't create a Certitude record..

[+Bear and Ragged]

http://status.geocaching.com/

 

Not looking good...

[+ekhoc]

API is down again.

[+ecanderson]

As concerns any recent issues regarding the API and retrieving specific cache data:

 

The API was modified (a limit was tweaked to deal with perceived problems regarding one developer's software), and this broke a few things for others. As far as I can see, API developers were not notified in advance about the change. Consequently, programs like GSAK are being hastily patched to work around this issue.

 

Naughty lackeys!

[+Viajero Perdido]

I came to this thread because I was curious whether an outside app developer wasn't paying attention to info about API changes, or there simply was no such info. Thanks ecanderson, quick answer.

 

Lackeys: Please warn your partners when you make changes.

[+ecanderson]

I should clarify the earlier post -- and reword something. A limit was tweaked to deal with perceived problems regarding the server load that one developer was causing.