Skip to main contentConnecting to monitoring
Status
Venon Security status
Public monitoring of the Discord bot, the dashboard, the API, the slash commands and the server protection services. The bot records a sample every 60 seconds and the page polls monitoring every 30 seconds. When monitoring goes quiet you get a concrete reason and a retry button — not an endless “Connecting…” or invented numbers.
60 s
Sampling interval
30 s
Page refresh cycle
90 days
Uptime history
Puls bota
Connecting…Ping
—
Baza
—
Czas pracy
—
Fetching component status…
The data comes straight from the running bot — nothing is simulated.
Fetching the status data
Venon · monitored every 60 s · refreshed every 30 s
Uptime (90 days)
No data
Running time
No data
Gateway ping
No data
Servers
No data
Members
No data
Commands
No data
System components
Component monitoring will refresh automatically.
Response time
Discord gateway ping
Current
No data
Average
No data
p95
No data
Peak
No data
Monitoring will refresh automatically once samples arrive.
Availability
Uptime — the last 90 days
The data is briefly unavailable.
90 days ago healthy degraded no datatoday
A sample every 60 seconds
Every minute the bot records the Discord gateway ping, the database response time and the availability of the services. The charts and statistics are built from those samples.
90-day retention
Daily availability results land on the uptime grid below. Each square is one day — hover to see the exact result.
Alert thresholds
The “degraded” status appears when the gateway ping goes above 300 ms or the database answers slower than 250 ms. No connection means an outage.
How it works
One event's journey through Venon
Every message, join and reaction takes the same path — in milliseconds, without slowing the chat down. Below is exactly what happens under the hood.
01
Discord gateway
The bot keeps a permanent WebSocket connection and receives events the moment they happen: messages, joins, reactions, role changes.
Always listening
02
Event router
Every event reaches a central router, which recognises its type and passes it only to the modules that actually need it.
Type classification
03
Protection layers
AntiRaid, Verify, LinkShield and AutoMod analyse the event in parallel — the account profile, the content, the links and the pace of activity.
Parallel analysis
04
Decision and response
If a rule is broken, the bot acts on your thresholds: a warning, a mute, a kick or a ban.
Your penalty thresholds
05
Logs and audit
The result goes to the logs and the case history — with the author, the reason and the time. Nothing happens without a trace.
A full trail
Monitoring
What does the Venon Security status mean?
The status shows the health of the services Discord administrators rely on for protection, moderation and running the server.
The public status page is the fast way to check whether Venon Security is working: the Discord bot, the web dashboard, the API, the slash commands, the logs and the protection services. Uptime is the percentage of time monitoring saw the service as available in the selected period. Ping shows the response time of the gateway or the API, and the components say whether a given part of the system runs normally, runs slower or needs attention.
Raw samples are kept for 7 days — the charts for the 1 h, 24 h and 7 d ranges are built from them. Daily availability summaries stay for 90 days and feed the history bars. A day without samples is marked as no data, not as a hundred percent availability.
If the status API goes quiet, the page does not fake valid data and does not sit in an endless “Connecting…”. Every attempt has a time limit; once it passes you see a concrete reason — an HTTP code, a network error or a timeout — plus a “Try again” button alongside the automatic background refresh. A monitoring problem does not always mean the bot is down, so when in doubt it is worth checking the support Discord.
Ready?
Having trouble with Venon Security?
Check the component status, read the documentation and join the support Discord if the problem concerns your server.