Summary

  • The marketed catalog and the independently observable routing record still diverge after the July 2026 outage: a Trustpilot page states the website has closed while the storefront's indexed listing still shows InStock offers, and five routing mirrors disagree on how many prefixes AS209874 originates.
  • The outage record itself is the newest continuity evidence: operator status pages documented a July 2026 Frankfurt (FFM2) incident with different restore states per service, and a timestamped third-party reading from 2026-07-20 shows the routing footprint still visible mid-incident.
  • No RIPE object carries the handle novacloud-admin; registry identity runs through the role object novacloud-hosting (NA8939-RIPE), abuse contact NA8940-RIPE, organisation ORG-MWUL2-RIPE and maintainer novacloud-mnt.
  • The evidence pattern is documented divergence, not a conclusion about intent: every claim below is attributed to a named source, and none establishes what happened inside the operator's business.

The operator behind the brand is Tech Tide Portugal Unipessoal LDA, registered in Quarteira, Portugal, VAT PT517354420, founded in 2023, operating the autonomous system AS209874 and marketing services from Frankfurt am Main, Nuremberg and Eygelshoven https://novacloud-hosting.com/. Portuguese company-registry mirrors list the same entity https://empresite.jornaldenegocios.pt/TECH-TIDE-PORTUGAL.html.

The storefront still advertises; the storefront status is disputed

The operator's homepage, as captured by a search-index excerpt, still lists seven service categories — KVM VPS, game servers, web hosting, GPU servers, dedicated servers, storage and network services — and embeds structured-data offers marked InStock, priced from 2.00 EUR per month (Plesk Webspace Solar) and 3.50 EUR per month (XEON Nova), pointing at its shop subdomain https://novacloud-hosting.com/. A separate capture of the shop itself was also retained in this run's source set https://shop.novacloud-hosting.com/?language=english.

Against that, the operator's Trustpilot business page states that the company's website has closed https://www.trustpilot.com/review/novacloud-hosting.com. These two statements cannot both describe the same present. No live checkout test was performed in this research pass, and the homepage excerpt's freshness is unknown, so the honest reading is a documented contradiction between two public pages, not a verified closure or a verified reopening. Community discussion moved in the same direction: a Lowendtalk thread titled "NovaCloud-Hosting seems to have died" records users' claims of service discontinuation https://lowendtalk.com/discussion/219410/novacloud-hosting-seems-to-have-died, alongside earlier threads critical of the operator https://lowendtalk.com/discussion/206620/novacloudhosting-scam-false-promising-and-lie https://lowendtalk.com/discussion/214986/review-novacloud-hosting and one offering free transfer of a VPS https://lowendtalk.com/discussion/216139/free-transfer-of-novacloud-hostings-pumpkin-ryzen-vps.

The operator's own status pages are the newest continuity evidence

The most informative new material is the operator's status infrastructure. Two separate status pages on the instatus platform exist for the operator, including a per-incident page https://novacloud-hosting.instatus.com/ and a main status page https://novacloud.instatus.com/cmrsxwgnz06wh1ao0b04o4obb. The July 2026 incident, centred on the FFM2 Frankfurt facility, was not a uniform event: IP-transit and High-End VPS services were reported restored while Standard VPS in Germany and dedicated/colocation remained down — a service-by-service restore pattern rather than a single all-clear. The status updates during the incident referenced AS203446, AS215787 and PletX as the operative transit paths.

That last detail matters because it is a self-description made under operational stress, when marketing copy is least curated. It names a transit set that does not match the operator's own marketing site.

Five mirrors, five different footprints

