novacloud-admin

At a glance

• Autonomous system numberLinked with AS209874, AS49581, AS203446, AS215787 +2High confidence
• Address blocks2 address blocks currently recordedHigh confidence

Basic information

• Display namenovacloud-adminHigh confidence
• Directory categoryCompanyHigh confidence
• Last updatedJun 12, 2026High confidence

Locations

• Geography scopeNetherlandsHigh confidence
• Data centerNetherlandsMedium confidence
• ColocationNetherlandsMedium confidence
• Internet accessNetherlandsMedium confidence
• Peering and IXPsNetherlandsMedium confidence
• Security and DDoSNetherlandsMedium confidence

What it does

• Data centerNetherlands, Data center operator, Public registry sourceHigh confidence
• ColocationNetherlands, Colocation provider, Public registry sourceHigh confidence
• Internet accessNetherlands, Internet access provider, Public registry sourceHigh confidence
• Peering and IXPsNetherlands, Peering or exchange entity, Public registry sourceHigh confidence
• Security and DDoSNetherlands, Network security provider, Public registry sourceHigh confidence

Network identity

• Autonomous system numberAS209874High confidence
• Autonomous system numberAS49581High confidence
• Autonomous system numberAS203446High confidence
• Autonomous system numberAS215787High confidence
• Autonomous system numberAS62403High confidence
• Autonomous system numberAS48314High confidence

IP address resources

Other network resources

• Data centernovacloud-admin Netherlands Data center · NetherlandsHigh confidence
• Data centernovacloud-admin Netherlands Colocation · NetherlandsHigh confidence
• Service platformnovacloud-admin Netherlands Internet access · NetherlandsHigh confidence
• Internet exchangenovacloud-admin Netherlands peering/IXP · NetherlandsHigh confidence
• Service platformnovacloud-admin Netherlands security/DDoS · NetherlandsHigh confidence

People and contacts

• ContactsCommercial, NOC, AbuseMedium confidence
• Available contact typesCommercial, NOC, AbuseMedium confidence

Registry and related records

