Core Entity Brief
| Entity | Uwe Michels |
|---|---|
| Public role | The registry listing makes Uwe Michels the designated human recipient for operational, abuse, and resource queries tied to AS210849. A stale or incorrect entry could misdirect critical communications, potentially delaying incident response and undermining trust in the contact directory for peers and law enforcement. Monitoring handle changes helps detect shifts in the contact landscape. |
| Region | Global |
| Category | Individual registry-holder label |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | QUARTER_30_120D |
| Impact | Medium |
| Confidence | 0.95 |
| Evidence coverage | 1 public source reference |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 03, 2026 |
Uwe Michels is a natural person with no identifiable corporate entity; the relevant operating surface is the registry contact role for AS210849.
What It Does
- Registry contact role: The person is listed as a contact in the RIPE NCC database for AS210849, with no inherent commercial activity. Any business affiliation would require additional evidence.
- No commercial footprint: No website, product, service, or customer references exist. The profile is limited to registry-level identification without any observable revenue model or market offering.
Operating Snapshot
- Registry assignment: The RIPE NCC records show Uwe Michels as the admin and tech contact for AS210849, which is the only operational indicator.
- No routing or network services: No BGP announcements, PeeringDB entries, or network services can be attributed to the person. There is no evidence of active network operations.
Control Surface
- RIPE NCC registry entry: The sole control surface is the autnum object for AS210849. Modifications require RIPE authentication; actual authority is unverified.
- No alternative digital surface: No personal website, social media profile, or organisation page has been identified.
Watchpoints
- Person vs. organisation confusion: Readers should not interpret this as a company profile. All organisational ties are inferred from the registry association.
- Obsolescence risk: The contact may no longer be valid. Monitor the RDAP record for updates.

