Ahmad Bayat is a UK corporate officer and RIPE registry contact for a hosting and cloud infrastructure cluster spanning Iran and the UK. Companies House filings show he holds more than 75% of shares and voting rights in Karizanta LTD, while RIPE records name him as the administrative and technical contact for AS212077 and other resources. Upcoming identity verification and confirmation statement deadlines in August 2026, along with any changes to his registry handles, will signal shifts in accountability. The evidence does not verify his authority over Web Gostaran, ABRISHAM CLOUD, or KakoHost.
Bayat's public role spans registry coordination and corporate governance. In RIPE records, he is the designated contact for technical and administrative matters, implying responsibility for resource registration, routing policy, and abuse handling. At Karizanta LTD, his Companies House filings grant him formal control over the company's strategic and operational decisions, including appointment of directors, financial direction, and compliance. The company's SIC activities align with the networking resources he manages in RIPE.
Bayat matters because public records make him visible at two accountability layers. Companies House users can identify him as a formal authority point for Karizanta LTD, while network operators can see him as the contact for key routing resources. Changes to his officer or PSC filings, or to his RIPE handles, would alter the public map of responsibility for technical coordination and company authority, potentially affecting routing stability and abuse reporting.
Bayat matters because public records make him visible at two accountability layers. Companies House users can identify him as a formal authority point for Karizanta LTD, while network operators can see him as the contact for key routing resources. Changes to his officer or PSC filings, or to his RIPE handles, would alter the public map of responsibility for technical coordination and company authority, potentially affecting routing stability and abuse reporting.
Bayat's public role spans registry coordination and corporate governance. In RIPE records, he is the designated contact for technical and administrative matters, implying responsibility for resource registration, routing policy, and abuse handling. At Karizanta LTD, his Companies House filings grant him formal control over the company's strategic and operational decisions, including appointment of directors, financial direction, and compliance. The company's SIC activities align with the networking resources he manages in RIPE.
If his registry contacts change, other networks lose their known coordination path, potentially disrupting routing stability and abuse handling. If his corporate status changes—missed deadlines, officer changes, or PSC shifts—it could affect Karizanta LTD's ability to manage its internet resources and signal internal governance problems. The upcoming identity-verification deadline in August 2026 is a critical watchpoint.
Ahmad Bayat is a UK corporate officer and RIPE registry contact for a hosting and cloud infrastructure cluster spanning Iran and the UK. Companies House filings show he holds more than 75% of shares and voting rights in Karizanta LTD, while RIPE records name him as the administrative and technical contact for AS212077 and other resources. Upcoming identity verification and confirmation statement deadlines in August 2026, along with any changes to his registry handles, will signal shifts in accountability. The evidence does not verify his authority over Web Gostaran, ABRISHAM CLOUD, or KakoHost.
If his registry contacts change, other networks lose their known coordination path, potentially disrupting routing stability and abuse handling. If his corporate status changes—missed deadlines, officer changes, or PSC shifts—it could affect Karizanta LTD's ability to manage its internet resources and signal internal governance problems. The upcoming identity-verification deadline in August 2026 is a critical watchpoint.
| 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
Ahmad Bayat
Ahmad Bayat is a public accountability figure visible through UK corporate filings and RIPE registry contacts. He is the director, secretary, and person with significant control of Karizanta LTD, and serves as the administrative and technical contact for AS212077 and related resources. His dual role makes him a critical junction for network coordination and corporate governance in a hosting cluster spanning Iran and the United Kingdom.
Why It Matters
If his registry contacts change, other networks lose their known coordination path, potentially disrupting routing stability and abuse handling. If his corporate status changes—missed deadlines, officer changes, or PSC shifts—it could affect Karizanta LTD's ability to manage its internet resources and signal internal governance problems. The upcoming identity-verification deadline in August 2026 is a critical watchpoint.
What Public Sources Show
Ahmad Bayat appears as a key accountability link in a hosting and cloud infrastructure cluster spanning Iran and the UK. UK filings name him the director, secretary, and controlling person of Karizanta LTD, while RIPE records list him as the administrative and technical contact for AS212077 and other resources tied to Web Gostaran Shaina Shiraz LLC. His dual visibility gives him influence over corporate governance and network coordination.
Karizanta LTD, incorporated in August 2023, carries SIC codes for data processing, hosting, and web portals. Companies House records confer on Bayat more than 75 percent of shares and voting rights, plus the right to appoint or remove directors. This makes him the dominant decision‑maker for the company’s operations, finances, and compliance.
Next accounts are due by May 2027, with a confirmation statement and director identity verification due in August 2026.
On the registry side, Bayat is the named contact for AS212077, registered to Web Gostaran Shaina Shiraz LLC and operating as abrisham.cloud. He also administers the ABRISHAM-CLOUD IP block (85.133.200.0/24) and AS215419, which is registered to Karizanta LTD. These RIPE handles—AB43987-RIPE, AB45895-RIPE, AB45601-RIPE—make him the human point of contact for technical coordination, routing policy, and abuse handling.
Any change to these handles would disrupt the known coordination path for other operators.
The evidence rests on official sources. RIPE RDAP and WHOIS records for AS212077, AS215419, and the inetnum confirm his contact roles. The RIPE NCC member list places Web Gostaran in Shiraz, Iran. Companies House filings for company 15081941 prove his corporate control.
Supporting context from third‑party mirrors, a datacenter listing, and PeeringDB adds service and interconnection detail, but none of these sources independently verify Bayat’s authority over entities like KakoHost or his employment at Web Gostaran.
Crucially, the public record does not establish that Bayat owns or controls Web Gostaran, ABRISHAM CLOUD, or the adjacent KakoHost colocation provider. His authority is confined to Karizanta LTD and his registry‑contact accountability. The abrisham.cloud domain and its use as nameservers for kakohost.com suggest a technical relationship, but no corporate filing links these brands.
Readers should treat the registry contacts and corporate filings as separate control surfaces until stronger evidence emerges.
If Bayat’s registry contacts were altered, network operators would lose a known path for coordination, potentially affecting routing stability and abuse handling. If his corporate status changes—missed deadlines, officer resignations, or PSC shifts—it could signal disruptions in Karizanta’s ability to manage its internet resources. The upcoming identity‑verification period in August 2026 and the confirmation statement deadline will be early indicators of any governance change.
Future watchpoints include modifications to the RIPE handles, any new corporate filings that connect Karizanta to Web Gostaran or KakoHost, expansions of AS215419 or AS212077 in routing tables, and the timely submission of Karizanta’s accounts. Because Bayat’s biography, employment terms, and full career history remain unsourced, any official statement clarifying his role at Web Gostaran would significantly reshape this profile.
Operating Surface
Bayat's public role spans registry coordination and corporate governance. In RIPE records, he is the designated contact for technical and administrative matters, implying responsibility for resource registration, routing policy, and abuse handling. At Karizanta LTD, his Companies House filings grant him formal control over the company's strategic and operational decisions, including appointment of directors, financial direction, and compliance.
The company's SIC activities align with the networking resources he manages in RIPE.
Bayat matters because public records make him visible at two accountability layers. Companies House users can identify him as a formal authority point for Karizanta LTD, while network operators can see him as the contact for key routing resources.
Changes to his officer or PSC filings, or to his RIPE handles, would alter the public map of responsibility for technical coordination and company authority, potentially affecting routing stability and abuse reporting.
Watchpoints
Bayat occupies a chokepoint role: he is the sole named individual controlling Karizanta LTD and the primary technical contact for multiple ASNs. This concentration of accountability means that any legal or operational disruption affecting him could simultaneously impact corporate governance and network coordination. The upcoming UK PSC verification deadline introduces a near-term compliance risk that could force disclosure or change in control if not met.
Companies House filings for Karizanta LTD around 17 Aug and 31 Aug 2026 for confirmation statement and identity verification; failure to comply could trigger registry action. 2) Changes to the RIPE person objects AB43987-RIPE, AB45895-RIPE, AB45601-RIPE; any removal or reassignment would indicate a shift in technical responsibility. 3) New corporate filings linking Karizanta to Web Gostaran or KakoHost, which would expand the known control map.
BGP observation of AS212077 and AS215419 for prefix growth or policy changes.
We lack independent confirmation of Bayat's role at Web Gostaran beyond registry contact; employment records, biographies, or corporate websites could fill this. No financial data is public for Karizanta, so its scale and viability are unassessed. The exact relationship between Web Gostaran and Karizanta (e.g., common ownership) is not documented. KakoHost's connection remains a technical association via DNS only.
Sources
- Registry RDAP / WHOIS record - public-source identity and registry context for Ahmad Bayat.
- Registry RDAP / WHOIS record - Identifies AS212077 / abrisham.cloud registry context and links Ahmad Bayat via the AB43987-RIPE administrative and technical contact surface associated with Web Gostaran Shaina Shiraz LLC.
- RIPE registry record - Lists Web Gostaran Shaina Shiraz LLC as a RIPE NCC member with service area in Iran, supporting the affiliated organisation context around the Bayat-linked registry records.
- Registry RDAP / WHOIS record - Mirrors RIPE WHOIS data showing AS212077 as abrisham / abrisham.cloud, organisation Web Gostaran Shaina Shiraz LLC, and admin-c/tech-c AB43987-RIPE with role Ahmad Bayat.
- Registry RDAP / WHOIS record - Shows a RIPE inetnum record for 85.133.200.0/24 / ABRISHAM-CLOUD with admin and technical contact AB45895-RIPE, person Ahmad Bayat, and route origin AS212077.
- datacentermap.com - Lists Kako Host Communications Inc as operator of KakoHost Shiraz and describes colocation, cloud, connectivity, bare-metal and public-cloud service categories, supporting the hosting-service environment around the Kakohost/Abrisham records.
- Registry RDAP / WHOIS record - Shows kakohost.com domain registration data and nameservers under abrisham.cloud, supporting the public naming link between KakoHost and Abrisham infrastructure.
- ipinfo.io - Shows the 85.133.200.0/24 ABRISHAM-CLOUD inetnum record with admin/tech contact AB45895-RIPE, person Ahmad Bayat, and route origin AS212077.
- find-and-update.company-information.service.gov.uk - Lists Karizanta LTD as an active private limited company incorporated on 18 August 2023 with SIC activities covering data processing, hosting, web portals, and other information services.
- find-and-update.company-information.service.gov.uk - Lists Ahmad Bayat as active director and active secretary of Karizanta LTD, appointed on 18 August 2023.
- find-and-update.company-information.service.gov.uk - Lists Ahmad Bayat as the active person with significant control over Karizanta LTD, with 75 percent or more of shares and voting rights and the right to appoint or remove directors.
- whois.ipip.net - Readable RIPE WHOIS mirror for AS215419 showing Karizanta LTD, sponsoring-org ORG-WGSS2-RIPE, admin/tech contact AB45601-RIPE, person Ahmad Bayat, and abrishamcloud-linked maintainer context.
Domain of operation
Ahmad Bayat is a public accountability figure visible through UK corporate filings and RIPE registry contacts. He is the director, secretary, and person with significant control of Karizanta LTD, and serves as the administrative and technical contact for AS212077 and related resources. His dual role makes him a critical junction for network coordination and corporate governance in a hosting cluster spanning Iran and the United Kingdom.
- Registry RDAP / WHOIS record: public-source identity and registry context for Ahmad Bayat. Evidence basis: source-6bce7f94af77
Timeline
- Ahmad Bayat public evidence observed
Bayat matters because public records make him visible at two accountability layers. Companies House users can identify him as a formal authority point for Karizanta LTD, while network operators can see him as the contact for key routing resources. Changes to his officer or PSC filings, or to his RIPE handles, would alter the public map of responsibility for technical coordination and company authority, potentially affecting routing stability and abuse reporting.
At A Glance
- Name: Ahmad Bayat
- 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
- If his registry contacts change, other networks lose their known coordination path, potentially disrupting routing stability and abuse handling. If his corporate status changes—missed deadlines, officer changes, or PSC shifts—it could affect Karizanta LTD's ability to manage its internet resources and signal internal governance problems. The upcoming identity-verification deadline in August 2026 is a critical watchpoint.
- 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.
If his registry contacts change, other networks lose their known coordination path, potentially disrupting routing stability and abuse handling. If his corporate status changes—missed deadlines, officer changes, or PSC shifts—it could affect Karizanta LTD's ability to manage its internet resources and signal internal governance problems. The upcoming identity-verification deadline in August 2026 is a critical watchpoint.
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
If his registry contacts change, other networks lose their known coordination path, potentially disrupting routing stability and abuse handling. If his corporate status changes—missed deadlines, officer changes, or PSC shifts—it could affect Karizanta LTD's ability to manage its internet resources and signal internal governance problems. The upcoming identity-verification deadline in August 2026 is a critical watchpoint.
Watchpoints
- Bayat occupies a chokepoint role: he is the sole named individual controlling Karizanta LTD and the primary technical contact for multiple ASNs.
- This concentration of accountability means that any legal or operational disruption affecting him could simultaneously impact corporate governance and network coordination.
- The upcoming UK PSC verification deadline introduces a near-term compliance risk that could force disclosure or change in control if not met.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track Ahmad Bayat?
Bayat matters because public records make him visible at two accountability layers. Companies House users can identify him as a formal authority point for Karizanta LTD, while network operators can see him as the contact for key routing resources. Changes to his officer or PSC filings, or to his RIPE handles, would alter the public map of responsibility for technical coordination and company authority, potentially affecting routing stability and abuse reporting.
What evidence supports the profile?
public-source identity and registry context for Ahmad Bayat.
What should readers watch next?
Bayat occupies a chokepoint role: he is the sole named individual controlling Karizanta LTD and the primary technical contact for multiple ASNs.




