Network · data from 2026-11-12
AS208208 CYBERSE
Registry name: CYBERSE Marco Lingl trading as Cyberse GmbH & Co. KG, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208208, 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.
| 2a09:6301::/32 | Invalid: origin | None | 3 0%low visibility |
| 185.240.240.247/32 | Invalid: maxLength | Nonecovered by 185.240.240.0/24 | 1 0%low visibility |
| 185.240.240.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.240.241.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.240.242.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.240.243.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.31.199.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a09:6302::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a09:6306::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a09:6307::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS208208: RIPE::AS208208:AS-CYBERSE. 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 (AS208208 isn't in the set, or no route object for AS208208 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 | AS208208 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS208208:AS-CYBERSE | RIPE | 3 | 1 | Yes | 2 |
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 9 are in fix.csv.
- ROA: origin1
- ROA: maxLength1
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a09:6301::/32 | ROAs covering it name AS51202, not AS208208. If AS208208 should announce it, add a ROA for AS208208. |
| Route object: none | 2a09:6301::/32 | No route object for it. Add a route object with origin AS208208 in the RIR database for the space. |
| ROA: maxLength | 185.240.240.247/32 | ROA 185.240.240.0/24 AS208208 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.240.240.247/32. |
| Route object: none | 185.240.240.247/32 | No route object for it. A route object for 185.240.240.0/24 with origin AS208208 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS208208 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS208208 whose prefix no peer sees AS208208 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.90.30.0/24 | RIPE | Valid |
| 2a09:6305::/32 | RIPE | Valid |
| 2a0c:2500:571::/52 | RIPE | Invalid: origin |
| 2a0c:2500:572::/52 | RIPE | Invalid: origin |
| 2a14:7c0:1003::/48 | RIPE | Invalid: origin |
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.