Network · data from 2026-11-12
AS206215 KAERU Labs, S.L.
Registry name: AS-KAERULABS-ES KAERU Labs, S.L., ES · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206215, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 2a0e:8f02:1100::/40 | Invalid: origin | None | 3 0%low visibility |
| 167.150.22.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 167.150.220.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS206215: AS206215:AS-KAERULABS. 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 (AS206215 isn't in the set, or no route object for AS206215 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 | AS206215 in it | Not covered |
|---|---|---|---|---|---|
| AS206215:AS-KAERULABS | RIPE | 1 | 1 | Yes | 1 |
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 5 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a0e:8f02:1100::/40 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS206215 should announce it, add a ROA for AS206215. |
| Route object: none | 2a0e:8f02:1100::/40 | No route object for it. Add a route object with origin AS206215 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206215 whose prefix no peer sees AS206215 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 167.150.223.0/24 | RIPE | Valid |
| 2001:678:1118::/48 | RIPE | No ROA |
| 2001:678:111c::/48 | RIPE | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 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.