Hi Neil and Dave
I have just reviewed the cluster messaging for an entry from DL7VTX earlier this evening.
He also added a spot which reported the same issue.
The first entry is the correct entry (877) and GB3UJS and ON4KST seem to be involved, along with an IP
The second entry is incorrect (880) and seems to have GB3RDX and ON4KST involved.
Therefore, very tentatively, I would start to look a little closer at GB3RDX and its route.
CC11^10368877.0^OE1XGA/B^12-Jun-2019^2008^51s jn88eu - jo62tm^DL7VTX^24^GB7UJS^ON4KST-2^28^15^28^14^^^OE^DL^JN88^JO62^^2^48.5/-17^188.8.131.52^ (GB7DXS)
CC11^10368880.0^OE1XGA/B^12-Jun-2019^2008^51s jn88eu - jo62tm^DL7VTX^98^GB7RDX^ON4KST-2^28^15^28^14^^^OE^DL^JN88^JO62^^2^48.5/-17^^ (GB7DXS)
Nick – g4ogi
From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Neil Smith G4DBN via Groups.Io
Sent: Wednesday, June 12, 2019 9:29 PM
Subject: Re: [UKMicrowaves] beaconspot
I just checked on one cluster on the web and it is even worse, truncating to the nearest MEGAHERTZ when you search. I’ll drop the author a line as I know who writes this one!