The map is large. The control question is larger.

TGlobal Networks is a useful case because the public map looks bigger than the company file. The brand presents itself as a digital infrastructure provider for cloud, edge, DDoS mitigation, IP transit, Ethernet transport, bare metal and colocation. PeeringDB describes AS53427 as a global network service provider with a 500-1000 Gbps traffic band, open peering policy, presence in more than 30 data centers, and public exchange points across Brazil, the rest of Latin America, Miami, New York, London, Amsterdam and Frankfurt. BGP.Tools and Hurricane Electric show a network with hundreds of observed peers, several upstreams, dozens of downstreams or customer-like adjacencies, and a customer cone large enough to matter in regional routing. The company's own looking glass exposes locations in Fortaleza, Miami, Rio de Janeiro, Santiago and Sao Paulo.

That is not the profile of a tiny dormant AS. It is the profile of a real interconnection business. Yet the economic question is not simply whether TGlobal is visible in routing data. It is where control sits, how the legal entities relate to the route assets, whether the public footprint is built from owned capacity or partner-backed presence, and how much of the revenue is sticky recurring connectivity rather than resold capacity with thin margin. A global-sounding network has to do more than appear on a map. It has to let customers, upstreams, data-center operators, regulators and potential acquirers trace accountability from the contract to the AS, from the AS to the NOC, from the NOC to the facilities, and from the facilities to a service that keeps working during an attack.

The public evidence points to three overlapping identities. The first is TGLOBAL NETWORKS, the ARIN resource holder for AS53427, registered at 7345 W Sand Lake Road, Suite 210 Office 5042, Orlando, Florida. The second is TGLOBAL NETWORKS DO BRASIL LTDA, a Brazil company record with CNPJ 53.628.032/0001-00, an active Barueri address at Alameda Rio Negro 503, Sala 2020, capital of R$300,000, a Brazilian phone number that matches the website, and a principal activity in Servicos de Comunicacao Multimidia. The third is a Telic Technologies trail: AS61595 appears in some network sources as Telic Technologies and in more recent or other sources as TGlobal Networks do Brasil; public social and company traces show Telic and TGlobal appearing together; the cloud storefront carries Telic-hosted assets; and Antonio Donizeti Corazza Junior appears in Brazilian company and network records.

That overlap may be completely ordinary. Infrastructure companies often form a US resource holder, a Brazil operating company, and a related technical services company. They often migrate resource records after rebranding. They often sell through one brand while operations are run by another entity. The point is not to treat the overlap as suspicious. The point is that ambiguity has a cost. A customer buying DDoS mitigation during a real attack wants to know who is responsible. A Brazil enterprise buying cloud capacity wants to know which country stores data and which company invoices in reais. An ISP buying transit wants to know whose communities it is using and whose NOC will answer at 03:00. A regulator wants to know which authorised entity is providing telecom service. A lender wants to know whether the routes, contracts, ports and customer relationships can be enforced together.

TGlobal's opportunity is that the public network evidence is far stronger than the ordinary marketing site for a new infrastructure company. Its risk is that the same evidence opens more questions than a customer can settle from the website alone. The company appears to have assembled a serious regional carrier and infrastructure story quickly. The challenge is to make that story legible enough that the market prices it as controlled reach, not as an attractive wrapper around capacity that has to be rechecked one agreement at a time.

Identity begins in Orlando and lands in Barueri

The cleanest public anchor is AS53427. ARIN RDAP lists the autonomous system as TGLOBAL-NETWORKS, registered on March 13, 2023, with registrant entity TNL-167. ARIN's entity record identifies the organisation as TGLOBAL NETWORKS at the Orlando address. The same ARIN entity shows a public NOC contact at noc@tglobalnetworks.com and a US phone number. RIPEstat's AS overview describes the holder as TGLOBAL-NETWORKS - TGLOBAL NETWORKS and shows the AS as announced. BGP.Tools gives the same ARIN resource-holder story and adds registration to ARIN-TNL-167, active status, and a current public network view.

