TIM011 CLOUD d.o.o. is a Serbian hosting company with a minimal but conflicting internet presence. Public company records and BGP data support an operating surface limited to AS206639 and one IPv6 route. Legacy records still associate the ASN with Gregory Falla/Revosta, creating a holder-history conflict that must be monitored. The article explains what public evidence confirms, where the boundary lies, and which registry and routing changes would alter the assessment. Watchpoints include RIPE aut-num updates, IPv6 prefix announcements, and any official company disclosure.
TIM011 CLOUD d.o.o. appears in public internet infrastructure evidence as the current holder of AS206639, with a single IPv6 adjacency at the 4b42 IXP. The company is officially registered for data processing and hosting, and its public footprint consists entirely of registry and routing data—no website, product information, or direct RIPE aut-num object was found, so its operational role is inferred from public listings and BGP visibility.
The subject is tracked because it represents a small but active infrastructure entity in Serbia whose registry status is contested. Conflicting ASN catalogs list a prior Belgian holder, raising questions about the authority of the current registration. Changes in the RIPE aut-num record, new prefix announcements, or resolution of the holder conflict would directly affect how readers map Serbian connectivity, assess routing integrity, and identify dependency relationships.
The subject is tracked because it represents a small but active infrastructure entity in Serbia whose registry status is contested. Conflicting ASN catalogs list a prior Belgian holder, raising questions about the authority of the current registration. Changes in the RIPE aut-num record, new prefix announcements, or resolution of the holder conflict would directly affect how readers map Serbian connectivity, assess routing integrity, and identify dependency relationships.
TIM011 CLOUD d.o.o. appears in public internet infrastructure evidence as the current holder of AS206639, with a single IPv6 adjacency at the 4b42 IXP. The company is officially registered for data processing and hosting, and its public footprint consists entirely of registry and routing data—no website, product information, or direct RIPE aut-num object was found, so its operational role is inferred from public listings and BGP visibility.
If TIM011 CLOUD d.o.o. operates customer or internal services behind AS206639, changes in its registry data, IPv6 route visibility, or IXP peering could impact reachability and traffic attribution for entities dependent on that ASN. Although the footprint is small, unexpected withdrawals or re-associations of the ASN would signal operational risk for connectivity through the 4b42 IXP and could expose wider registry-accuracy issues in the RIPE region.
TIM011 CLOUD d.o.o. is a Serbian hosting company with a minimal but conflicting internet presence. Public company records and BGP data support an operating surface limited to AS206639 and one IPv6 route. Legacy records still associate the ASN with Gregory Falla/Revosta, creating a holder-history conflict that must be monitored. The article explains what public evidence confirms, where the boundary lies, and which registry and routing changes would alter the assessment. Watchpoints include RIPE aut-num updates, IPv6 prefix announcements, and any official company disclosure.
If TIM011 CLOUD d.o.o. operates customer or internal services behind AS206639, changes in its registry data, IPv6 route visibility, or IXP peering could impact reachability and traffic attribution for entities dependent on that ASN. Although the footprint is small, unexpected withdrawals or re-associations of the ASN would signal operational risk for connectivity through the 4b42 IXP and could expose wider registry-accuracy issues in the RIPE region.
| 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
TIM011 TIM011 CLOUD d.o.o.
TIM011 CLOUD d.o.o. 是一家最近注册的塞尔维亚托管和数据处理公司，与自治系统 AS206639 相关联，互联网存在虽小但可观察。公开公司记录确认其位于贝尔格莱德，为微型企业，从事数据处理活动；BGP 数据显示其通过 4b42 互联网交换点拥有一条 IPv6 路由。 另见: TIM011 TIM011 CLOUD d.o.o..
相互矛盾的旧注册记录仍将该 ASN 关联到先前的比利时持有者，限制了今天可归属的运营范围。监控注册变更和路由公告可为基础设施依赖性和转让历史审查提供早期信号。 另见: AKNET 互联网与信息系统有限公司.
为什么重要
如果 TIM011 CLOUD d.o.o. 在 AS206639 背后运营客户或内部服务，其注册数据、IPv6 路由可见性或 IXP 对等互联的变化可能影响依赖该 ASN 的实体的可达性和流量归属。尽管其足迹较小，但 ASN 的意外撤销或重新关联将预示通过 4b42 IXP 的连通性存在运营风险，并可能暴露 RIPE 区域更广泛的注册准确性事宜。 另见: Azarakhsh Ava-e Ahvaz Co.
公开来源显示的信息
TIM011 CLOUD d.o.o. 是一家最近成立的塞尔维亚托管提供商，其整个可观察的互联网足迹——一个自治系统号 AS206639 和一条 IPv6 路由——表明其进行着规模虽小但活跃的基础设施运营。 另见: Windhoos.
公开公司申报文件显示该公司位于贝尔格莱德，于 2024 年 7 月注册，从事数据处理和托管业务，但有关其服务、客户和运营权威的其他所有细节都必须从路由表和注册快照中推断，因为未找到任何官方网站、PeeringDB 条目或直接的 RIPE 数据库记录。 另见: EuroNet.
该公司在多个第三方 BGP 数据源中显示为 AS206639 的持有者。Hurricane Electric 的塞尔维亚国家列表显示其 IPv4 邻接为零，IPv6 邻接为一；其针对 4b42 互联网交换点的交换点表格记录了一个 IPv6 端点 2001:7f8:d0::3:272f:1，名称为 TIM011 CLOUD。IPIP 于 2026 年 5 月编制的一份塞尔维亚 ASN 列表将 65,536 个 IPv6 /64 地址块归于同一 ASN。 另见: DU jiarui.
综合这些观察结果表明该 ASN 正在运行，但并未揭示其连接到什么或谁依赖它。 另见: 弗罗茨瓦夫市政供水与污水处理公司（MPWiK）.
这些当前列表与仍将 AS206639 关联到 Gregory Falla 和比利时实体 Revosta 的旧记录存在冲突。ipinfo.io 和 whois.ipinsight.io 均显示这一历史持有者，最后修改日期为 2025 年 9 月。 另见: Vozhd.net.ua.
实时 BGP 数据与旧目录之间的冲突意味着读者不能假定我们今天看到的路由处于该塞尔维亚公司的无疑控制之下；延迟或不完整的转让可能掩盖了真实运营者。
因此，该公司的运营范围仅限于我们掌握的注册和路由证据。塞尔维亚商业信息平台 CompanyWall 提供了最具体的公司细节：一家位于贝尔格莱德萨夫斯基韦纳茨区巴尔干街 46 号的有限责任公司，税号 114493113，分类为微型企业，2024 年收入和净利润为 493,000 塞尔维亚第纳尔。邓白氏 (Dun & Bradstreet) 也将该公司列入该地区的信息类公司之中。
这些数据点确认了一个法律实体，但除了 ASN 关联之外，并未阐明其技术基础设施。
对于绘制塞尔维亚连通性地图的分析师而言，此资料提供了一个狭窄但有用的依赖标记。如果 TIM011 CLOUD d.o.o. 确实在 AS206639 背后运营服务，那么其注册数据的任何变化——纠正后的 aut-num 对象、新前缀或 RPKI 路由来源授权——都将改变流经 4b42 交换点的流量的可达性和归属格局。
由于目前仅看到该 ASN 有一个 IPv6 邻接，IPv4 路由的突然出现或现有 IPv6 公告的撤销将表明运营格局发生了变化。
关键观察点有三个：首先，出现可直接检索的 RIPE aut-num 或路由对象，命名该塞尔维亚公司的 AS206639；其次，该 ASN 所公告前缀的数量或类型发生变化；第三，建立确认运营角色的官方公司网站或 PeeringDB 条目。
这些事件中的每一个要么解决持有者冲突，要么提高公司的基础设施相关性，并且每一个都可以完全通过公开数据观察到。
在此类记录出现之前，阅读此资料时须了解该 ASN 的公开持有者历史存在分歧。缺乏可从此公司直接检索到的塞尔维亚商业注册局页面（主要政府来源）增加了一层对 CompanyWall 和邓白氏 (D&B) 的来源依赖。尽管这些商业注册信息一致且与 BGP 数据吻合，但它们并非不会过时或出错。
读者应将当前的 ASN 关联视为工作假设，如果注册记录重新与历史上的比利时持有者对齐，则应降低该公司的运营重要性。
运营范围
TIM011 CLOUD d.o.o. 在公开互联网基础设施证据中作为 AS206639 的当前持有者出现，在 4b42 IXP 处有一个 IPv6 邻接。该公司正式注册从事数据处理和托管业务，其公开足迹完全由注册和路由数据组成——未发现网站、产品信息或直接的 RIPE aut-num 对象，因此其运营角色是根据公开列表和 BGP 可见性推断的。
跟踪该主体是因为它代表塞尔维亚一个规模虽小但活跃的基础设施实体，其注册状态存在争议。相互矛盾的 ASN 目录列出了先前的比利时持有者，引发了有关当前注册权威性的疑问。RIPE aut-num 记录的变更、新前缀公告或持有者冲突的解决将直接影响读者如何绘制塞尔维亚连通性地图、评估路由完整性以及识别依赖关系。
观察点
该公司相互矛盾的 ASN 持有者数据和最小的路由足迹使其成为塞尔维亚基础设施绘图的一个低重要性但有用的标记。如果 RIPE aut-num 记录更新为反映该塞尔维亚公司，冲突将得到解决，公司信誉将增加；如果记录恢复为比利时持有者，当前路由可能代表异常或未经授权的使用。
无论哪种结果，都将为 RIPE 区域注册准确性的评估提供信息。
- 1. 出现或更新用于 AS206639 的 RIPE aut-num 对象，命名为 TIM011 CLOUD d.o.o.。2. 从该 ASN 公告新的 IPv4 或 IPv6 前缀。3. 创建官方公司网站或 PeeringDB 条目。4. 现有 IPv6 路由的删除或重新分配。5. 任何涉及 AS206639 的正式争议或转让通知。
该资料缺乏可直接检索的塞尔维亚商业注册局记录；公司身份依赖于 CompanyWall 和邓白氏 (D&B)。没有可用的 RIPE aut-num 对象、RPKI ROA、客户列表或产品信息。没有任何公司控制的披露意味着 ASN 关联仅基于第三方 BGP 数据。
来源
- 互联网注册记录 - 用于 TIM011 TIM011 CLOUD d.o.o. 的公开来源身份和注册背景。
- companywall.rs - 将 TIM011 CLOUD d.o.o. 列为位于塞尔维亚贝尔格莱德（萨夫斯基韦纳茨）巴尔干街 46 号的活跃公司，PIB 114493113，MB 22030825，注册日期 2024 年 7 月 18 日，活动 6311 数据处理/托管，微型企业规模，2024 年收入和净利润为 493,000 塞尔维亚第纳尔。
- dnb.com - 将 TIM011 CLOUD d.o.o. 列入塞尔维亚贝尔格莱德（萨夫斯基韦纳茨）的信息类公司中，支持行业和位置背景。
- bgp.he.net - 将 AS206639 列为塞尔维亚的 TIM011 CLOUD d.o.o.，IPv4 邻接/路由为 0，IPv6 邻接/路由为 1。
- bgp.he.net - 在 4b42 互联网交换点成员表中将 AS206639 TIM011 CLOUD d.o.o. 列为 IPv6 端点 2001:7f8:d0::3:272f:1。
- whois.ipip.net - 在 2026 年 5 月 17 日编制的塞尔维亚 ASN 列表中，将 AS206639 列为 TIM011 - TIM011 CLOUD d.o.o.，RS，IPv4 地址为 0，IPv6 /64 为 65,536。
- ipinfo.io - 将 AS206639 列为 Gregory Falla/Revosta，比利时，非活跃，附有 RIPE 注册和 2025 年更新元数据；这与当前的 TIM011 BGP 列表冲突，应视为来源时效性或持有者历史观察点。
- whois.ipinsight.io - 显示 AS206639 的历史 RIPE 风格详细信息，持有者为 Revosta/Gregory Falla，最后修改日期为 2025-09-02，强化了 AS206639 在来源间存在相互矛盾的公开持有者数据。
Domain of operation
TIM011 CLOUD d.o.o. is a recently registered Serbian hosting and data-processing company with a minimal but observable internet presence tied to autonomous system AS206639. Public company records confirm a Belgrade address, micro-enterprise size, and data-processing activity; BGP data shows a single IPv6 route through the 4b42 Internet Exchange Point. Conflicting legacy registry records still associate the ASN with a previous Belgian holder, limiting the operating surface that can be attributed today. Monitoring registry changes and routing announcements provides early signal for infrastructure dependency and transfer-history review.
- Internet registry record: public-source identity and registry context for TIM011 TIM011 CLOUD d.o.o.. Evidence basis: source-fde97ba0d6e3
Timeline
- TIM011 TIM011 CLOUD d.o.o. public evidence observed
The subject is tracked because it represents a small but active infrastructure entity in Serbia whose registry status is contested. Conflicting ASN catalogs list a prior Belgian holder, raising questions about the authority of the current registration. Changes in the RIPE aut-num record, new prefix announcements, or resolution of the holder conflict would directly affect how readers map Serbian connectivity, assess routing integrity, and identify dependency relationships.
At A Glance
- Name: TIM011 TIM011 CLOUD d.o.o.
- Type: Digital infrastructure institution
- Base: Europe
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- documented relationships updates
Why It Matters
- If TIM011 CLOUD d.o.o. operates customer or internal services behind AS206639, changes in its registry data, IPv6 route visibility, or IXP peering could impact reachability and traffic attribution for entities dependent on that ASN. Although the footprint is small, unexpected withdrawals or re-associations of the ASN would signal operational risk for connectivity through the 4b42 IXP and could expose wider registry-accuracy issues in the RIPE region.
- 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 TIM011 CLOUD d.o.o. operates customer or internal services behind AS206639, changes in its registry data, IPv6 route visibility, or IXP peering could impact reachability and traffic attribution for entities dependent on that ASN. Although the footprint is small, unexpected withdrawals or re-associations of the ASN would signal operational risk for connectivity through the 4b42 IXP and could expose wider registry-accuracy issues in the RIPE region.
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 TIM011 CLOUD d.o.o. operates customer or internal services behind AS206639, changes in its registry data, IPv6 route visibility, or IXP peering could impact reachability and traffic attribution for entities dependent on that ASN. Although the footprint is small, unexpected withdrawals or re-associations of the ASN would signal operational risk for connectivity through the 4b42 IXP and could expose wider registry-accuracy issues in the RIPE region.
Watchpoints
- The firm’s conflicting ASN holder data and minimal routing footprint make it a low‑materiality but useful marker for Serbian infrastructure mapping.
- If the RIPE aut‑num record is updated to reflect the Serbian company, the conflict would resolve and the company would gain credibility; if records revert to the Belgian holder, the current routing may represent an anomaly or unauthorised use.
- Either outcome would inform assessments of registry accuracy in the RIPE region.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track TIM011 TIM011 CLOUD d.o.o.?
The subject is tracked because it represents a small but active infrastructure entity in Serbia whose registry status is contested. Conflicting ASN catalogs list a prior Belgian holder, raising questions about the authority of the current registration. Changes in the RIPE aut-num record, new prefix announcements, or resolution of the holder conflict would directly affect how readers map Serbian connectivity, assess routing integrity, and identify dependency relationships.
What evidence supports the profile?
public-source identity and registry context for TIM011 TIM011 CLOUD d.o.o..
What should readers watch next?
The firm’s conflicting ASN holder data and minimal routing footprint make it a low‑materiality but useful marker for Serbian infrastructure mapping.
