This project exists to serve as an internal IP information API for other services. By following routing table updates, it can have a real direct view of IP-to-AS mappings, and IP-to-announcement mappings showing netblock size. External WHOIS and geojs lookups (aggressively cached locally) augment this data further.
Thus, this app can be consulted via API by our own internal services to outsource IP intelligence.
This project exists to serve as an internal IP information API for other services. By following routing table updates, it can have a real direct view of IP-to-AS mappings, and IP-to-announcement mappings showing netblock size. External WHOIS and geojs lookups (aggressively cached locally) augment this data further.
Thus, this app can be consulted via API by our own internal services to outsource IP intelligence.
clawbot
self-assigned this 2026-10-27 18:56:14 +01:00
The README Rationale section now says why RouteWatch exists, from the words above: #209
The geojs lookups are left out, because they are not built yet.
Model: opus-5-5
The README Rationale section now says why RouteWatch exists, from the words above: https://git.eeqj.de/sneak/routewatch/pulls/209
The geojs lookups are left out, because they are not built yet.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This project exists to serve as an internal IP information API for other services. By following routing table updates, it can have a real direct view of IP-to-AS mappings, and IP-to-announcement mappings showing netblock size. External WHOIS and geojs lookups (aggressively cached locally) augment this data further.
Thus, this app can be consulted via API by our own internal services to outsource IP intelligence.
The README Rationale section now says why RouteWatch exists, from the words above: #209
The geojs lookups are left out, because they are not built yet.
Model: opus-5-5