The commercial website points in a different but compatible direction. The English homepage at https://tglobalnetworks.com/en/ lists solutions in connectivity, security, cloud and edge. It gives offices in Orlando and Barueri, but the contact number is Brazilian: (11) 5253-0404. Product pages repeat the same footer. The IP Transit page says TGlobal is present in key locations across Latin America, the USA and Europe and claims direct connection to Tier 1 operators. The public cloud page says the company offers fixed-price cloud in Brazilian reais, explicitly positioning itself against dollar volatility and IOF tax. The LinkedIn page presents TGlobal as headquartered in Sao Paulo, founded in 2023, privately held, and focused on connectivity, security, cloud and edge for enterprise, telecom, hyperscale, fintech and OTT buyers.

The Brazil company record adds a firmer local frame. CNPJa lists TGLOBAL NETWORKS DO BRASIL LTDA as active from January 24, 2024, with capital of R$300,000, email financeiro@tglobalnetworks.com, phone (11) 5253-0404, and the Alameda Rio Negro address in Barueri. Its principal activity is the Brazilian SCM category, with secondary activities including equipment repair, other telecom activities, internet access providers, wired telecom services, IT consulting and related business services. The record names Antonio Donizeti Corazza Junior as socio-administrador from March 18, 2025. Other Brazil company data aggregators repeat the same broad identity, although they are secondary sources and should not replace direct official documents in a transaction.

AS61595 makes the identity question more interesting. IPinfo lists AS61595 as TGLOBAL NETWORKS DO BRASIL LTDA with Brazil as country, 45.165.80.0/22, one visible upstream and peer relationship to AS53427, and no downstreams. IPinfo also classifies the activity as a consumer ISP-like rhythm, with pingable IPs in Osasco and Fortaleza. BGP.Tools, however, shows AS61595 under Telic Technologies in its current page text, with AS53427 as the sole upstream/peer, and a whois excerpt naming TELIC TECHNOLOGIES, responsible Antonio Donizeti Corazza Junior, created in 2018. IPGeolocation's ASN page shows a more recent parsed whois response where AS61595 owner is TGLOBAL NETWORKS DO BRASIL LTDA, ownerid 53.628.032/0001-00, updated on June 23, 2026. The most plausible reading is a related technical and brand transition around Telic and TGlobal, not two unrelated networks. The public evidence does not fully settle the corporate history.

This matters because the directory subject is TGlobal Networks, not a generic AS and not Telic. The public article can name the related Telic trail only to explain why the same address space and people appear under more than one label. It should not erase the distinction. The market will ask whether TGlobal's customer contracts sit with the US resource holder, the Brazilian operating company, the older Telic entity, or a mix. The answer changes tax, data residency, telecom compliance, payment currency, collection rights, support obligations and the transferability of the business.

The company can reduce that cost with ordinary disclosure: contract forms, corporate structure, licence documents, resource assignment records, service terms, NOC escalation, facility agreements and invoicing entity. Without that disclosure, the public picture is still positive but harder to price. TGlobal looks real. It also looks like a company whose legal and operating boundary has to be reconciled early in any serious customer or investor review.

What TGlobal appears to sell

TGlobal's website is not built around retail broadband. It is built around business infrastructure. The IP Transit page is the clearest product: direct connection with Tier 1 carriers, Latin American, US and European coverage, high availability and native DDoS protection. The Ethernet transport page offers private point-to-point communication between customer sites, data centers and points of presence, including private optical and Ethernet-style transport, IX access and wavelength-style services. The DDoS page offers cloud, on-premise and hybrid mitigation, protection for a customer's downstream ASN cone, low-latency handling during attacks and a 12 Tbps mitigation-capacity claim. The public cloud and private cloud pages offer VPS, dedicated cloud environments, support, managed security, firewall, VPN and predictable pricing. NeoCloud extends the story into GPU and AI infrastructure. Bare metal and colocation turn the company into a physical infrastructure intermediary as well as a network provider.

