I have a logbook that has been working fine. I have it set in Preferences to use HamQTH to auto-fill fields. It has worked fine for several years. In last day I noted the fields were not getting populated in a new QSO. I have done various tests. Following are some findings:

1) If I switch to QRZ.COM it works. (Although it is only importing the first name. More on this in a bit)
2) I tried creating a new logbook and the problem still exists
3) I did a TCPDUMP and when the problem occurs there are 9 GET statements to HamQTH with no replies. Here is one of them:

21:49:51.535820 IP 192.168.2.6.36850 > hamqth.com.http: Flags [P.], seq 1:205, ack 1, win 502, options [nop,nop,TS val 608174916 ecr 250688205], length 204: HTTP: GET /xml.php?id=[redacted]&callsign=AJ8V&prg=CQRLOG HTTP/1.0

This same line will repeat 9 times. The first six come rapidly and then 7 - 9 come at delayed intervals. After the 9th attempt "(0)" appears in the box below "Callbook (HamQTH,com) on the UI.

4 There are also seemingly random timeouts when trying to search for a callsign on the web interface. I have not been able to discern a pattern for when it works or does not work with the web interface.

It seems like the problem may be on the server end although I cannot say that with any certainty. I would guess if others are not having similar problem it is then not the server.

In a related issue (See 1) above, using QRZ.COM does work but it only imports the First Name into the UI except in the box below "Callbook (qrz.com) it lists callsign and fullname. Is this expexted behavior. I would have thought it would fill in all the fields for which there was data, similar to what happens with Hamqth.com.

Is anyone else experiences problems with data from HamQTH.COM? Any ideas on next steps I can take to troubleshoot?

Thanks
Ricke
AJ8V