• Editorial contextNovacloud's service layer under the microscope: DNS split, twin status pages and a 19-day outage the registry never sees, The storefront sells three European datacenters and direct control over routing. The operator's own incident records and third-party DNS data describe something more layered — and more dependent — than the marketing suggests.Medium confidence
• Editorial contextWho answers for AS209874: Novacloud's contact surfaces, registry objects and the handle that resolves to nothing, Novacloud, the hosting and IP-transit brand operated by Portugal's Tech Tide Portugal Unipessoal LDA, runs a small European network under autonomous system number 209874. Previous BTW reporting has followed the company from several angles: routing mirrors that disagree about how many prefixes the network announces, a transit-dependency structure far narrower than the marketing suggests, a commercial-legal paper trail in which the Portuguese registry classifies the operator as a consultancy, and storefront and status pages that contradict each other. This report examines the layer none of that coverage assembled: the accountability and contact surface. Who does the registry name? Who does the operator's own web properties name? Where the two diverge, what does a customer, a downstream network, or an abuse reporter actually reach?Medium confidence
• Editorial contextNovacloud's AS209874: A Routing Footprint the Mirrors Can't Agree On, Novacloud, the hosting and IP-transit brand operated by Portugal's Tech Tide Portugal Unipessoal LDA, runs the tiny autonomous system AS209874. On 4 October 2026, public routing mirrors captured on the same day disagreed with each other about how many IPv4 prefixes that system announces, the operator shows no verifiable exchange-point presence, and no captured record resolves who actually stands behind the 'novacloud-admin' handle. For a company selling IP transit, that thin auditable layer matters.Medium confidence
• Editorial contextNovaCloud-Hosting's real transit story: three small upstreams behind a Tier-1 marketing front, NovaCloud-Hosting sells itself as a globally connected European host, but the registry and the routing table tell a narrower story. This investigation reconstructs who actually carries the operator's traffic, why its own pages contradict each other, and what a customer is really depending on.Medium confidence
• Editorial contextNovaCloud-Hosting's paperwork does not match its storefront: the commercial-legal trace BTW had not yet examined, NovaCloud-Hosting presents one commercial face to customers, but the Portuguese registry, the LEI record and the operator's own checkout pages tell a different story about what kind of company is actually selling the hosting. This briefing reads that paperwork layer — the part of the operator's footprint that prior BTW coverage of routing, registry delegation and status pages had not examined.Medium confidence
• Editorial contextNovaCloud-Hosting's own surfaces contradict themselves: an InStock storefront, a closed-review Trustpilot page and two disagreeing status pages, Prior BTW reporting mapped NovaCloud-Hosting's routing footprint, its registry delegation and the aftermath of the 19-day Frankfurt FFM2 outage of July 2026. What none of that coverage examined is the operator's own commercial and technical surfaces — what the company tells its own customers. A read of those surfaces in early October 2026 shows a picture that is internally contradictory: a storefront still marking products as InStock while a Trustpilot page says the company's website has closed, two status pages for the same brand disagreeing about the same infrastructure, and an upstream list on the operator's own ASN microsite that matches neither external observation nor the operator's own incident narrative.Medium confidence
• Editorial contextNovaCloud-Hosting's registry administration is split across three maintainers: who actually runs the operator's record?, NovaCloud-Hosting, the hosting brand of the Portuguese company Tech Tide Portugal Unipessoal LDA, operates its own autonomous system, AS209874. Previous BTW coverage mapped the routing footprint, the aftermath of the 19-day Frankfurt FFM2 outage of July 2026, and the fact that the brand sits under two distinct RIPE organisation handles [https://btw.media/en/novacloud-admin-registry-accountability]. What none of that reporting examined is the delegation layer beneath the organisations: who maintains and administers the operator's registry objects in practice. A direct read of public whois and RDAP mirrors on 1 October 2026 shows the answer is not one party but three — the operator's own maintainer, a German network company, and a UK sponsoring LIR — each with its own contact route, while the operator's commercial imprint presents a single unified surface.Medium confidence
• Editorial contextOne operator, two RIPE organisations: the administrative layer BTW had not yet mapped, Prior BTW coverage of NovaCloud-Hosting — the Portuguese-registered host operating under AS209874 — has tracked the gap between what the operator announces and what its network can actually deliver: five routing mirrors disagreeing on prefix counts, a registered /24 invisible in the global routing table, and the contradictory status pages surrounding the 19-day FFM2 outage of July 2026. What none of that reporting examined is the layer beneath the routing: who, in the RIPE registry, actually administers the operator's objects. A direct read of the registry record on 1 October 2026 shows an administrative footprint split across two distinct RIPE organisation identities, two different maintainer accounts and two different abuse routes — a structure the operator's own legal imprint does not disclose.Medium confidence

Source basis

• public registry sourcePublic registry sourceHigh confidence

How to read these connections

• Address compositionThe visible prefix footprint is IPv6-only with 2 announced prefixes.Medium confidence

Related research

• Primary articleNovacloud's service layer under the microscope: DNS split, twin status pages and a 19-day outage the registry never seesHigh confidence
• Primary articleWho answers for AS209874: Novacloud's contact surfaces, registry objects and the handle that resolves to nothingHigh confidence
• Primary articleNovacloud's AS209874: A Routing Footprint the Mirrors Can't Agree OnHigh confidence
• Primary articleNovaCloud-Hosting's real transit story: three small upstreams behind a Tier-1 marketing frontHigh confidence
• Primary articleNovaCloud-Hosting's paperwork does not match its storefront: the commercial-legal trace BTW had not yet examinedHigh confidence
• Primary articleNovaCloud-Hosting's own surfaces contradict themselves: an InStock storefront, a closed-review Trustpilot page and two disagreeing status pagesHigh confidence
• Primary articleNovaCloud-Hosting's registry administration is split across three maintainers: who actually runs the operator's record?High confidence
• Primary articleOne operator, two RIPE organisations: the administrative layer BTW had not yet mappedHigh confidence
• Primary articleNovaCloud-Hosting after FFM2: the registry footprint that refuses to moveHigh confidence
• Primary articleNovaCloud-Hosting one month on: PletX still listed, Trustpilot still closedHigh confidence
• Primary articleNovaCloud after the outage: what the record shows about the gap between storefront and networkHigh confidence
• Primary articleNovaCloud-Hosting, re-checked against the record: what first-hand page reads confirm about the announced-service gapHigh confidence
• Primary articleNovaCloud-Hosting: the €3.95 VPS plan and the network behind the storefrontHigh confidence
• Primary articleNovaCloud: two autonomous systems, one brand, and the gap between marketed cloud and routed realityHigh confidence
• Primary articleThe Control Surface Behind novacloud-admin: Who Actually Holds Administrative AuthorityHigh confidence
• Primary articleNovaCloud Admin: one brand, several operators, no single accountable roleHigh confidence