The buyer set follows from those products. ISPs buy transit, DDoS protection, BGP communities, traffic engineering, blackhole support, IP address reachability and NOC responsiveness. Enterprises buy private transport, cloud, managed security and human support. Fintechs and SaaS companies buy low latency, data-residency assurance and predictable bills. OTT and CDN players buy interconnection and reach. Smaller operators may buy TGlobal not because it is the cheapest global carrier, but because it speaks the regional ISP language: IX.br, PIT exchange points, Brazil invoices, WhatsApp support, regional data centers, attack mitigation near the source, and a team that markets itself as more agile than a large carrier.

The public network data supports that positioning. PeeringDB's network note says TGlobal is a Latin American digital infrastructure company focused on low latency, security and scalability, with presence in more than 30 data centers across Brazil, Latin America, Europe and the United States. PeeringDB lists 22 public IX records through its API, including IX.br in Sao Paulo, Rio de Janeiro, Fortaleza, Brasilia, Curitiba and Porto Alegre; DE-CIX Sao Paulo, New York and Frankfurt; PIT points in Argentina, Peru, Colombia and Ecuador; Chile IX by PIT.net; FL-IX; LINX LON1; and AMS-IX. Its facility API lists 32 sites, including Equinix, Ascenty, Cirion, AngoNAP, PowerHost, Digital Realty, NIKHEF, Global Switch and Elea locations. TGlobal's own looking glass exposes six query locations: Fortaleza - AngoNAP, Miami - Equinix MI1, Rio de Janeiro - Equinix RJ2, Santiago - Powerhost, Sao Paulo - Ascenty SP2 and Sao Paulo - Equinix SP4.

That footprint fits a wholesale and enterprise infrastructure business. A consumer ISP's value is often measured by households and last-mile density. TGlobal's value is measured by the number of networks it can reach, the number of places where it can hand off traffic, the number of attacks it can absorb, the speed with which its NOC acts, and the ease with which customers can move traffic around the Americas without negotiating separately with every carrier and exchange.

The explicit unit economics are likely a blend of recurring connectivity, protection and managed-infrastructure revenue. An ISP or enterprise probably pays monthly recurring charges for IP transit commits, private transport capacity, port access, DDoS mitigation, cloud instances, bare-metal servers, colocation space, support and managed security. Value comes from cross-border reach, low-latency paths, attack filtering, route control, local support labour, and the ability to buy in Brazilian reais or through a regional commercial team instead of stitching together global carriers directly. Gross margin depends on upstream transit costs, IX and data-center cross-connect charges, facility and power costs, router capacity, DDoS scrubbing infrastructure, cloud hardware utilisation, IP resource cost, sales commissions and the NOC labour needed to keep customers calm during incidents. The more TGlobal owns or controls its routing and mitigation layer, the more it can defend margin. The more it resells capacity without durable control, the more revenue becomes a pass-through with support risk attached.

This is why the distinction between map and control matters. A network can list many exchanges and still have little pricing power if most capacity is leased, oversubscribed, or not backed by customer density. It can also originate little IPv4 space and still be valuable if the customer cone, route policy, DDoS tooling and support relationships are strong. TGlobal's originated IPv4 footprint is modest. Its apparent reach and downstream handling are larger. The business is therefore less about hoarding addresses and more about using interconnection to sell dependable regional reach.

Routing evidence is stronger than the website alone

AS53427 has a public record that a buyer would actually use. Hurricane Electric shows TGLOBAL NETWORKS with country of origin United States, 20 Internet exchanges, 12 originated prefixes, 255 announced prefixes, 223 observed BGP peers, 1,024 originated IPv4 addresses, no RPKI-originated invalid routes in its summary, and a looking-glass link. BGP.Tools shows four originated IPv4 routes and six originated IPv6 routes, 450 peers, six upstreams, 41 downstreams, and a cone of 180. The upstream list includes Cogent, GTT, Telecom Italia Sparkle, Angola Cables, Lumen and Durand do Brasil. IPinfo shows AS53427 with 1,024 IPv4 addresses, ARIN as registry, allocation on March 13, 2023, and a hosting/ISP/business classification. CAIDA ASRank puts AS53427 at rank 362 with a customer cone of 139 and AS degree of 77.

