Odd regression with scan submission

[acdha]

I noticed at some point earlier this year shodan scan submit started failing with an error which doesn't appear to be related:

Starting Shodan scan at 2023-05-09 13:24 - 99 scan credits left
# Scan ID: JX1xRd9RcszQqYv6
Error: You have reached the limit on the number of networks that you can monitor with alerts

Beyond the obvious question of why individual scans are triggering an error related to network monitoring, the scans are actually submitted. If I run shodan info info before, I'll see e.g. Scan credits available: 99 before and Scan credits available: 98 after the failure, and after about 20 minutes the updated scan results will show up.

I'm using 1.28.0 which was released last summer so it's not clear if this is a client issue or some odd way the backend API can fail.

[rmhowe425]

@acdha What is the size of the network that you're trying to scan when you run into this issue? I could be way off here, but I seem to remember that you can't run a single scan against a network range larger than a /16

[acdha]

That was a single IP. I get this every time I scan anything so I was wondering it shows up because my continuous monitoring quota is maxed.