nlnetlabs / roto-api Goto Github PK

While calling the API it returns incorrect json in a certain cases e.g.:
https://rest.bgp-api.net/api/v1/prefix/85.206.0.0/16/search returns incorrect "meta" with the double array closing symbols ']]':

{
  "type": "longest-match",
  "prefix": "85.206.0.0/16",
  "result": {
     "prefix": null,
     "type": "empty-match",
     "meta": []],
     "members": []
  }
}

The /v1 endpoint is for now the discovery starting point. That's rather sparse, though.

Hi,

It would be very helpful to me if you could ship a Dockerfile and build official images for roto-api.

From our brief chat at the RPKI community on Discord I understand that your deployment at https://roto-api.nlnetlabs.nl uses a loadbalancer in front of two instances to deal with file loading. I don't have an immediate idea what makes sense in that regard, but I suppose we can figure that out if/when this feature request gets some love.

I'm building ROV-support for Internet.nl and I'm interested to consume roto-api for both allocations and BGP data.
I use the NLnetLabs docker images for routinator as part of the development environment and would do so for roto-api too, were they become available.

Thanks for creating this project!

Related Prefixes entries should specify if there are any more specific prefixes covered by the presented one. These more-specifics could be one of:

• a routed prefix (from RisWhois)
• an allocated prefix (from del-ext dataset)

Create an interface that allows to search for all prefixes that are:

• announced by a specific ASN
• allocated to the same organisation as a specific ASN
• in a VRP with a specific validation ASN

The UI has two make two calls to /status and / to figure out status-related stuff (sources and version). Merging that would fix that and it would be similar to the routinator API.