Each IP should include all of the routing information we know about it - ASN, netblock, how long it's been announced, how many ASes are announcing it, last seen, peer count, etc.
I put `eeqj.com` in the IP address lookup box and it gave me this:
```
{
"query": "eeqj.com",
"results": [
{
"blocklists": [],
"ip": "172.67.135.118"
},
{
"blocklists": [],
"ip": "104.21.6.237"
},
{
"blocklists": [],
"ip": "2606:4700:3035::6815:6ed"
},
{
"blocklists": [],
"ip": "2606:4700:3036::ac43:8776"
}
]
}
```
Each IP should include all of the routing information we know about it - ASN, netblock, how long it's been announced, how many ASes are announcing it, last seen, peer count, etc.
clawbot
was assigned by sneak2026-10-27 18:32:46 +01:00
Why the answer had no routing data: your instance had restarted 18 minutes earlier, and its table then held about half of the IPv4 prefixes; the feed had not yet announced those four prefixes to it. On a full table the same lookup of eeqj.com returns each address with its AS, netblock, peer count, first and last seen.
Plan, so the answer is complete and always has one shape:
Every result has the same fields, for a name and for an address.
New: the number of ASes announcing the netblock, and which they are.
An address the table has no route for yet keeps every routing field, set to null, so a client sees the same fields every time.
Model: opus-5-5
Why the answer had no routing data: your instance had restarted 18 minutes earlier, and its table then held about half of the IPv4 prefixes; the feed had not yet announced those four prefixes to it. On a full table the same lookup of `eeqj.com` returns each address with its AS, netblock, peer count, first and last seen.
Plan, so the answer is complete and always has one shape:
- Every result has the same fields, for a name and for an address.
- New: the number of ASes announcing the netblock, and which they are.
- An address the table has no route for yet keeps every routing field, set to null, so a client sees the same fields every time.
Model: opus-5-5
Built in #206. Every result of the IP lookup now has the same fields, for a name and for an address. A field without a value is null instead of left out, so an address with no route yet still shows every routing field. Two new fields, num_origins and origin_asns, say how many origin ASes announce the netblock and which. README "HTTP Endpoints" lists every field and when it is null.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/routewatch/pulls/206. Every result of the IP lookup now has the same fields, for a name and for an address. A field without a value is null instead of left out, so an address with no route yet still shows every routing field. Two new fields, `num_origins` and `origin_asns`, say how many origin ASes announce the netblock and which. README "HTTP Endpoints" lists every field and when it is null.
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.
I put
eeqj.comin the IP address lookup box and it gave me this:Each IP should include all of the routing information we know about it - ASN, netblock, how long it's been announced, how many ASes are announcing it, last seen, peer count, etc.
Why the answer had no routing data: your instance had restarted 18 minutes earlier, and its table then held about half of the IPv4 prefixes; the feed had not yet announced those four prefixes to it. On a full table the same lookup of
eeqj.comreturns each address with its AS, netblock, peer count, first and last seen.Plan, so the answer is complete and always has one shape:
Model: opus-5-5
Built in #206. Every result of the IP lookup now has the same fields, for a name and for an address. A field without a value is null instead of left out, so an address with no route yet still shows every routing field. Two new fields,
num_originsandorigin_asns, say how many origin ASes announce the netblock and which. README "HTTP Endpoints" lists every field and when it is null.Model: opus-5-5