WAYSCloud Status

Issue affecting IP Intelligence has been resolved.

Investigating an issue affecting IP Intelligence. IP lookups and threat scoring may be delayed

LLM API is operating normally.

Investigating an issue affecting LLM API. AI-powered features and completions may be unavailable

S3 Gateway Node is operating normally.

Issue detected with S3 Gateway Node. Investigating. Direct S3 operations may experience issues

Storage API is operating normally.

Investigating an issue affecting Storage API. File uploads, backups, and media storage may be affected

Resolved — all services fully operational

All issues related to this incident have now been resolved, and our platform is back in normal operation. The upstream network fault has been cleared, our rerouted network paths are stable, and all affected services — the Customer Portal, App Platform, Database, DNS, Storage, LLM, IoT, SMS and security services — are confirmed operational.

Customer service channels are restored. Calls, emails and support requests are reaching us again. As promised, any enquiry that arrived during the incident will be answered — you do not need to contact us again or resend your message.

We sincerely apologise for the inconvenience this incident has caused. We will continue to follow up on this matter with our upstream provider and internally, and we will review and improve our routines to reduce the risk and impact of similar incidents in the future.

Thank you for your patience throughout this incident.

Customer service channels also affected

This incident is also affecting our customer service centre and inbound enquiries. Calls, emails and support requests may fail to reach us or be significantly delayed. If you have already contacted us and not had a reply, it is possible your message did not arrive.

Please note: this supersedes the advice in our earlier updates. While these channels are degraded, contacting support is not a reliable way to get information about this incident, and we would rather you did not spend time waiting on a reply that may not come.

We recommend following this status page for the latest information. We are updating it as the situation develops, and it is currently the most reliable channel we have.

Any enquiries that did reach us will be answered once our support channels are restored, and we will confirm here when that has happened. You do not need to contact us again to keep your place — please avoid resending, as duplicate enquiries will slow down our recovery of the queue.

We will post the next update by 15:45 CEST.

Further problems upstream — rerouting continues

Our upstream provider has run into further significant problems with their remediation. We are in direct contact with them while they work on it.

In parallel, we are continuing to reroute traffic across our own network infrastructure, so that our recovery does not depend on the provider's timeline alone.

Current impact Services remain reachable, but they are not yet stable. You may see intermittent failures, timeouts or slow responses, and sign-in and authenticated API requests may still fail for some customers. We are holding the affected services on this page at "Performance Issues" rather than marking them operational, because we cannot yet confirm they are fully healthy.

If a request fails, please retry. If the problem persists for you, please contact support so we can look at your specific case.

We will post the next update by 15:45 CEST.

API restored — around 90% of the platform available

Our API is operational again, and approximately 90% of the platform is now available. The rerouting of our network infrastructure has taken effect, and the majority of services have returned to normal operation.

We are moving the affected services on this page from "Major Outage" to "Performance Issues" to reflect this. They are reachable again, but we are not yet declaring them fully healthy.

Still outstanding Work continues on the remaining portion of the platform. Some requests may still fail or respond slowly, and you may see brief interruptions as the last components are brought back onto the restored paths.

If you are still unable to sign in or authenticate API requests, please retry — and if the problem persists, contact support so we can investigate your specific case.

We will post the next update by 15:30 CEST, and will resolve this incident once all services are confirmed healthy.

Parallel rerouting underway

In addition to working with our upstream provider, we have begun rerouting our own network infrastructure away from the affected path. This work is running in parallel with the provider's remediation, so that restoration does not depend on a single track.

The rerouting is being carried out in stages. As traffic is moved onto the new paths, individual services may briefly become unavailable or return errors during cut-over — including services that had already recovered. This is expected, and each occurrence should be short-lived.

The authentication layer remains the main outstanding item. Sign-in, new account registration, and authenticated API access continue to be affected.

We will post the next update by 15:15 CEST.

Partial restoration — authentication layer still affected

Upstream network connectivity has been restored across the majority of the affected platform, currently around 70% of the surface. Most services are reachable again, and work continues on the remainder.

Authentication is still degraded. Parts of our authentication layer are not yet operational. This matters even where the underlying service has returned to normal, because requests against it cannot be authenticated. Customers should expect the following to be affected:

• Sign-in to the Customer Portal
• New account registration
• API access — authenticated requests may be rejected or fail intermittently, including with valid credentials

Established sessions and existing tokens are less likely to be affected, and services that do not require authentication should behave normally.

What to expect Connectivity may remain intermittent while the remaining components are restored, so occasional errors, timeouts or slow responses are still possible even on services that appear to be back. If a request fails, please retry shortly.

Restoring the remaining components is our highest priority. We will post the next update by 15:00 CEST.

Recovery in progress

Network connectivity to the affected platform has been restored, and services are now coming back up gradually.

Our systems are reaching the affected infrastructure again as of approximately 14:25 CEST. Not every service is serving traffic yet — recovery is staged, so services will return in groups rather than all at once. While the platform stabilises you may still see failed requests, timeouts or slower than usual responses.

No action is required on your side. If a request fails, please retry shortly.

We are keeping the affected services marked as down on this page until we have confirmed each one is healthy, so this page may lag slightly behind actual recovery. We will post the next update by 15:00 CEST.

Cause identified

We have identified the cause of this outage: a network layer fault at one of our upstream infrastructure providers in Norway. The failure is on the provider's side, and it is what is making our portal and API services unreachable.

We are in direct contact with the provider and are working to restore the affected services as quickly as possible.

Services that do not depend on the affected network path — DNS Nameservers (Norway, Sweden, Finland, Denmark), WAYSCloud Connect, WAYSCloud Drive, GPU Studio and Redis Service — continue to operate normally.

We do not yet have a confirmed time to resolution. We will post the next update by 15:00 CEST.

We are currently experiencing a major outage affecting the majority of WAYSCloud services.

What is happening From approximately 13:39 CEST on 3 September 2026, the portal and our API services became unreachable. This affects the Customer Portal, App Platform, and our Database, DNS, Storage, LLM, IoT, communication (SMS, Voice, Verify, Email Compliance) and security intelligence APIs.

Confirmed unaffected DNS Nameservers (Norway, Sweden, Finland, Denmark), WAYSCloud Connect, WAYSCloud Drive, GPU Studio and Redis Service are operating normally. Existing DNS resolution is not affected.

What we know The fault is at the network layer, upstream of our platform. The individual services themselves are not at fault — they are unreachable because of the network failure.

Next update We will post an update within 30 minutes, or sooner if we have more information.