Re: LoTW "All confirmed"


Mike Olbrisch
 

And of course as always, LoTW queue status is just one click away.

 

http://www.arrl.org/logbook-queue-status

 

Long ago, I’ve seen delays of over 2 days.  In the last few years I have seen some delays of less than 3 hours after a major contest (like Field Day).  Over the last 12 hours the delay has reached 15 minutes, but seems to be under a minute nearly every other hour, except right now, running 2+ minutes.  (Who just uploaded their whole log?)  <grin>.

 

If you’re having slow return data from LoTW, check it at the above link.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Scott Davis via Groups.Io
Sent: Wednesday, April 1, 2020 7:45 AM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] LoTW "All confirmed"

 

Hi Steve,

 

Thanks for your e-mail.  I understand that between the WPX contest last weekend and increased number of users with so many of us home, the LoTW server is experiencing heightened demand.  Please see this FAQ here:

 

 

 

Enjoy!

73, Scott

N3FJP

 

Serving the Amateur Radio community with contesting and general logging software since 1997.

 

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...

 

-----Original Message-----
From: AI3KS <AI3KS.01@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 1, 2020 9:37 am
Subject: [N3FJPSoftwareUsers] LoTW "All confirmed"

Using ACLog 6.6, LoTW Manager 1.9.

I do an "all confirmed" for LOTW several times a year. Doing that this morning it was extremely quick. Looking at the raw data, the start date was 2020-03-04. Coincidentally, that was the last time I updated the log. I tried that with all three of my callsighns and the result was the same. The only way I could get a complete history was to to a "confirmed since" and change the date to the date of the original callsign issue.

Is my config hosed or is there something else going on?

Steve, AI3KS

Join N3FJPSoftwareUsers@groups.io to automatically receive all group messages.