Network · data from 2026-11-12
AS57763 SELFNET-AS SelfNet Internet Ges.m.b.H.
Registry name: SELFNET-AS SelfNet Internet Ges.m.b.H., AT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57763, 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.
| 91.223.101.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2001:67c:2318::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 2001:67c:2560::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 185.63.2.0/24 | Valid | Nonecovered by 185.63.2.0/23 | 673 100% |
| 185.63.3.0/24 | Valid | Nonecovered by 185.63.2.0/23 | 673 100% |
| 37.75.136.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 45.90.24.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 91.224.66.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.0.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2001:67c:2074::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:67c:2c2c::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:5740::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:5741::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a06:3cc0::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS57763 isn't in PeeringDB, where networks name their AS-SET.
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 14 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.223.101.0/24 | No ROA covers it. Add a ROA for AS57763, maxLength 24. |
| ROA: none | 2001:67c:2318::/48 | No ROA covers it. Add a ROA for AS57763, maxLength 48. |
| ROA: none | 2001:67c:2560::/48 | No ROA covers it. Add a ROA for AS57763, maxLength 48. |
| Route object: none | 185.63.2.0/24 | No route object for it. A route object for 185.63.2.0/23 with origin AS57763 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57763 in the RIR database for the space. |
| Route object: none | 185.63.3.0/24 | No route object for it. A route object for 185.63.2.0/23 with origin AS57763 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57763 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS57763 whose prefix no peer sees AS57763 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.75.136.0/22 | RIPE | Valid |
| 37.75.140.0/24 | RIPE | Valid |
| 37.75.141.0/24 | RIPE | Valid |
| 37.75.142.0/23 | RIPE | Valid |
| 185.63.0.0/22 | RIPE | Valid |
| 185.63.2.0/23 | RIPE | Invalid: maxLength |
| 2a01:5740::/31 | RIPE | No ROA |
| 2a01:5740::/48 | RIPE | Valid |
| 2a01:5741::/48 | 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.