Network · data from 2026-11-12
AS211154 MFBANKA-AS MF banka akcionarsko drustvo, Banja Luka
Registry name: MFBANKA-AS MF banka akcionarsko drustvo, Banja Luka, BA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS211154, 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.
| 81.93.92.96/27 | Invalid: origin | None | 0 0%low visibility |
| 45.148.123.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS211154 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 4 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 81.93.92.96/27 | ROAs covering it name AS21107, AS25144, not AS211154. If AS211154 should announce it, add a ROA for AS211154. |
| Route object: none | 81.93.92.96/27 | No route object for it. Add a route object with origin AS211154 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS211154 whose prefix no peer sees AS211154 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.148.123.0/25 | RIPE | Valid |
| 45.148.123.128/25 | RIPE | Valid |
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.