Jakub Kamma is a registry contact for AS210407 visible in public RIPE data. The profile summarizes what can be verified: his handle JK15461-RIPE, the role as admin and technical contact, and the absence of any confirmed employer, title, or organizational affiliation. Evidence is limited to RIPE RDAP and WHOIS records; no commercial services, products, or additional network resources are publicly tied to his name. This baseline supports monitoring future changes to the AS210407 record and any new resource registrations. No private relationship claims are asserted; the assessment is bounded by the observable registry surface.
He serves as the formal point of contact for network operators, the RIPE NCC, and anyone needing to communicate about AS210407. The role likely allows updating the registration record and receiving official inquiries, but there is no evidence of personal ownership or routing authority.
As a publicly listed registry contact, Jakub Kamma represents a human point of failure or continuity for AS210407. If his contact information becomes outdated or he becomes unreachable, incident responders and peers could face delays in addressing operational or security issues tied to that autonomous system. Monitoring his registry status helps assess the reliability of the ASN's registration.
As a publicly listed registry contact, Jakub Kamma represents a human point of failure or continuity for AS210407. If his contact information becomes outdated or he becomes unreachable, incident responders and peers could face delays in addressing operational or security issues tied to that autonomous system. Monitoring his registry status helps assess the reliability of the ASN's registration.
He serves as the formal point of contact for network operators, the RIPE NCC, and anyone needing to communicate about AS210407. The role likely allows updating the registration record and receiving official inquiries, but there is no evidence of personal ownership or routing authority.
Outdated or inaccurate contact information could prevent external parties from reaching the responsible operator of AS210407, delaying incident response, abuse handling, and peering discussions. A change in the contact record would indicate a shift in stewardship, altering the trust model for any networks that depend on AS210407.
Jakub Kamma is a registry contact for AS210407 visible in public RIPE data. The profile summarizes what can be verified: his handle JK15461-RIPE, the role as admin and technical contact, and the absence of any confirmed employer, title, or organizational affiliation. Evidence is limited to RIPE RDAP and WHOIS records; no commercial services, products, or additional network resources are publicly tied to his name. This baseline supports monitoring future changes to the AS210407 record and any new resource registrations. No private relationship claims are asserted; the assessment is bounded by the observable registry surface.
Outdated or inaccurate contact information could prevent external parties from reaching the responsible operator of AS210407, delaying incident response, abuse handling, and peering discussions. A change in the contact record would indicate a shift in stewardship, altering the trust model for any networks that depend on AS210407.
| 0.90–1.00 | A | High — direct sources |
| 0.75–0.89 | A/B | Strong |
| 0.55–0.74 | B/C | Medium |
| 0.35–0.54 | C/D | Weak–medium |
| 0.10–0.34 | D | Weak signal |
| 0.00–0.09 | D | Internal monitoring |
Several public sources
Jakub Kamma
Jakub Kamma is listed as the administrative and technical contact for Autonomous System AS210407 in the RIPE internet registry, with handle JK15461-RIPE. The public record establishes a registry liaison role without confirming employer, organizational affiliation, or routing control. This profile limits its assessment to the observable registry surface and its implications for network coordination and incident response.
Why It Matters
Outdated or inaccurate contact information could prevent external parties from reaching the responsible operator of AS210407, delaying incident response, abuse handling, and peering discussions. A change in the contact record would indicate a shift in stewardship, altering the trust model for any networks that depend on AS210407.
What Public Sources Show
Jakub Kamma appears in RIPE's public internet registry as the administrative and technical contact for autonomous system AS210407. Under handle JK15461-RIPE, he is listed as the formal point of contact for network operators and the RIPE NCC on matters related to that ASN. No employer or organizational affiliation is documented alongside the registration.
The evidence consists of three official RIPE-controlled sources. An RDAP query for AS210407 reveals the contact handle, while a RIPEstat overview confirms the autonomous system's existence in the RIPE region. A direct lookup of the handle in the RIPE Database validates the listing as publicly queryable.
As the registered contact, Jakub Kamma can receive official inquiries and likely holds the authority to update the ASN's registration details. This makes him a human node responsible for maintaining the accuracy of the record. However, there is no evidence he controls routing policy or personally owns the ASN.
If his contact information becomes outdated or inaccurate, external parties—incident responders, peers, or the RIPE NCC—could face delays in reaching the operator of AS210407. That gap might slow abuse handling, peering negotiations, or compliance actions, placing a premium on record freshness.
The profile is bounded by a single registry snapshot. Jakub Kamma's actual decision-making power, tenure, and active involvement remain unknown. No public biography, professional profile, or employer link has been found, and it is unclear whether the entry is current or maintained by a third party.
Readers should watch for any change to the AS210407 contact record, as that would shift the attribution of responsibility. The appearance of announced IP prefixes under AS210407 would increase the operational significance of the contact role. Identifying an employer or organization would also clarify the authority behind the registration.
Until new evidence emerges, the assessment treats Jakub Kamma as a registry contact whose relevance depends on the continued accuracy and activity of the AS210407 record.
Operating Surface
He serves as the formal point of contact for network operators, the RIPE NCC, and anyone needing to communicate about AS210407. The role likely allows updating the registration record and receiving official inquiries, but there is no evidence of personal ownership or routing authority.
As a publicly listed registry contact, Jakub Kamma represents a human point of failure or continuity for AS210407. If his contact information becomes outdated or he becomes unreachable, incident responders and peers could face delays in addressing operational or security issues tied to that autonomous system. Monitoring his registry status helps assess the reliability of the ASN's registration.
Watchpoints
Jakub Kamma is a registry-only contact for an ASN with no active prefixes; his operational relevance is contingent on the accuracy of the record and any future routing activity. The absence of an employer leaves the chain of authority opaque, making the listing a potential single point of contact failure if it becomes stale.
Monitor the AS210407 RIPE record for changes in admin or tech contacts; track whether IP prefixes begin to be announced by the ASN; search for any public employer or organization link to Jakub Kamma that would establish the entity behind the registration.
Employer, official job title, and decision-making authority are undocumented. Historical changes to the AS210407 record and any past contact roles are unknown. No professional biography or corroborating web profiles exist.
Sources
- Registry RDAP / WHOIS record - public-source identity and registry context for Jakub Kamma.
- RIPE registry record - RIPEstat provides a public overview page for AS210407, confirming the autonomous system exists in RIPE-associated public internet-number-resource data.
- RIPE registry record - The RIPE Database web interface provides a public lookup path for the entity handle JK15461-RIPE referenced by the RDAP record.
Domain of operation
Jakub Kamma is listed as the administrative and technical contact for Autonomous System AS210407 in the RIPE internet registry, with handle JK15461-RIPE. The public record establishes a registry liaison role without confirming employer, organizational affiliation, or routing control. This profile limits its assessment to the observable registry surface and its implications for network coordination and incident response.
- Registry RDAP / WHOIS record: public-source identity and registry context for Jakub Kamma. Evidence basis: source-9bd35424f0ad
Timeline
- Jakub Kamma public evidence observed
As a publicly listed registry contact, Jakub Kamma represents a human point of failure or continuity for AS210407. If his contact information becomes outdated or he becomes unreachable, incident responders and peers could face delays in addressing operational or security issues tied to that autonomous system. Monitoring his registry status helps assess the reliability of the ASN's registration.
At A Glance
- Name: Jakub Kamma
- Type: Individual registry-holder label
- Base: Global
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- source-backed relationship updates
Why It Matters
- Outdated or inaccurate contact information could prevent external parties from reaching the responsible operator of AS210407, delaying incident response, abuse handling, and peering discussions. A change in the contact record would indicate a shift in stewardship, altering the trust model for any networks that depend on AS210407.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- official company sources
- public registries
- operator-published records
Track verified source updates, role changes, and current public evidence.
Outdated or inaccurate contact information could prevent external parties from reaching the responsible operator of AS210407, delaying incident response, abuse handling, and peering discussions. A change in the contact record would indicate a shift in stewardship, altering the trust model for any networks that depend on AS210407.
Longer-term relevance depends on verified operating, policy, and relationship changes.
Member Briefing
Deeper Profile Context
Login is required to unlock the full profile briefing and source notes.
Only for Strategy Circle
Strategic Circle Access
Open to all readers. Unlock profile briefings after joining and logging in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance Access
For owners and management of IP-holding companies. Login required to unlock.
Join Leadership AlliancePublic View
Outdated or inaccurate contact information could prevent external parties from reaching the responsible operator of AS210407, delaying incident response, abuse handling, and peering discussions. A change in the contact record would indicate a shift in stewardship, altering the trust model for any networks that depend on AS210407.
Watchpoints
- Jakub Kamma is a registry-only contact for an ASN with no active prefixes; his operational relevance is contingent on the accuracy of the record and any future routing activity.
- The absence of an employer leaves the chain of authority opaque, making the listing a potential single point of contact failure if it becomes stale.
- Monitor the AS210407 RIPE record for changes in admin or tech contacts; track whether IP prefixes begin to be announced by the ASN; search for any public employer or organization link to Jakub Kamma that would establish the entity behind the registration.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track Jakub Kamma?
As a publicly listed registry contact, Jakub Kamma represents a human point of failure or continuity for AS210407. If his contact information becomes outdated or he becomes unreachable, incident responders and peers could face delays in addressing operational or security issues tied to that autonomous system. Monitoring his registry status helps assess the reliability of the ASN's registration.
What evidence supports the profile?
public-source identity and registry context for Jakub Kamma.
What should readers watch next?
Jakub Kamma is a registry-only contact for an ASN with no active prefixes; his operational relevance is contingent on the accuracy of the record and any future routing activity.