Third-party routing views of AS209874 still disagree with each other, and the disagreement is substantive:

  • Hurricane Electric's canonical page counts 34 originated prefixes (17 IPv4, 17 IPv6), 4,352 IPv4 addresses, 9 observed peers, and reproduces the RIPE aut-num created 2025-04-24, as-name TECHTIDE, organisation ORG-MWUL2-RIPE, maintainer novacloud-mnt https://bgp.he.net/AS209874. Hurricane Electric also flags that AS209874 announces bogons https://bgp.he.net/AS209874.
  • Hurricane Electric's own IPv4-specific subdomain page returns a different count from the same provider: 39 prefixes (22 IPv4, 17 IPv6) and 5,632 IPv4 addresses https://ipv4.bgp.he.net/AS209874.
  • bgp.tools reports 22 IPv4 and 16 IPv6 prefixes originated, with upstreams AS203446 (SMARTNET), AS49581 (Tube-Hosting) and AS215787 (TELE90) https://bgp.tools/as/209874.
  • CIDR Report, from a single RouteViews vantage point, shows 21 announced prefixes and — notably — labels the AS "-Reserved AS-, ZZ", meaning the operator's registry identity does not propagate into that analysis pipeline at all https://www.cidr-report.org/cgi-bin/as-report?as=AS209874&v=4&view=6447.
  • Whisper, the only source in this set with an explicit timestamp, recorded on 2026-07-20 at 14:37:45 GMT that AS209874 announced 37 routed IP prefixes and peered with 8 other autonomous systems — a reading taken inside the outage window https://canon.whisper.security/asn/209874.

IPregistry, whose data is registry-derived and dated 2026-02-26 rather than a live routing reading, lists 17 IPv4 ranges and states flatly that AS209874 "does not have any direct peering agreements" and reaches the Internet only through transit providers https://ipregistry.co/AS209874. That statement conflicts with the peer counts at HE and bgp.tools, which likely count downstream or customer adjacencies as peers — the ambiguity itself is part of the evidence.

The upstream sets conflict across every layer: the operator's ASN marketing site names AS62403 (PletX GmbH), AS49581 (Ferdinand Zink / Tube-Hosting) and AS48314 (IP-Projects GmbH & Co. KG), with PoPs in Germany and the Netherlands and datacenters NTT FRA1 and SkyLink https://as209874.net/; HE and IPregistry match that set https://bgp.he.net/AS209874 https://ipregistry.co/AS209874, while bgp.tools and CIDR Report name AS203446, AS49581 and AS215787 https://bgp.tools/as/209874 https://www.cidr-report.org/cgi-bin/as-report?as=AS209874&v=4&view=6447 — and the operator's own July 2026 status updates named AS203446, AS215787 and PletX. Two additional registry-mirror views of the ASN were retained for cross-checking https://whois.ipip.net/AS209874 https://novacloud-hosting.com/imprint.

Registry identity: who the network says it is

No RIPE object carries the handle novacloud-admin — the closest artefact is the maintainer novacloud-mnt. Administrative authority for AS209874 is visible through the role object novacloud-hosting (NA8939-RIPE) as admin-c and tech-c, the abuse contact NA8940-RIPE, and organisation ORG-MWUL2-RIPE belonging to Tech Tide Portugal Unipessoal LDA, registration number 517354420; BTW's earlier registry-accountability analysis documents this chain https://btw.media/en/novacloud-admin-registry-accountability. The imprint page on the operator's own site identifies the same legal entity https://novacloud-hosting.com/imprint.

What the gap looks like now

Compared with the gap documented on 2026-09-28 — a full HA product line marked "Coming Soon" with prices to be announced https://novacloud-hosting.com/vps-high-end, conflicting upstream lists, and a peering claim uncorroborated by third parties — the post-outage record shows neither convergence nor collapse. The routing footprint remained visible during the incident https://canon.whisper.security/asn/209874, the storefront still advertises https://novacloud-hosting.com/, the community record claims closure https://www.trustpilot.com/review/novacloud-hosting.com https://lowendtalk.com/discussion/219410/novacloud-hosting-seems-to-have-died, and the mirrors still disagree with each other and with the operator's own pages. Two reputation-scanner pages were also retained as part of the source set https://www.scam-detector.com/validator/novacloud-hosting-com-review/ https://gridinsoft.com/online-virus-scanner/url/novacloud_hosting-com; neither adds verifiable operational information.

The verifiable condition that would distinguish a functioning cloud operator from a nominal one remains the same: purchasable plans confirmed by a live transaction, upstream sets consistent across the operator's pages and independent mirrors, and prefix counts that converge. On the current public record, none of those conditions is met.

A methodological note applies to every source above: this research pass read indexed page excerpts rather than raw full-page fetches, and only Whisper carries an explicit as-of timestamp. Checkout functionality and page freshness were not verified. The evidence supports documented divergence between public claim layers; it does not establish intent.