Network · data from 2026-11-12
AS12399 q.beyond AG
Registry name: SCAN-PLUS-AS q.beyond AG, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12399, 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.
| 213.153.66.0/24 | Invalid: origin | None | 74 11% |
| 193.24.12.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 185.247.40.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 212.75.32.0/19 | Valid | RIR databaseRIPE | 670 100% |
| 212.211.128.0/17 | Valid | RIR databaseRIPE | 670 100% |
| 2001:a78::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS12399: RIPE::AS12399:AS-SPXS. 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 (AS12399 isn't in the set, or no route object for AS12399 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 | AS12399 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS12399:AS-SPXS | RIPE | 2 | 2 | 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
- ROA: none1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 213.153.66.0/24 | ROAs covering it name AS15518, not AS12399. If AS12399 should announce it, add a ROA for AS12399. |
| Route object: none | 213.153.66.0/24 | No route object for it. Add a route object with origin AS12399 in the RIR database for the space. |
| ROA: none | 193.24.12.0/24 | No ROA covers it. Add a ROA for AS12399, maxLength 24. |
Route objects not announced
Route objects with origin AS12399 whose prefix no peer sees AS12399 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.69.179.0/24 | RIPE | No ROA |
| 195.160.251.0/24 | 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.