The exact counts differ by source because each public dataset sees the internet through different collectors, timing and thresholds. RIPEstat's announced-prefixes API returned 10 current prefixes in the checked view, including the 23.128.100.0/24, 38.246.87.0/24, 104.234.152.0/24, 45.177.138.0/24 and 2602:fa91 IPv6 space. Hurricane Electric's page showed 12 originated prefixes and 255 announced prefixes. BGP.Tools showed 4 IPv4 and 6 IPv6 originated routes. These differences do not undermine the basic point. They show why routing diligence cannot rely on one collector. TGlobal is visible from multiple independent routing views, and the broad shape is consistent: a small origin footprint, a large transit/peering footprint, and many relationships beyond its own address space.

The AS-set is especially revealing. RADb's AS-53427-TGLOBAL query lists a large set of member ASNs and was last modified in June 2026. A large AS-set is not a revenue statement, but it is operational evidence. Customers and peers use AS-sets to build filters and understand the cone a network intends to announce. If TGlobal is included in customer AS-sets and maintains its own customer set, it is acting like a provider rather than a decorative AS. The company's BGP user guide reinforces that. It describes mitigation communities, blackhole handling, informational communities for route sources, traffic-manipulation communities, BFD by request, acceptance of MED, rejection of RPKI-invalid prefixes, customer prefix-size rules, support channels and escalation. That is the language of a network selling service to other networks.

The guide also makes the control surface public. It tells customers how to mark routes for basic and premium DDoS mitigation, how to blackhole individual destinations, how TGlobal tags routes received from customers, exchanges, private interconnects, peers and upstreams, and how customers can request support. Those details matter more than marketing adjectives. If the communities work, they give customers a direct lever during congestion or attack. If the support channels answer, they turn a technical feature into a commercial promise. If RPKI-invalid routes are actually dropped, TGlobal reduces one class of routing trust risk. If the public guide is stale or the communities do not match real configuration, the value falls quickly.

There are also limits. PeeringDB is partly operator-maintained. Facility listings do not prove active capacity, paid cross-connects, equipment ownership or traffic volume at each site. Port-speed fields are not audited financial capacity. A 100G or 200G IX entry can be strategic or underused. Looking-glass locations do not prove the same redundancy customers receive. Public AS cone counts cannot distinguish high-paying strategic customers from small or transient peers. A fair valuation would require contracts, invoices, port utilisation, traffic graphs, cross-connect records, DDoS scrubbing telemetry and customer references.

Still, the routing file is too detailed to dismiss as brochure language. TGlobal's public network record supports the idea of a functioning regional carrier and infrastructure provider. The open question is how much of that functioning network is controlled by TGlobal's own assets and contracts, and how much depends on third-party facilities, leased capacity and related-company arrangements.

DDoS protection is both product and trust test

DDoS mitigation is central to TGlobal's public identity. The website repeatedly presents high-performance connectivity and DDoS protection as the company's reason to exist. The DDoS product page offers cloud, on-premise and hybrid mitigation. It says TGlobal monitors constantly, can protect the entire downstream ASN cone, prioritises low latency during attack scenarios, and has 12 Tbps of mitigation capacity. LinkedIn and Instagram posts similarly position the company around attacks against ISPs, cloud dependency and infrastructure that cannot stop.

This product has unusual economics. Transit and cloud can be sold through ordinary monthly pricing. DDoS protection is sold through fear, trust and proof. Customers pay before the attack because failure during an attack is too expensive to negotiate in real time. The provider's real cost appears during peak attack periods: scrubbing capacity, traffic diversion, routing precision, packet filtering, staff attention, emergency support and the risk that collateral filtering harms legitimate traffic. A provider can underprice protection in calm months and then discover its margin is negative when several customers are attacked at once.

TGlobal's user guide is therefore important. It shows that mitigation is not only a slogan. The guide exposes customer communities for basic and premium mitigation and for blackhole. It says premium mitigation is available only to customers who contracted that product, and warns that using the community without the product will discard traffic. That is commercially meaningful. It implies product segmentation: a basic protection tier available to all customers, a paid premium tier, and emergency blackhole control for specific addresses. It also implies the company has customer-facing route policy aligned to its revenue model.

