Core Entity Brief
| Entity | STJ |
|---|---|
| Public role | BTW monitors STJ because autonomous system registrations can signal emerging infrastructure operators, especially if routing activity begins. Currently, the lack of any announced prefixes, website, or contacts keeps the entity dormant and low-risk. Analysts track it to distinguish dormant registrations from entities that may later assert routing presence or publish organizational details, which could introduce new dependencies or risks. |
| Region | No regional attribution is confirmed in the current public registry evidence. |
| Category | Network-related institution |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | Quarter (30-120d) |
| Impact | Medium |
| Confidence | 0.95 |
| Evidence coverage | 3 public source references |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 02, 2026 |
STJ holds AS210839 in the RIPE NCC registry but has no known business, services, or active network operations.
What It Does
- Registry holding: STJ's sole observable activity is the registration of AS210839. It does not sell connectivity, host applications, or conduct commerce.
- No commercial model: There is no evidence of a customer base, revenue model, or financial operation.
Operating Snapshot
- Registry presence: STJ appears solely as the organisation name for AS210839 in RDAP and associated routing intelligence tools. No announced IP prefixes, peers, or route objects are linked to it.
- Dormant routing: AS210839 has no known BGP announcements, confirming that STJ is not actively participating in internet routing.
Control Surface
- AS registration: Whoever possesses the RIPE NCC credentials for AS210839 can update the registration; the identity of that party is not disclosed.
- Potential routing control: If STJ originates BGP routes in the future, it would gain control over reachability for any associated prefixes, creating new dependencies for peers.
Watchpoints
- Record staleness: Registry data can become outdated; if STJ's registration lapses or is reassigned, its relevance ceases.
- Operational emergence: New BGP announcements, a PeeringDB entry, or a corporate website would transform the profile from dormant to potentially active.

