I've emailed Rob with a note that many of the API requests to wsprnet.org are timing out and there are large gaps in the sequence numbers of spots being returned by wsprnet.org. There is certainly congestion at wsprnet,org today.
However, I've found that upload into the wsprdaemon_spots table in the tutorial database is working well, as this is entirely independent of wsprnet.org. I know terminology can sometimes be confusing, so in case it helps, here is a reminder:
On any wsprdaemon server (wsprdaemon.org, logs1.wsprdaemon.org, logs2.wsprdaemon.org):
1. Database 'wsprnet' has a table 'spots' gathered via an API from wsprnet.org
2. Database 'tutorial' has two tables 'wsprdaemon_spots' and 'wsprdaemon_noise' from data sent directly to the wsprdaemon server from your client wsprdaemon application, and so is unaffected by any congestion at wsprnet.org