Network · data from 2026-11-12
AS35205 RFTkabel Brandenburg GmbH
Registry name: RFT-Brandenburg RFT Kabel Brandenburg GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35205, 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.
| 77.78.180.0/24 | Invalid: maxLength | Nonecovered by 77.78.176.0/20 | 27 4%low visibility |
| 212.37.162.0/23 | Invalid: maxLength | Nonecovered by 212.37.160.0/20 | 27 4%low visibility |
| 77.78.188.0/22 | Valid | Nonecovered by 77.78.176.0/20 | 673 100% |
| 80.84.208.0/21 | Valid | Nonecovered by 80.84.208.0/20 | 673 100% |
| 77.78.181.0/24 | Valid | Nonecovered by 77.78.176.0/20 | 672 100% |
| 2a04:a080::/30 | Valid | Nonecovered by 2a04:a080::/29 | 471 74% |
| 2a04:a084::/30 | Valid | Nonecovered by 2a04:a080::/29 | 471 74% |
| 46.28.80.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 77.78.160.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 77.78.160.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 77.78.176.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 77.78.184.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 80.84.192.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 80.84.192.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 80.84.192.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 80.84.208.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 185.27.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.48.208.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 212.37.160.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 212.37.160.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 212.37.176.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 2a03:ed00::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a04:a080::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:3700::/29 | Valid | RIR databaseRIPE | 472 74% |
| 194.126.129.0/24 | Valid | RIR databaseRIPE | 386 57% |
AS-SET
PeeringDB's irr_as_set for AS35205: AS-RFT. 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 (AS35205 isn't in the set, or no route object for AS35205 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 | AS35205 in it | Not covered |
|---|---|---|---|---|---|
| AS-RFT | RIPE | 1 | 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 12 are in fix.csv.
- ROA: maxLength2
- Route object: none7
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 77.78.180.0/24 | ROA 77.78.160.0/19 AS35205 has maxLength 19; ROA 77.78.176.0/20 AS35205 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 77.78.180.0/24. |
| Route object: none | 77.78.180.0/24 | No route object for it. A route object for 77.78.176.0/20 with origin AS35205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35205 in the RIR database for the space. |
| ROA: maxLength | 212.37.162.0/23 | ROA 212.37.160.0/19 AS35205 has maxLength 19; ROA 212.37.160.0/20 AS35205 has maxLength 20; the route is a /23. Raise the maxLength, or add a ROA for 212.37.162.0/23. |
| Route object: none | 212.37.162.0/23 | No route object for it. A route object for 212.37.160.0/20 with origin AS35205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35205 in the RIR database for the space. |
| Route object: none | 77.78.188.0/22 | No route object for it. A route object for 77.78.176.0/20 with origin AS35205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35205 in the RIR database for the space. |
| Route object: none | 80.84.208.0/21 | No route object for it. A route object for 80.84.208.0/20 with origin AS35205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35205 in the RIR database for the space. |
| Route object: none | 77.78.181.0/24 | No route object for it. A route object for 77.78.176.0/20 with origin AS35205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35205 in the RIR database for the space. |
| Route object: none | 2a04:a080::/30 | No route object for it. A route object for 2a04:a080::/29 with origin AS35205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35205 in the RIR database for the space. |
| Route object: none | 2a04:a084::/30 | No route object for it. A route object for 2a04:a080::/29 with origin AS35205 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35205 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS35205 whose prefix no peer sees AS35205 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.78.166.0/24 | RIPE | Valid |
| 80.84.204.0/23 | RIPE | Invalid: maxLength |
| 212.37.168.0/21 | RIPE | Valid |
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.