Network · data from 2026-11-12
AS208316 elca-as Elca Informatique SA
Registry name: elca-as Elca Informatique SA, CH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208316, 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.
| 185.154.38.44/32 | Invalid: origin | None | 1 0%low visibility |
| 185.154.38.45/32 | Invalid: origin | None | 1 0%low visibility |
| 185.154.38.46/32 | Invalid: origin | None | 1 0%low visibility |
| 185.154.38.48/32 | Invalid: origin | None | 1 0%low visibility |
| 185.154.38.49/32 | Invalid: origin | None | 1 0%low visibility |
| 185.154.38.50/32 | Invalid: origin | None | 1 0%low visibility |
| 185.154.38.56/32 | Invalid: origin | None | 1 0%low visibility |
| 193.168.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.168.212.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.168.213.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.168.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.168.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS208316 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: origin7
- Route object: none7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.154.38.44/32 | ROAs covering it name AS24951, not AS208316. If AS208316 should announce it, add a ROA for AS208316. |
| Route object: none | 185.154.38.44/32 | No route object for it. Add a route object with origin AS208316 in the RIR database for the space. |
| ROA: origin | 185.154.38.45/32 | ROAs covering it name AS24951, not AS208316. If AS208316 should announce it, add a ROA for AS208316. |
| Route object: none | 185.154.38.45/32 | No route object for it. Add a route object with origin AS208316 in the RIR database for the space. |
| ROA: origin | 185.154.38.46/32 | ROAs covering it name AS24951, not AS208316. If AS208316 should announce it, add a ROA for AS208316. |
| Route object: none | 185.154.38.46/32 | No route object for it. Add a route object with origin AS208316 in the RIR database for the space. |
| ROA: origin | 185.154.38.48/32 | ROAs covering it name AS24951, not AS208316. If AS208316 should announce it, add a ROA for AS208316. |
| Route object: none | 185.154.38.48/32 | No route object for it. Add a route object with origin AS208316 in the RIR database for the space. |
| ROA: origin | 185.154.38.49/32 | ROAs covering it name AS24951, not AS208316. If AS208316 should announce it, add a ROA for AS208316. |
| Route object: none | 185.154.38.49/32 | No route object for it. Add a route object with origin AS208316 in the RIR database for the space. |
| ROA: origin | 185.154.38.50/32 | ROAs covering it name AS24951, not AS208316. If AS208316 should announce it, add a ROA for AS208316. |
| Route object: none | 185.154.38.50/32 | No route object for it. Add a route object with origin AS208316 in the RIR database for the space. |
| ROA: origin | 185.154.38.56/32 | ROAs covering it name AS24951, not AS208316. If AS208316 should announce it, add a ROA for AS208316. |
| Route object: none | 185.154.38.56/32 | No route object for it. Add a route object with origin AS208316 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS208316 is announced.
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.