Core Entity Brief
| Entity | AIZDEVUMS-LV SIA "Aizdevums.lv" |
|---|---|
| Public role | A dormant ASN holder can become an active network operator at any moment by originating BGP prefixes. Such a shift would introduce new routing dependencies, potential traffic attraction, or misconfiguration risks in Latvia and neighbouring networks, altering the operational threat model for regional infrastructure. |
| Region | Latvia |
| Category | Digital infrastructure institution |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | Quarter (30-120d) |
| Impact | Medium |
| Confidence | 0.70 |
| Evidence coverage | 6 public source references |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 02, 2026 |
AIZDEVUMS-LV SIA "Aizdevums.lv" is a dormant ASN holder in Latvia, known only from RIPE NCC registry records; it does not operate an active network or publish routing policy.
What It Does
- Visible operating role: The company is a dormant registry resource holder for AS211838. It can modify WHOIS records and create RPKI Route Origin Authorisations but currently does not announce prefixes, peer at exchanges, or operate any visible BGP routing.
- Revenue and customer gap: No public evidence establishes a revenue model, customer base, or contract position. These aspects remain unknown until official financial or service-source records appear.
Operating Snapshot
- Identity baseline: The company is a Latvian SIA holding AS211838. Public registry records confirm its name and a Latvian address but provide no website, business details, or operational network information.
- Routing context: No IP prefixes are announced from AS211838. No RPKI Route Origin Authorisations exist, and PeeringDB has no network record, indicating the absence of public peering.
Control Surface
- Numbering records: Registry control is exercised through the RIPE NCC membership account and the maintainer object that authorises changes to AS211838. The RIPE database lists administrative and technical contact handles, but the individuals behind them are not identified.
- Evidence changes: Any new BGP announcement, ROA publication, PeeringDB entry, or registry modification would signal a shift in operational significance and require reassessment.
Watchpoints
- Record freshness: Stale or changed RIPE database records are the main source of uncertainty. Modifications to the AS211838 object should trigger a review.
- Footprint change: The appearance of an announced prefix, a PeeringDB profile, or an RPKI ROA would indicate the company is becoming an active network participant, introducing new dependencies.