The unanswered question is capacity provenance. A 12 Tbps claim is large. It may be built from a mix of TGlobal equipment, upstream arrangements, partner scrubbing, IX presence and route control. Public evidence does not show how much mitigation capacity is in each site, how much is usable simultaneously, how attacks are detected, how false positives are handled, which vendors or internal systems are involved, or what service credits apply. For a customer, the right question is not whether the number appears on the website. It is whether the contract, test reports, attack history and incident reviews support the promised protection.

Reputation matters here because DDoS providers live near abusive traffic. AbuseIPDB samples show mixed signals. One AS53427 sample at 38.246.87.153 was labelled TGLOBAL NETWORKS, data-center/web-hosting/transit usage, Brazil/Sao Paulo, with one historical report and 0% confidence at the time opened. Another sample at 104.234.152.2 was labelled ONTAR-40 / Velcom INC under AS53427, data-center/web-hosting/transit usage, Brazil/Sao Paulo, with many historical reports but a low 3% confidence value on the opened page. These samples do not prove misconduct by TGlobal. They show the normal exposure of a transit and hosting-adjacent network: customer traffic, resold blocks, delegated operations and attack response all become part of the reputation surface. If TGlobal can close abuse tickets quickly, the exposure is manageable. If not, customers may inherit friction from address reputation and upstream scrutiny.

For TGlobal, DDoS protection is not just another SKU. It is the proof point for the entire brand. If the network performs during attacks, the company can justify premium pricing against commodity transit. If the network does not, the broad map becomes less valuable because customers can buy cheaper ports elsewhere.

Cost base: ports, power, people and proof

The public footprint implies a high fixed-cost base. TGlobal lists or appears at major exchanges and data centers. Every serious site brings costs: cross-connects, rack or remote hands, optics, router ports, support contracts, power, transport between facilities, monitoring, sparing, vendor maintenance and staff time. Some costs may be direct; some may be bundled through partners; some may be offset by customer revenue at the same location. The public map alone cannot tell which sites are profitable.

Brazil adds a particular operating burden. IX.br is one of the world's most important internet exchange ecosystems, and presence across Sao Paulo, Rio de Janeiro, Fortaleza, Brasilia, Curitiba and Porto Alegre can be valuable for regional performance. But multi-site presence requires disciplined operations. Fortaleza has strategic value because of submarine-cable routes and northeast Brazil connectivity. Sao Paulo and Barueri are commercial and data-center hubs. Rio de Janeiro, Brasilia and Porto Alegre add reach and redundancy. Each city increases the network's selling story and its support surface.

International points create another layer. Miami is a natural Latin America gateway. New York, London, Amsterdam and Frankfurt add global interconnection and cloud/customer proximity. Santiago, Lima, Buenos Aires, Bogota and Quito support a Latin American regional story. But geography does not become margin automatically. The company must aggregate enough traffic to justify ports and transport, enough customers to spread NOC cost, and enough route control to avoid becoming an expensive reseller of upstream capacity.

The cost base is not only technical. TGlobal markets human support as a differentiator. The public cloud page promises 24/7/365 human support. The BGP guide describes support portal, support email, phone and WhatsApp channels, a 24x7 NOC, manager escalation after several hours, and CTO escalation after a longer period. That is expensive if customers use it heavily and valuable if customers pay for it. A customer under attack or outage is not buying only packets. It is buying the confidence that someone with authority will answer, understand BGP and act.

Sales labour is also visible. A LinkedIn post advertises a closer role for consultative B2B sales and negotiations with ISPs and enterprises. That is an important signal. Wholesale connectivity and cloud infrastructure do not sell like consumer apps. They require account management, procurement cycles, technical pre-sales, migration planning, legal work and trust-building. A growing commercial team can convert technical footprint into revenue. It can also increase burn before revenue catches up.

Cloud and GPU products change the economics again. Public and private cloud, bare metal and NeoCloud require hardware utilisation discipline. Routers and cross-connects can be justified by traffic commits. GPU and bare-metal infrastructure require capital, depreciation, power, cooling, support and demand forecasting. If TGlobal has the right customers, local cloud in Brazilian reais can be attractive because buyers dislike dollar exposure and global-cloud unpredictability. If utilisation is low, hardware becomes a drag. The website's cloud store surfaced at least one public price marker around R$200 in the JavaScript bundle, but the public page did not provide a clean full pricing table in the research view. The safest conclusion is that TGlobal is trying to add recurring cloud revenue to the network base, while the public evidence does not yet show utilisation or margin.

