Institution Profiling / Digital infrastructure institution

TIM011 TIM011 CLOUD d.o.o.

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.

TIM011 TIM011 CLOUD d.o.o.
Caption: The sole observable internet presence of TIM011 CLOUD d.o.o.: a single IPv6 route visible through the 4b42 Internet Exchange Point. · Source context: Internet registry record; companywall.rs; dnb.com; bgp.he.net. · Relevance reason: The image visualizes the company's minimal and contested infrastructure footprint—one blinking LED in a dark room, with a shadowy figure representing the unclear holder situation. · Image provenance: Internet registry record; companywall.rs; dnb.com; bgp.he.net.

Sources

Public references used for this article.

  • Internet registry recordpublic-source identity and registry context for TIM011 TIM011 CLOUD d.o.o.. (source risk: low)
  • companywall.rsLists TIM011 CLOUD d.o.o. as an active company at Balkanska 46, Beograd (Savski Venac), Serbia, with PIB 114493113, MB 22030825, registration date 18 July 2024, activity 6311 data processing/hosting, micro-enterprise size, and 2024 revenue/net profit of RSD 493,000. (source risk: low)
  • dnb.comLists TIM011 CLOUD d.o.o. among Information companies in Beograd (Savski Venac), Serbia, supporting the sector and location context. (source risk: low)
  • bgp.he.netLists AS206639 as TIM011 CLOUD d.o.o. in Serbia with 0 IPv4 adjacencies/routes and 1 IPv6 adjacency/route. (source risk: low)
  • bgp.he.netLists AS206639 TIM011 CLOUD d.o.o. on the 4b42 Internet Exchange Point member table with IPv6 endpoint 2001:7f8:d0::3:272f:1. (source risk: low)
  • whois.ipip.netLists AS206639 as TIM011 - TIM011 CLOUD d.o.o., RS, with 0 IPv4 addresses and 65,536 IPv6 /64s on a Serbia ASN list built 2026-05-17. (source risk: low)
  • ipinfo.ioLists AS206639 as Gregory Falla/Revosta, Belgium, inactive, with RIPE registry and 2025 update metadata; this conflicts with current TIM011 BGP listings and should be treated as a source-freshness or holder-history watchpoint. (source risk: low)
  • whois.ipinsight.ioShows historical RIPE-style details for AS206639 as Revosta/Gregory Falla with last-modified 2025-09-02, reinforcing that AS206639 has conflicting public holder data across sources. (source risk: low)
CategoryInstitution

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.

RegionEurope

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.

Signal FocusDigital infrastructure institution

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.

Content TypeProfile

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.

Primary DomainInfrastructure

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.

TopicDigital infrastructure institution

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.

ImpactMedium

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.

Confidence?Confidence Grade
0.90–1.00AHigh — direct sources
0.75–0.89A/BStrong
0.55–0.74B/CMedium
0.35–0.54C/DWeak–medium
0.10–0.34DWeak signal
0.00–0.09DInternal monitoring
Good confidence (70%)

Several public sources

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 TIM011 CLOUD d.o.o.

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.

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.

What Public Sources Show

TIM011 CLOUD d.o.o. is a recently formed Serbian hosting provider whose entire observable internet footprint—one autonomous system number, AS206639, and a single IPv6 route—points to a small but active infrastructure operation.

Public company filings place the firm at a Belgrade address, registered in July 2024 for data processing and hosting, but every other detail about its services, customers, and operational authority must be inferred from routing tables and registry snapshots, because no official website, PeeringDB entry, or direct RIPE Database record has been located.

The company appears in multiple third-party BGP data sources as the holder of AS206639. Hurricane Electric's country listing for Serbia shows zero IPv4 adjacencies and one IPv6 adjacency; its exchange point table for the 4b42 Internet Exchange Point records an IPv6 endpoint, 2001:7f8:d0::3:272f:1, under the TIM011 CLOUD name. A Serbian ASN list from IPIP, built in May 2026, attributes 65,536 IPv6 /64s to the same ASN.

Together, these observations suggest that the ASN is operational, but they do not reveal what it connects to or who depends on it.

Those current listings clash with older records that still associate AS206639 with Gregory Falla and the Belgian entity Revosta. Both ipinfo.io and whois.ipinsight.io show that historic holder, with a last-modified date of September 2025.

The conflict between the live BGP data and the legacy catalogs means readers cannot assume that the routing we see today is under unquestioned control of the Serbian company; a delayed or incomplete transfer could be obscuring the real operator.

