Streamotive was unavailable for much of Saturday 23 May 2026 after a distributed denial-of-service (DDoS) attack hit VentraIP, the Australian hosting provider that carries our production environment. If you tried to load tools, dashboards, or APIs and saw timeouts or errors, that was almost certainly this upstream incident—not a planned maintenance window or a change on our side.
We are sorry. Losing access to the tools you rely on during a stream or a content workflow is frustrating, and we do not consider today’s disruption acceptable for a service you trust with your channel. Our team monitored VentraIP’s status board and worked with whatever connectivity remained to keep you informed where we could. We have also begun migrating Streamotive to a dedicated host so future incidents on shared provider networks are far less likely to take us offline with everyone else on the same edge.
What VentraIP reported
VentraIP first flagged the event at 10:34 AEST on 23 May 2026, stating that an ongoing DDoS attack was under investigation. Over the following hours the provider posted repeated updates: early messages asked for patience while engineers investigated; later ones described work with upstream partners to apply mitigations, warned of intermittent connectivity, and noted efforts to strengthen DDoS defences.
By 17:38 AEST, VentraIP reported that its team and upstream vendors had tentatively mitigated the attack and that services across their network were recovering. They committed to a full post-incident review (PIR) for customers with more detail on cause and hardening—something we will read closely as we finalise our own hosting plans.
If you were refreshing our site during the afternoon, you may have seen brief moments where pages loaded and then failed again—that pattern matches VentraIP’s own warnings about intermittent stability while mitigations were rolled out, not isolated bugs in Streamotive’s application code.
What this meant for Streamotive
Streamotive’s web app, authentication flows, and API endpoints all depend on the same network path as our host. When VentraIP’s edge was saturated or unstable, everything behind it became unreachable: no logins, no clip tools, no browser-source endpoints, no status page on our domain if it resolves through the same stack.
We did not take the site down deliberately. We did not ship a breaking release today. The outage was infrastructure-level, driven by an attack aimed at VentraIP’s network rather than at Streamotive by name. That distinction matters for blame and for fix—but it does not change the outcome for you, which was an unacceptable day of downtime from our perspective.
We apologise to every creator and team who could not reach Streamotive today. This level of unavailability is not what we build for, and we are treating it as a forcing function to move to dedicated infrastructure.
What we are doing next
Migration to a dedicated host is already underway. Shared hosting and multi-tenant edges can be cost-effective, but today showed the downside: a provider-wide DDoS can blank every customer on that network at once. A dedicated environment gives us clearer capacity boundaries, more control over failover, and separation from unrelated tenants when upstream attacks spike.
We will not promise a finish date in this post while engineering and DNS cutovers are still being scoped. We will publish a follow-up when migration milestones are locked and when we have a clearer picture from VentraIP’s promised PIR.
In the meantime:
- If something still fails intermittently, wait a few minutes and retry—residual edge instability may linger after the “recovering” status.
- Save work locally when you can (overlay configs, clip lists) so a future blip does not block you mid-stream.
- Watch this site and our usual channels for migration updates; we will be explicit before any DNS or URL changes affect how you bookmark tools.
Recovering, not “resolved”
VentraIP’s latest public message describes the situation as recovering, not fully closed. We are aligning our communication with that: Streamotive should be reachable again for most users, but we will stay cautious until we see stable metrics on our side and until our dedicated migration reduces reliance on this shared path.
We appreciate your patience today. We do not expect you to be satisfied with “upstream had a bad day” as the final word—and we are not satisfied either. The work to make that less likely starts now.