Regulation and jurisdiction are part of the product

Infrastructure buyers care about jurisdiction because contracts, data, logs and regulatory responsibility sit somewhere. TGlobal's public surface crosses the United States and Brazil. ARIN resource records put AS53427 under a US resource holder in Orlando. The commercial site lists Orlando and Barueri offices. The Brazil company record shows a Barueri limited company with SCM as principal activity. The website's cloud positioning talks about Brazilian-real pricing and data-country awareness. The LinkedIn page presents Sao Paulo as the company headquarters.

Brazil's Anatel defines Servico de Comunicacao Multimidia as a fixed telecom service of collective interest, under private regime, allowing multimedia transmission and reception including internet connection. Anatel's public page explains authorisation and notification context for entities interested in offering SCM, as well as station registration issues. The CNPJa record shows TGlobal Networks do Brasil's principal activity in SCM. That does not prove a current Anatel authorisation under TGlobal's exact name. It does make telecom compliance a central diligence topic.

For customers, the key questions are practical. Which company signs the contract? Which entity invoices? Which entity provides the SCM-regulated service in Brazil? Which entity operates the NOC? Which entity holds customer logs? Which entity responds to lawful requests? Which data center stores customer data? Which entity controls ARIN resources and which controls Brazilian resources? Which entity carries liability for DDoS mitigation mistakes? Which entity has the right to announce customer prefixes and maintain AS-set membership?

The public record gives pieces but not the whole picture. The BGP guide uses TGLOBAL NETWORKS LLC language, while the Brazil company record uses TGLOBAL NETWORKS DO BRASIL LTDA. AS53427 is the global-facing AS. AS61595 appears to be a Brazil resource path tied to the Brazil entity and the Telic transition. The customer may not care about every corporate distinction when the service works. But institutional buyers and regulators will care. In infrastructure, jurisdiction is not a legal footnote; it is part of uptime, data protection, collection rights and emergency response.

The US-Brazil structure can also be an advantage. A US resource holder may ease ARIN resource management and North American interconnection. A Brazil operating company may ease local contracts, tax, SCM activity, local support and Brazilian-real billing. The cross-border structure becomes valuable if cleanly documented. It becomes costly if customers have to discover it by reconciling registry pages, LinkedIn posts, PDFs and routing databases themselves.

Competitors and substitutes are not only carriers

TGlobal competes with several categories at once. For IP transit and international reach, it faces global carriers and regional backbone operators: Cogent, GTT, Lumen, Telecom Italia Sparkle, Angola Cables, V.tal, Cirion, Ufinet, Seaborn-type routes, Hurricane Electric and other networks that can sell capacity or peers in similar locations. For DDoS mitigation, it competes with global security providers, carrier scrubbing services, CDN security platforms and local anti-DDoS specialists. For cloud and bare metal, it competes with hyperscale clouds, Oracle, local data-center clouds, managed hosting providers, colocation resellers and customer-owned equipment in Equinix, Ascenty, Cirion or other facilities.

Its advantage is regional packaging. A large global carrier may have deeper capacity but less local customer intimacy. A hyperscale cloud may have more products but more dollar exposure, more complexity and less BGP-handholding for a regional ISP. A local ISP consultant may have trust but not the international exchange footprint. TGlobal's pitch is that it combines enough backbone, enough DDoS, enough cloud, enough Brazil billing and enough human support to remove friction for mid-market buyers that are too complex for retail hosting and too small to command global-carrier attention.

Switching costs can be real. An ISP that moves transit has to change BGP sessions, filters, communities, routing policy, monitoring, abuse contacts and possibly customer announcements. An enterprise that moves cloud has to migrate workloads, IPs, backups, security policy, contracts and support escalation. A customer using DDoS mitigation has to trust that the new provider will work during the next attack. If TGlobal's service is good, these switching costs make revenue sticky. If service is weak, the same technical dependencies make customers angry and accelerate exits.

