The exception raised at this line occurs when there is a dataset which has both nulls and not-null values, in other words, it may occur when there is no data for a particular interval. Might be fixed by #1 when it gets done

i think we should think of a cooler name for the tool 0-)

Possibly using one of the tools from here?
https://ipdata.co/blog/asn-data-lookup-apis-and-tools/

This one looks particularly promising (lookup ASN just from api request with IP)
https://docs.ipdata.co/overview/asn-data
edit: jk that's paid :(

Maybe:

Cymru
Cymru provides an easy-to-use whois compatible API. This means we can switch the whois host to whois.cymru.com and use it to look up IP addresses.

whois -h whois.cymru.com 17.253.144.10

AS      | IP               | AS Name
714     | 17.253.144.10    | APPLE-ENGINEERING, US
The output is short and easy to read - this IP address’ ASN is AS714, which is owned by Apple. However, it’s very limited and missing a lot of useful information, so let’s look at PeeringDB and CAIDA, which can enrich the data.

https://pypi.org/project/python-whois/

requests to the /src route return the src node IP with ":portnum" on the end. Not sure if the port should be removed from the string or not,

Refactor logic in app.py to only retrieve traceroutes that differ from the most recent in the query