Network · data from 2026-11-12
AS200233 bfh Berner Fachhochschule
Registry name: bfh Berner Fachhochschule, CH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200233, 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.
| 2001:620:500::/48 | Invalid: origin | None | 0 0%low visibility |
| 138.124.176.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 147.87.0.0/16 | Valid | RIR databaseRIPE | 670 100% |
| 193.5.80.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 2a07:6b40::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:181::/32 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS200233 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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2001:620:500::/48 | ROAs covering it name AS559, not AS200233. If AS200233 should announce it, add a ROA for AS200233. |
| Route object: none | 2001:620:500::/48 | No route object for it. Add a route object with origin AS200233 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS200233 whose prefix no peer sees AS200233 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a13:180::/32 | 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.