Bundling can help. IP transit plus DDoS plus private transport plus cloud plus colocation creates more ways to keep a customer. It also increases operational complexity. A network outage can affect cloud. A DDoS false positive can affect transit. A bad invoice can affect renewal. A support failure can damage every product line at once. Bundles are valuable only when the provider can support the whole bundle under pressure.

The strongest competitor is not always another named carrier. It is direct procurement. A sophisticated ISP can buy Cogent, Hurricane Electric, Lumen, Angola Cables, local IX ports and cloud separately. A large enterprise can use AWS, Azure, Google Cloud, Oracle or a managed-security provider. TGlobal wins when the integration, support and regional route quality are worth more than the saving from direct assembly. That is a service business, not just a bandwidth resale business.

Unofficial signals point to activity, not proof of scale

Public social and reputation signals suggest an active company still building market proof. LinkedIn shows regular updates, roughly a thousand followers, hiring for B2B sales, posts about Chile data centers, cloud migration, data residency and infrastructure visits. Instagram snippets show hiring, DDoS, cloud and enterprise-infrastructure marketing. Facebook pages have very small visible like counts, which does not mean weak sales but does show limited public consumer-style traction. AbuseIPDB samples show both low-confidence and historically reported addresses under AS53427, consistent with a transit and hosting-adjacent network that must manage customer abuse. These signals suggest commercial momentum and a real operational surface; they do not prove revenue, customer satisfaction, attack success rates or scale. The evidence that would settle those points would be customer references, churn, support-ticket closure times, attack postmortems, renewal rates, traffic commits and facility invoices.

This is the right way to use unofficial market evidence. The social footprint does not need to be large if the customer base is wholesale and enterprise. B2B infrastructure sales can happen through conferences, referrals, WhatsApp, account managers and engineering trust. But the public social trail does reveal the company's current emphasis: agility against large providers, DDoS, cloud migration, data-center credibility, human support and sales hiring. The abuse samples reveal a different emphasis: when a network carries other networks and hosts customer workloads, reputation becomes a cost line. Neither signal is decisive alone. Together they help frame what TGlobal must prove.

What would change the judgement

Several facts would raise confidence materially. First, a clean corporate map: TGLOBAL NETWORKS in the United States, TGLOBAL NETWORKS DO BRASIL LTDA in Brazil, any Telic relationship, ownership, intercompany contracts, and which entity signs each product line. Second, direct telecom authorisation evidence for Brazil service, or a clear explanation of the authorised basis under which services are offered. Third, facility evidence: current contracts, cross-connects, port speeds, equipment ownership, rack locations and live traffic graphs for the listed data centers and exchanges. Fourth, customer evidence: signed ISP and enterprise contracts, customer-cone reconciliation, churn, renewal rates, unpaid accounts, ticket statistics and reference customers. Fifth, DDoS evidence: attack history, mitigation capacity by site, test reports, false-positive rates, post-incident reviews and vendor or internal-platform architecture.

Facts could also lower confidence. If the 30-plus data-center footprint is mostly inactive or marketing-led, the valuation falls. If the Brazil company and US resource holder are not linked by enforceable agreements, customer contracts become harder to price. If the AS-set contains stale customers, route-filter risk rises. If downstreams are transient low-margin networks, the apparent cone is less valuable. If DDoS mitigation depends on third-party capacity that is not contractually secured, the product is more fragile. If abuse tickets are slow to close, the network reputation discount rises. If cloud utilisation is low or hardware is underfinanced, the cloud expansion becomes a burn item rather than a margin enhancer.

The most constructive reading is that TGlobal is building a cross-border Latin American infrastructure provider around a real AS, real interconnection, real support tooling and a Brazil commercial base. It is not merely a website. The public network evidence is too broad for that. The cautious reading is that rapid expansion creates diligence debt. Every new city, exchange, product and related-company trace adds a question that must be answered in contracts and operations. TGlobal's brand asks customers to trust a global map. The business will be strongest if it makes the control behind that map as visible as the map itself.

Evidence register

The following public sources anchor the analysis: