โ—€ BACK TO LEADERBOARD

โšก Operational Services

๐ŸŒ
MTCTiers Web App (mtctiers.com)
Latency: Checking...
Checking...
๐Ÿ“œ
Web App Script (app.js)
Syntax Check: Checking...
Checking...
๐Ÿ”ฅ
Firebase Firestore Database
Read Ping: Checking...
Checking...
๐Ÿค–
MTCTiers Discord Bot (Railway Service)
WebSocket Gateway: Checking...
Checking...
๐Ÿ”‘
Google OAuth Authentication
Auth Domain Ping: Checking...
Checking...

๐Ÿ“œ Past Incident Log

August 26, 2026 โ€” 11:15 UTC
Resolved: Firestore 403s & Discord Bot Data Layer
Anonymous REST writes were failing closed and the bot treated that as success, serving stale JSON. The bot now uses the Firebase Admin SDK on Railway. Duel identity is one integer (`#365` next). Site share links are `?tab=duels&duel=365`. Firestore rules: public read on rankings/duels, no client writes. Save Profile / Submit Duel on the website stay disabled until those writes go through the bot.
August 7, 2026 โ€” 20:00 UTC
Resolved: Firestore Rankings Cache & Duel History Alignment
All nested kit tier maps in Firestore have been flattened and unified. Duel perspective outcome descriptions for promoted players have been corrected across web rankings and Discord bot notifications. All services operational.
August 5, 2026 โ€” 18:30 UTC
Resolved: Railway Gateway Intent Sharding Adjustment
Adjusted unprivileged Discord bot gateway intents to resolve reconnecting loops on Railway. Bot response time restored to under 45ms.