Core Entity Brief
| Entity | RELEASE14 Release14 d.o.o. |
|---|---|
| Public role | If AS210730 is activated, it could introduce new BGP paths and dependencies, potentially affecting traffic engineering and exposing adjacent networks to prefix hijack risk. Monitoring the entity provides an early indicator of new infrastructure emergence or registry changes, making it a useful watchpoint for routing security and network topology shifts. |
| Region | RIPE NCC service region (specific jurisdiction not confirmed) |
| Category | Digital infrastructure institution |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | Quarter (30-120d) |
| Impact | Medium |
| Confidence | 0.70 |
| Evidence coverage | 3 public source references |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 03, 2026 |
RELEASE14 Release14 d.o.o. is a RIPE-registered entity holding AS210730; its commercial activity and operating model are unverified.
What It Does
- ASN registration: The entity is the registrant of AS210730 in the RIPE NCC database, with no active BGP announcements. It does not operate any known public network services.
- No verified revenue: No public evidence establishes any products, customers, or revenue streams. The entity's commercial purpose and funding remain unsubstantiated.
Operating Snapshot
- Registry presence: AS210730 is registered to RELEASE14 Release14 d.o.o. in the RIPE NCC service region.
- Routing status: RIPEstat and BGP.tools confirm that AS210730 is not currently announcing any IP prefixes in global routing tables.
Control Surface
- ASN registration: The primary control point is the AS210730 object in the RIPE database. Any modification to this record, or the initiation of prefix advertisements, would indicate operational change.
Watchpoints
- Record freshness: Registry data can become stale or reassigned. Periodic rechecking of the RIPE database is necessary to confirm current ownership details.
- Activity emergence: If AS210730 later announces prefixes, the entity would shift from dormant to active, introducing routing dependencies and potential security considerations.
- Footprint change: The appearance of a company website, PeeringDB record, or corporate filing would significantly clarify the entity's purpose, scale, and activities, reducing current uncertainties.

