HalloweenBot - Notice history

100% - uptime
100% - uptime

Slash Commands - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025100.0% uptime
Feb 2025100.0% uptime
Mar 2025100.0% uptime

Prefix Commands - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025100.0% uptime
Feb 2025100.0% uptime
Mar 2025100.0% uptime

HalloweenBot 2 - Operational

99% - uptime
Jan 2025 · 96.70%Feb · 99.29%Mar · 100.0%
Jan 202596.70% uptime
Feb 202599.29% uptime
Mar 2025100.0% uptime
100% - uptime

HalloweenBot Website - Operational

100% - uptime
Jan 2025 · 99.93%Feb · 100.0%Mar · 100.0%
Jan 202599.93% uptime
Feb 2025100.0% uptime
Mar 2025100.0% uptime

Dashboard - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025100.0% uptime
Feb 2025100.0% uptime
Mar 2025100.0% uptime

CDN - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025100.0% uptime
Feb 2025100.0% uptime
Mar 2025100.0% uptime

API - Operational

100% - uptime
Jan 2025 · 99.88%Feb · 99.74%Mar · 100.0%
Jan 202599.88% uptime
Feb 202599.74% uptime
Mar 2025100.0% uptime
100% - uptime

Database - Operational

100% - uptime
Jan 2025 · 99.82%Feb · 100.0%Mar · 100.0%
Jan 202599.82% uptime
Feb 2025100.0% uptime
Mar 2025100.0% uptime

Third Party: Discord → API - Operational

100% - uptime

Shard 0 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025100.0% uptime
Feb 2025100.0% uptime
Mar 2025100.0% uptime

Shard 1 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025100.0% uptime
Feb 2025100.0% uptime
Mar 2025100.0% uptime

Shard 2 - Operational

100% - uptime
Jan 2025 · 99.97%Feb · 100.0%Mar · 100.0%
Jan 202599.97% uptime
Feb 2025100.0% uptime
Mar 2025100.0% uptime

Shard 3 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%
Jan 2025100.0% uptime
Feb 2025100.0% uptime
Mar 2025100.0% uptime

Notice history

Mar 2025

📢 Scheduled Maintenance Notice 📢
  • Completed
    March 06, 2025 at 1:42 PM
    Completed
    March 06, 2025 at 1:42 PM

    This has now been completed

  • Planned
    March 06, 2025 at 1:30 PM
    Planned
    March 06, 2025 at 1:30 PM

    🛠 Date: 6th March


    Impact: Possible service slowdowns or temporary unavailability

    We will be performing scheduled maintenance on our servers on the 6th of March. During this time, our services may respond slower or appear offline for short periods. We appreciate your patience and understanding.

    For real-time updates, check our status page.

    🔧 Thank you for your support!

  • In progress
    March 06, 2025 at 11:22 AM
    In progress
    March 06, 2025 at 11:22 AM

    We have started our scheduled maintenance earlier than planned and it will be taking place within the next 10 minutes. During this time, some services may respond slower or appear temporarily offline.

    We appreciate your patience and understanding.

Feb 2025

Jan 2025

🚨 Database Connection Issue - Ongoing Investigation
  • Resolved
    Resolved

    Resolution & Current Status

    ✅ A server restart has resolved the issue, and all systems are now operating normally.
    🛠 We have implemented monitoring to track database connections and optimize performance.

    Next Steps

    📌 Ongoing Monitoring: We will continue to observe system performance to ensure stability.
    📌 Preventative Measures: Additional optimizations, such as connection pooling and rate limits, are being explored to prevent future occurrences.

    Monitoring Status

    🔍 Database Health: ✅ Normal
    🔍 Bot Functionality: ✅ Fully Operational
    🔍 Redis Cache: ✅ Active

    🚀 Marking this issue as resolved, but we will continue to monitor.
    If you experience any further issues, please reach out to support via Discord. Thank you for your patience! 🎃

  • Monitoring
    Monitoring

    Issue Summary

    Earlier, we experienced database connection issues, leading to "Too many clients already" errors, which disrupted support ticket retrieval and certain bot functionalities.

    Resolution & Current Status

    🔄 A server restart has successfully resolved the issue, and all systems are now operational.
    🛠️ Monitoring has been enabled to track database connections and prevent future occurrences.

    Next Steps

    📌 Root Cause Investigation: We are analyzing logs to identify the underlying cause of the issue.
    📌 Preventative Measures: We will implement optimizations such as connection pooling and rate limits to avoid similar disruptions in the future.

    Monitoring Status

    🔍 Database Health: ✅ Normal
    🔍 Bot Functionality: ✅ Fully Operational
    🔍 Redis Cache: ✅ Active

    🚀 If you encounter any further issues, please reach out to support via Discord. Thank you for your patience! 🙌

  • Investigating
    Investigating

    Issue Summary

    We are currently experiencing database connection issues, resulting in "Too many clients already" errors in the logs. This may cause disruptions in certain bot functionalities, including database-dependent commands.

    Current Impact

    • Bot commands relying on the database may fail

    • Possible slowdowns in certain bot features

    Redis Workaround Available

    🔹 If you have used the bot within the last hour, your data may still be available in Redis. This allows some functionalities to continue working, but new database queries may be affected.
    🔹 We are redirecting temporary data to Redis where possible to reduce the impact.

    What We're Doing

    ⚙️ Our team is implementing database optimizations including:

    • Connection pooling to manage simultaneous connections

    • Increasing PostgreSQL client limits

    • Enhancing Redis caching to reduce direct database queries

    Next Update

    We will provide another update within 60 minutes, or as soon as the issue is resolved. Thank you for your patience! 🙌

    💡 Workaround: If you're experiencing issues, please try again later or contact support via Discord. 🚀

Jan 2025 to Mar 2025

Next