01
Public website and education pages
Public incident notice — manually maintained
Last updated: August 3, 2026
SignalShield status and support.
Use this page to check current public notes and see what to send if login, billing, TradingView alerts, journaling, or live system status behavior does not look right.
Status boundary
Public availability guidance, not broker monitoring.
This page is for SignalShield product availability and support direction. It does not monitor broker connectivity, verify market orders, execute trades, or replace the in-app Event/Journal Status view when a specific webhook, journal write, Discord delivery, cooldown, or lock needs review.
Areas to check
Start with the part of SignalShield that looks wrong.
These are product areas covered by the public status and support workflow. They are not individual automated uptime monitors.
02
Customer login and onboarding
03
TradingView alert workflow intake
04
Journal and system-state workflows
05
Billing and subscription access
Quick support paths
Start with the page that matches the question.
01→
Event/Journal Status
Check tracking health, last webhook receipt, last journal write, pending or failed events, Discord delivery, realtime state, and filter visibility.
Open path
02→
Product Updates
Review recent reliability, setup, and public-site changes before assuming behavior changed silently.
Open path
03→
Pricing and tier access
Confirm system counts, manual reset access, and analytics depth without treating Beta as a normal public tier.
Open path
Report an issue
Give support enough context to reproduce the problem.
For alert issues, include the SignalShield page and relevant TradingView alert context. Do not send brokerage credentials.
Page where it happened
Action you attempted
Expected result
Actual result
Approximate time
TradingView context for alert issues