reconstruct command stops w/o apparent reason, won't restart

[vbar]

e.g.

2024-07-12T14:42:58.786042Z  INFO PROGRESS: [94%] CUR BLOCK L1: 20076173 L2: 485394 TOTAL BLOCKS PROCESSED L1: 280000 L2: 7035
2024-07-12T14:43:08.786954Z  INFO PROGRESS: [94%] CUR BLOCK L1: 20076173 L2: 485394 TOTAL BLOCKS PROCESSED L1: 280000 L2: 7035
2024-07-12T14:43:18.788467Z  INFO PROGRESS: [94%] CUR BLOCK L1: 20076173 L2: 485394 TOTAL BLOCKS PROCESSED L1: 280000 L2: 7035
$ target/release/state-reconstruct reconstruct l1 --http-url https://eth.llamarpc.com
2024-07-16T05:56:41.629666Z  INFO Found snapshot, starting from L1 block 20083453
2024-07-16T05:56:41.629873Z  INFO PROGRESS: [ - ] CUR BLOCK L1: 20083453 L2: 485394 TOTAL BLOCKS PROCESSED L1: 0 L2: 0
2024-07-16T05:56:46.100822Z ERROR failed parsing response of https://api.blobscan.com/blobs/0x8c5cbc55845bb91e9a67eba27e4c80e69406f5794fee1f512f53847fecee6059cc6daad04424881307fbdd474dbb3399
2024-07-16T05:56:46.100844Z ERROR Cannot parse {"message":"No blob with versioned hash or kzg commitment '0x8c5cbc55845bb91e9a67eba27e4c80e69406f5794fee1f512f53847fecee6059cc6daad04424881307fbdd474dbb3399'.","code":"NOT_FOUND"}: missing field `data` at line 1 column 180
2024-07-16T05:56:46.101060Z  INFO PROGRESS: [93%] CUR BLOCK L1: 20083453 L2: 485394 TOTAL BLOCKS PROCESSED L1: 0 L2: 0

[vbar]

So with a longer log (example attached), it becomes clear the stop isn't spontaneous, but results from a network error. Failure to find the blob remains fatal, though...
screen.zip