ASN source download error results in 127.1.7.7 in table. Can it just keep the old data?

[QueBall]

pfBlockerNG-devel net 3.1.0_4
pfsenseCE Current Base System 2.6.0
Having same issue on 3 separate systems on different ISP networks so I'm pretty sure it's not just my ISP screwing up the ASN lookup site.

I saw a few related threads of issues with the ASN lookup source throwing intermittent errors.
The problem I am having with this, is when the next download is attempted it results in my tables being replaced with 127.1.7.7 instead of just keeping the old valid data. Now I'm making an assumption it's the remote server throwing an error. It's not 100% clear to me this is the cause of my problem but it appears about 98% certain.

Maybe there is a way I can configure things to keep the old data but I'm not really seeing anything obvious. Download failure limit is set to unlimited but it still replaces the old list with the placeholder IP address in my case.
So a product feature suggestion is that instead of replacing the previous table date with the update. In the case the server reports an error 500 or anything other than success can it just keep the old data in the table instead of replacing it?

I'm using ASN permit to only allow the IP ranges of some local internet providers through to services where the remote end has dynamic IP but I know which ISP they are using so it should always be from their pool of IP addresses. (hosting a unifi controller in this example where I'm generally ok with giving it internet access but it keeps log spam down to lock it to the valid range of IP's)

If I force a cron update it generally works. I changed the cron time to not run at the top of the hour thinking the server is getting hit by all the systems doing automated lookups near the same time of the day which reduced the times it's been happening but not completely. So something on the lookup site is overloaded but we could be handling the failure a bit better in my opionion.

[ AS398671Rogers_v4 ] Downloading update .
Downloading ASN: 398671... completed
parse error: Invalid numeric literal at line 1, column 10
. completed ..
Empty file, Adding '127.1.7.7' to avoid download failure.