Network · data from 2026-11-12
AS25465 BIOSME-AS Business Integrated Operating Systems M.E. LLC
Registry name: BIOSME-AS Business Integrated Operating Systems M.E. LLC, AE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25465, 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.78.160.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 672 100% |
| 94.207.41.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 45.83.99.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 45.83.96.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 671 100% |
| 45.83.97.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 671 100% |
AS-SET
AS25465 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 13 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.78.160.0/24 | No ROA covers it. Add a ROA for AS25465, maxLength 24. |
| Route object: RIR | 94.207.41.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25465 whose prefix no peer sees AS25465 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.178.17.0/24 | RADB | No ROA |
| 5.178.18.0/24 | RADB | No ROA |
| 5.178.19.0/24 | RADB | No ROA |
| 45.83.96.0/22 | RADB | No ROA |
| 45.83.96.0/23 | RADB, RIPE | No ROA |
| 45.83.98.0/23 | RADB | No ROA |
| 45.83.98.0/24 | RADB, RIPE | Valid |
| 89.42.169.168/29 | RADB | No ROA |
| 192.69.118.94/31 | RADB | No ROA |
| 192.69.119.82/31 | RADB | No ROA |
| 205.147.94.74/31 | RADB | 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.