Network · data from 2026-11-19
AS138037 NekomimiRouter
Registry name: DREAMRY-AS - NekomimiRouter, HK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138037, things to look at first. Visibility = full-table peers that see it, of 672 (IPv4) and 633 (IPv6) on 75 collectors. Also as routes.csv.
| 2a0b:4340:a6::/48 | Invalid: origin | RIR databaseRIPE | 211 33% |
AS-SET
PeeringDB's irr_as_set for AS138037: AS-NEKOMIMIROUTER-MEMBERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS138037 isn't in the set, or no route object for AS138037 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS138037 in it | Not covered |
|---|---|---|---|---|---|
| AS-NEKOMIMIROUTER-MEMBERS | RIPE | 10 | 1 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 1 are in fix.csv.
- ROA: origin1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a0b:4340:a6::/48 | ROAs covering it name AS205532, not AS138037. If AS138037 should announce it, add a ROA for AS138037. |
Route objects not announced
Every route object with origin AS138037 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-19 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.