Network · data from 2026-11-12
AS49457 OpenBusiness
Registry name: OPENBUSINESS Openbusiness S.A., CH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49457, 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.
| 94.103.96.0/20 | No ROA | RIR databaseRIPE | 670 100% |
| 193.247.76.0/24 | No ROA | RIR databaseRIPE | 669 99% |
| 193.247.87.0/24 | No ROA | RIR databaseRIPE | 669 99% |
| 2a00:a500::/32 | No ROA | RIR databaseRIPE | 635 100% |
| 193.247.88.0/24 | No ROA | RIR databaseRIPE | 197 29% |
| 94.103.96.0/24 | No ROA | RIR databaseRIPE | 5 1%low visibility |
| 94.103.97.0/24 | No ROA | RIR databaseRIPE | 5 1%low visibility |
| 94.103.98.0/24 | No ROA | RIR databaseRIPE | 5 1%low visibility |
| 94.103.99.0/24 | No ROA | RIR databaseRIPE | 5 1%low visibility |
| 94.103.100.0/24 | No ROA | RIR databaseRIPE | 5 1%low visibility |
| 94.103.101.0/24 | No ROA | RIR databaseRIPE | 5 1%low visibility |
AS-SET
PeeringDB's irr_as_set for AS49457: AS-OBS. 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 (AS49457 isn't in the set, or no route object for AS49457 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 | AS49457 in it | Not covered |
|---|---|---|---|---|---|
| AS-OBS | 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 16 are in fix.csv.
- ROA: none11
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 94.103.96.0/20 | No ROA covers it. Add a ROA for AS49457, maxLength 20. |
| ROA: none | 193.247.76.0/24 | No ROA covers it. Add a ROA for AS49457, maxLength 24. |
| ROA: none | 193.247.87.0/24 | No ROA covers it. Add a ROA for AS49457, maxLength 24. |
| ROA: none | 2a00:a500::/32 | No ROA covers it. Add a ROA for AS49457, maxLength 32. |
| ROA: none | 193.247.88.0/24 | No ROA covers it. Add a ROA for AS49457, maxLength 24. |
| ROA: none | 94.103.96.0/24 | No ROA covers it. Add a ROA for AS49457, maxLength 24. |
| ROA: none | 94.103.97.0/24 | No ROA covers it. Add a ROA for AS49457, maxLength 24. |
| ROA: none | 94.103.98.0/24 | No ROA covers it. Add a ROA for AS49457, maxLength 24. |
| ROA: none | 94.103.99.0/24 | No ROA covers it. Add a ROA for AS49457, maxLength 24. |
| ROA: none | 94.103.100.0/24 | No ROA covers it. Add a ROA for AS49457, maxLength 24. |
| ROA: none | 94.103.101.0/24 | No ROA covers it. Add a ROA for AS49457, maxLength 24. |
Route objects not announced
Route objects with origin AS49457 whose prefix no peer sees AS49457 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.103.96.128/25 | RIPE | No ROA |
| 94.103.102.0/24 | RIPE | No ROA |
| 94.103.103.0/24 | RIPE | No ROA |
| 193.246.108.0/24 | RIPE | No ROA |
| 193.246.109.0/24 | 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.