Core Entity Brief
| Entity | PrintLab OÜ |
|---|---|
| Public role | PrintLab OÜ is tracked because a change in its routing status—from inactive to actively announcing prefixes—would require reassessment of routing security, abuse contacts, and dependency mapping for any services reliant on its ASN. Its registry presence creates a dormant but material network identity. |
| Region | Estonia |
| Category | Network infrastructure operator |
| Primary domain | Infrastructure |
| Signal focus | Company Type |
| Time horizon | Quarter (30-120d) |
| Impact | Medium |
| Confidence | 0.95 |
| Evidence coverage | 6 public source references |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 02, 2026 |
PrintLab OÜ is an Estonian private limited company registered for computing infrastructure and data hosting; it holds RIPE LIR membership and AS211924 with listed but unannounced prefixes, and its operational status is pre‑commercial.
What It Does
- Visible operating role: PrintLab OÜ is registered as a computing infrastructure and data hosting company, and it appears in RIPE and PeeringDB as the organisation behind AS211924, but no active network service or customer base is publicly visible.
- Unverified commercial activity: No evidence establishes a revenue model, paying customers, or service contracts; the company’s website is parked and public financial records are absent, leaving its commercial status unverified.
Operating Snapshot
- Corporate registration: PrintLab OÜ (Estonian registry code 17166621) is incorporated in Tallinn with share capital €2,500, managed solely by Dariusz Edward Nowak, and registered for data hosting under EMTAK 63101.
- Network identifier: AS211924 is allocated and appears in PeeringDB with prefix counts, but global routing tables show zero originated IPv4 or IPv6 prefixes, confirming pre‑operational status.
Control Surface
- Administrative control: Public control is exercised through the Estonian e‑Business Register (legal representation, shareholding), RIPE/RDAP organisation and maintainer objects, and the PeeringDB entry, all of which are currently maintained solely by the management board member.
- Future activation: Activation would add BGP‑announced prefixes, interconnection relationships, and operational NOC/abuse contacts, expanding the control surface to include routing policy and network security responsibilities.
Watchpoints
- BGP activation: First observed IPv4 or IPv6 prefix announcement by AS211924 in public route collectors.
- PeeringDB updates: Addition of exchange or facility entries, or changes to peering policy and contacts in the PeeringDB network record.
- Registry changes: Modifications to the RIPE organisation, maintainer, or aut‑num objects, or to the Estonian corporate registry (management, shareholding, activity).

