Core Entity Brief
| Entity | SIC-AS Shetland Islands Council |
|---|---|
| Public role | If AS211438 begins announcing prefixes, it would introduce a new local-government network presence into the global routing table, potentially affecting connectivity for Shetland Islands Council digital services. A registry holder change would indicate a transfer of control and could redirect future routing dependencies. |
| Region | Europe |
| Category | Digital infrastructure institution |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | Quarter (30-120d) |
| Impact | Medium |
| Confidence | 0.70 |
| Evidence coverage | 2 public source references |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 02, 2026 |
SIC-AS Shetland Islands Council is the holder of AS211438, a dormant autonomous system with no active routing.
What It Does
- Registry holding: The entity's only visible activity is holding AS211438 in the RIPE NCC registry. There is no observable business operations, customers, or revenue. The ASN is either reserved for future local-government networking or held for another purpose.
- Unconfirmed government link: The name implies an association with the Shetland Islands Council, but no council IT webpage, network policy document, or official statement confirms that this ASN is controlled by or operated for the council.
Operating Snapshot
- ASN Registration: Registered as the holder of AS211438 in the RIPE NCC database. The registration record is the sole public identifier.
- Routing Status: No IPv4 or IPv6 prefixes are announced from AS211438 according to RIPEstat. The ASN is not visible in the global BGP routing table.
- Operational Footprint: No PeeringDB entry, website, or network engineering contacts are associated with AS211438 in the public evidence. The entity has no observable network infrastructure.
Control Surface
- Registry record: The RIPE NCC registration is the sole control point. Changes to the holder name, organisation, or associated prefixes can be made through the registry portal.
- Potential future routing: If the ASN begins originating prefixes, BGP configurations would become an additional control surface, and the routing policies would determine reachability and security for any advertised address space.
Watchpoints
- Registration changes: Any modification to the registry entry (holder name, organisation, country) would indicate a change in control and should trigger a reassessment of the entity's role and dependencies.
- Prefix announcements: If AS211438 begins announcing IP prefixes, it would transition from a dormant registry entry to an operational network, introducing routing dependencies and security considerations for any services relying on those prefixes.
- Operational context missing: Without a council IT webpage, PeeringDB profile, or public network policy, the entity's operational plans and governance remain opaque. The appearance of any such evidence would improve confidence in the entity's role.

