Automated Battle.net Server Status Alerts
Every hour, WebRun opens Battle.net, checks service status and any scheduled maintenance against the team's practice and match calendar, posts a routine update to Slack, and sends a Telegram alert when an outage overlaps a scrim or match window.
How do I get warned before a Battle.net outage disrupts a scheduled scrim?
WebRun checks Battle.net service status and scheduled maintenance every hour, posts a routine update to Slack, and sends an urgent Telegram alert only when an outage overlaps a scheduled scrim or match. Esports organizations get an early warning before players sit down to a game that is not actually up.
- Outages overlapping a scrim are flagged within the hour
- Routine status checks stay out of urgent channels
- Coaches get a heads up before players waste a practice slot
Built for esports organizations · gaming community managers · team coaches · tournament operations staff
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
battle.netin a real browser with your saved login - no setup, no API keys. -
1
Battle.net - check service status and maintenance
- Open the service status page for the team's games
- Note any active incident or scheduled maintenance window
- Compare the maintenance window against today's scrim or match schedule
Done when Current status and any overlapping maintenance are captured.
-
2
Slack - post the routine status update
slack.com
WebRun opens Slack to post the routine status update. - Post the hourly status check to the team channel
- Note any upcoming maintenance window even if it doesn't conflict
- Keep the message short when everything is normal
Done when The team channel has the current hourly status.
-
3
Telegram - escalate outages hitting a scrim window
telegram.org
WebRun opens Telegram to escalate outages hitting a scrim window. - Send an urgent message only when an outage overlaps a scrim or match
- Include the affected game and the expected resolution time
- Skip this step entirely when there is no conflict
Done when The team has an urgent alert whenever status overlaps scheduled play.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it change anything in Battle.net or reschedule scrims?
No. WebRun only reads the public service status page. Moving a scrim or match is always a call the team makes.
Why post to both Slack and Telegram?
Slack carries the routine hourly check for anyone catching up later. Telegram is reserved for the rare case where an outage actually overlaps scheduled play, so it stays worth an immediate look.
How current is the status check?
It reads the live status page each hour, so a new incident is reflected within the hour it starts.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.