Sometimes you just have to wait, or check your internet connection. It may be faulty. Go take a nap, if you don't think about it then it usually changes
I don't think that's the problem. It's been like this for over a week straight.
In my debug.log, here's an excerpt:
PROCESSMESSAGE SKIPPED 33 BYTES
ProcessMessage(inv, 37 bytes) : CHECKSUM ERROR nChecksum=ccd4d259 hdr.nChecksum=00000101
PROCESSMESSAGE SKIPPED 33 BYTES
ProcessMessage(inv, 37 bytes) : CHECKSUM ERROR nChecksum=ccd4d259 hdr.nChecksum=00000101
PROCESSMESSAGE SKIPPED 33 BYTES
ProcessMessage(inv, 37 bytes) : CHECKSUM ERROR nChecksum=ccd4d259 hdr.nChecksum=00000101
PROCESSMESSAGE SKIPPED 33 BYTES
ProcessMessage(addr, 27 bytes) : CHECKSUM ERROR nChecksum=a9be161b hdr.nChecksum=00000101
PROCESSMESSAGE SKIPPED 23 BYTES
ProcessMessage(addr, 27 bytes) : CHECKSUM ERROR nChecksum=6ebc0cbd hdr.nChecksum=00000101
PROCESSMESSAGE SKIPPED 23 BYTES
ProcessMessage(inv, 37 bytes) : CHECKSUM ERROR nChecksum=ccd4d259 hdr.nChecksum=00000101
PROCESSMESSAGE SKIPPED 33 BYTES
ProcessMessage(inv, 37 bytes) : CHECKSUM ERROR nChecksum=ccd4d259 hdr.nChecksum=00000101
PROCESSMESSAGE SKIPPED 33 BYTES
ProcessMessage(inv, 37 bytes) : CHECKSUM ERROR nChecksum=2633f1d0 hdr.nChecksum=00000101
PROCESSMESSAGE SKIPPED 33 BYTES
No idea why it's doing this.