StreamWizard system status: Loading status

How the status traffic light works

StreamWizard depends on several platforms: Twitch, Kick and YouTube provide chat, stream data and sign-in, Discord carries the bot, and Stripe handles payments. This page checks the services StreamWizard needs for that, plus our own servers. At a glance you can see whether a problem lies with StreamWizard itself or with a platform we have no control over.

Checks run from our server, not from your browser. A result stays valid for 120 seconds so the platforms are not queried again on every page view; the page itself reloads every 60 seconds. Each single check gives up after 6 seconds so a hanging service cannot block the traffic light.

What the colours mean

Green

All checks for the service respond as expected.

Yellow

The service works, but with limitations – for example when the platform's official status page reports an incident, cannot be reached itself, or only one of several server instances is running.

Red

The service cannot be reached or answers with an error. Features that depend on it are likely to fail.

Not automatically checkable

The check is not set up on this server or deliberately switched off, such as an optional cache. This is not an error; the feature then runs another way.

Which services are checked

The rating says how strongly StreamWizard depends on a service: “critical” means core features fail without it; “important” means individual features are affected; “optional” means operation continues without it.

• Twitch

  Streaming platforms · Rating: critical

  Used for: OAuth, Helix API, chat/EventSub workflows, Streamstats, and OBSBot/rafflebot platform logic.

  If it fails: Login or API issues affect Twitch connections, token refresh, stream data, and chat/bot features.

  Official page of Twitch (opens in a new tab)

• Kick

  Streaming platforms · Rating: critical

  Used for: Kick OAuth, chat/API features, public-key verification for webhooks, and OBSBot Kick runtime.

  If it fails: Outages affect Kick authorization, chat, viewer/channel data, and event subscriptions.

  Official page of Kick (opens in a new tab)

• YouTube / Google APIs

  Streaming platforms · Rating: important

  Used for: Retrieval of public channel data through the YouTube Data API for the OBS plugin schedule.

  If it fails: Issues delay refreshing the video list. Already scheduled videos keep playing, and local files are not affected at all.

  Official page of YouTube / Google APIs (opens in a new tab)

• Discord

  Login, community, and bot platform · Rating: critical

  Used for: Login, support server, Discord bot/DM flows, role sync, avatars, and dashboard access.

  If it fails: Incidents can affect sign-in, support access, DMs, role sync, and avatar delivery.

  Official page of Discord (opens in a new tab)

• StreamWizard StreamwizardNode

  StreamWizard runtime · Rating: critical

  Used for: Central Discord gateway service for OBSBot, RaffleBot, Discord dispatch, and outbound Discord messages.

  If it fails: If this service is degraded, Discord commands, buttons, DMs, threads, and bot output may be delayed or unavailable.

• StreamWizard loginserver

  StreamWizard runtime · Rating: important

  Used for: Offloads the Twitch viewer login of public giveaway profiles from the PHP-FPM pool (faster, load-resilient logins).

  If it fails: If no login node is fresh, the viewer login automatically falls back to the classic PHP flow (fail-open) – slower under load, but no outage.

• StreamWizard website & API

  StreamWizard runtime · Rating: critical

  Used for: Dashboard, giveaway profiles, viewer login, the REST API for the bots, plus payment and account management — everything runs through this web stack.

  If it fails: Incidents affect dashboard access, giveaway pages, and the bot API at the same time. The fact that you can see this page shows the web server itself is responding.

• Stripe

  Payments and billing · Rating: critical

  Used for: Checkout, billing portal, Premium/VIP/Diamond payments, webhooks, invoices, and tax exports.

  If it fails: Outages affect purchases, subscriptions, webhook processing, invoice sync, and payment state.

  Official page of Stripe (opens in a new tab)

• StreamElements

  Integrations · Rating: important

  Used for: Optional StreamElements import (points/watchtime import into the giveaway system, initiated by the creator).

  If it fails: Incidents affect only the optional StreamElements import, not core sign-in, payments, or the giveaway itself.

  Official page of StreamElements (opens in a new tab)

• Trustpilot

  Reviews and trust · Rating: optional

  Used for: Public review display and optional review invitations after purchases.

  If it fails: Outages affect only review display or invitations, not login, downloads, bots, or payments.

  Official page of Trustpilot (opens in a new tab)

• IndexNow

  Search and discovery · Rating: optional

  Used for: Sitemap pushes to participating search engines after public page changes.

  If it fails: Outages only delay search-engine pings; the website and bots continue running.

  Official page of IndexNow (opens in a new tab)

• Google Public DNS

  Diagnostics and admin checks · Rating: optional

  Used for: Optional DNS resolution in admin/security checks.

  If it fails: Outages affect diagnostics convenience, not the actual StreamWizard runtime.

  Official page of Google Public DNS (opens in a new tab)

• Google Tag / Analytics

  Consent-based analytics · Rating: optional

  Used for: Optional reach measurement after cookie consent.

  If it fails: Outages affect optional analytics only, not product features.

  Official page of Google Tag / Analytics (opens in a new tab)

What you can do during an outage

If a platform is red or yellow, the cause usually lies there – waiting until the platform has fixed its incident is the only option. The service’s official page (link above) usually names the cause and expected duration. If everything is green and something still does not work, please report it with the time and the affected feature via the contact form.