Network · data from 2026-11-12
AS34146 ISP Solutions SA
Registry name: ISP-SOLUTIONS-AS ISP Solutions SA, CH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34146, 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.184.14.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 78.40.72.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.73.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.79.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.200.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.200.221.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.200.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.200.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.74.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 78.40.75.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 78.40.76.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a02:449::/32 | Valid | RIR databaseRIPE | 605 95% |
AS-SET
PeeringDB's irr_as_set for AS34146: AS-ISP-SOLUTIONS. 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 (AS34146 isn't in the set, or no route object for AS34146 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 | AS34146 in it | Not covered |
|---|---|---|---|---|---|
| AS-ISP-SOLUTIONS | RIPE | 4 | 1 | Yes | 1 |
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 8 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.184.14.0/24 | ROAs covering it name AS206522, not AS34146. If AS34146 should announce it, add a ROA for AS34146. |
| Route object: none | 185.184.14.0/24 | Route objects for it name AS206522. Add a route object with origin AS34146 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS34146 whose prefix no peer sees AS34146 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 78.40.72.0/21 | RIPE | No ROA |
| 78.40.77.0/24 | RIPE | No ROA |
| 78.40.78.0/24 | RIPE | No ROA |
| 217.197.208.0/20 | RIPE | No ROA |
| 217.197.222.0/24 | NTTCOM | No ROA |
| 2a02:448::/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.