The company’s operating surface, therefore, is confined to the registry and routing evidence we have. CompanyWall, a Serbian business-information platform, provides the most concrete corporate detail: a limited-liability company at Balkanska 46 in the Savski Venac municipality of Belgrade, tax number 114493113, classified as a micro enterprise with 2024 revenue and net profit of RSD 493,000. Dun & Bradstreet also lists the firm among Information companies in that district.

These data points confirm a legal entity, but they do not illuminate its technical infrastructure beyond the ASN association.

For analysts mapping Serbian connectivity, this profile offers a narrow but useful dependency marker. If TIM011 CLOUD d.o.o. is indeed operating services behind AS206639, then any change in its registry data—a corrected aut-num object, a new prefix, or a RPKI route-origin authorization—would alter the reachability and attribution landscape for traffic flowing through the 4b42 exchange.

Because the ASN is currently seen with only an IPv6 adjacency, any sudden appearance of IPv4 routes or withdrawal of the existing IPv6 announcement would be a signal that the operational picture has shifted.

The key watchpoints are threefold: first, the appearance of a directly retrievable RIPE aut-num or route object for AS206639 that names the Serbian company; second, any change in the number or type of prefixes announced from the ASN; third, the establishment of an official company website or PeeringDB entry that confirms the operating role.

Each of these events would either resolve the holder conflict or raise the company’s infrastructure relevance, and each is observable entirely from public data.

Until such a record appears, the profile must be read with the understanding that the ASN’s public holder history is split. The absence of a directly retrieved Serbian Business Registers Agency page for this company—the primary government source—adds a layer of source dependency on CompanyWall and D&B. While those commercial registries are consistent and aligned with the BGP data, they are not impervious to staleness or error.

Readers should treat the current ASN association as the working hypothesis and downgrade the company’s operational significance if registry records realign with the historic Belgian holder.

Operating Surface

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.

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.

  1. Appearance or update of a RIPE aut‑num object for AS206639 naming TIM011 CLOUD d.o.o. 2. Announcement of new IPv4 or IPv6 prefixes from the ASN. 3. Creation of an official company website or PeeringDB entry. 4. Deletion or reassignment of the existing IPv6 route. 5. Any formal dispute or transfer notification involving AS206639.

The profile lacks a directly retrieved Serbian Business Registers Agency record; company identity relies on CompanyWall and D&B. No RIPE aut‑num object, RPKI ROA, customer list, or product information is available. The absence of any company‑controlled disclosure means the ASN association is based on third‑party BGP data alone.

Sources

  • Internet registry record - public-source identity and registry context for TIM011 TIM011 CLOUD d.o.o..
  • companywall.rs - Lists TIM011 CLOUD d.o.o. as an active company at Balkanska 46, Beograd (Savski Venac), Serbia, with PIB 114493113, MB 22030825, registration date 18 July 2024, activity 6311 data processing/hosting, micro-enterprise size, and 2024 revenue/net profit of RSD 493,000.
  • dnb.com - Lists TIM011 CLOUD d.o.o. among Information companies in Beograd (Savski Venac), Serbia, supporting the sector and location context.
  • bgp.he.net - Lists AS206639 as TIM011 CLOUD d.o.o. in Serbia with 0 IPv4 adjacencies/routes and 1 IPv6 adjacency/route.
  • bgp.he.net - Lists AS206639 TIM011 CLOUD d.o.o. on the 4b42 Internet Exchange Point member table with IPv6 endpoint 2001:7f8:d0::3:272f:1.
  • whois.ipip.net - Lists AS206639 as TIM011 - TIM011 CLOUD d.o.o., RS, with 0 IPv4 addresses and 65,536 IPv6 /64s on a Serbia ASN list built 2026-05-17.
  • ipinfo.io - Lists AS206639 as Gregory Falla/Revosta, Belgium, inactive, with RIPE registry and 2025 update metadata; this conflicts with current TIM011 BGP listings and should be treated as a source-freshness or holder-history watchpoint.
  • whois.ipinsight.io - Shows historical RIPE-style details for AS206639 as Revosta/Gregory Falla with last-modified 2025-09-02, reinforcing that AS206639 has conflicting public holder data across sources.

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

  1. 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
  • source-backed relationship 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
NowMedium priority

Track verified source updates, role changes, and current public evidence.

QuarterMedium policy sensitivity

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.

YearNext quarter outlook

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 Circle

Only for Leadership Alliance

Leadership Alliance Access

For owners and management of IP-holding companies. Login required to unlock.

Join Leadership Alliance

Public 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.

← BackAll Companies