Infinity Bots - Notice history

Experiencing partially degraded performance

96% - uptime

Production - Degraded performance

96% - uptime
Apr 2025 · 100.000%May · 93.9135%Jun · 93.4766%
Apr 2025
May 2025
Jun 2025

Development - Operational

97% - uptime
Apr 2025 · 100.000%May · 96.7115%Jun · 94.9102%
Apr 2025
May 2025
Jun 2025

Documentation - Operational

99% - uptime
Apr 2025 · 100.000%May · 100.000%Jun · 95.5282%
Apr 2025
May 2025
Jun 2025

Staff Panel - Operational

97% - uptime
Apr 2025 · 100.000%May · 95.4099%Jun · 95.3602%
Apr 2025
May 2025
Jun 2025

Widgets - Operational

93% - uptime
Apr 2025 · 100.000%May · 83.6022%Jun · 95.0940%
Apr 2025
May 2025
Jun 2025
94% - uptime

Production - Degraded performance

91% - uptime
Apr 2025 · 100.000%May · 89.1873%Jun · 85.2706%
Apr 2025
May 2025
Jun 2025

Development - Degraded performance

96% - uptime
Apr 2025 · 100.000%May · 94.1470%Jun · 94.8889%
Apr 2025
May 2025
Jun 2025
100% - uptime

Cloudflare → Always Online - Operational

Cloudflare → DNS Firewall - Operational

Cloudflare → DNS Root Servers - Operational

Cloudflare → DNS Updates - Operational

Cloudflare → Firewall - Operational

Cloudflare → Gateway - Operational

Cloudflare → Network - Operational

Cloudflare → Pages - Operational

Discord → API - Operational

Discord → Gateway - Operational

Github → Actions - Operational

Github → API Requests - Operational

Github → Git Operations - Operational

Github → Issues - Operational

Github → Pull Requests - Operational

Github → Webhooks - Operational

Ionos → Cloud Backup - Operational

Ionos → Cloud Server - Operational

Stripe → Stripe API - Operational

Vercel → Builds - Operational

Vercel → Build & Deploy - Operational

Vercel → DNS - Operational

Notice history

Jun 2025

Server Downtime
  • Postmortem
    Postmortem

    📝 Postmortem: June 2025 Service Outage

    Incident Duration:

    June 16, 2025 – June 21, 2025

    Status: Resolved

    Root Cause: Misconfigured infrastructure and networking components

    📌 Summary

    Between June 16 and June 21, 2025, our services experienced a prolonged and critical disruption. This impacted system accessibility, network stability, and overall deployment reliability. The root causes were traced back to multiple misconfigurations within our new infrastructure stack, primarily involving our Dokploy instance, networking setup, and reverse proxy (Traefik).

    ⚙️ Technical Cause

    Upon investigation, we identified several compounding issues:

    • Misconfigured Dokploy Instance: The initial deployment lacked critical network isolation and routing configurations, leading to service timeouts and container miscommunication.

    • Traefik Reverse Proxy: Misconfigured routing and TLS handling caused failed ingress connections and prevented external traffic from reaching internal services.

    • Networking Setup Errors: Overlapping subnets and improperly bridged networks led to intermittent connectivity between deployer and host machines, further destabilizing the system.

    • Missing Health Checks: Some containers were not being monitored properly, which delayed automatic restarts and extended service downtime.

    🚑 Immediate Actions Taken

    • Isolated deployer and host networks to stabilize inter-service traffic.

    • Corrected routing rules and middleware configuration in Traefik.

    • Rebuilt the Dokploy configuration with clearer network separation and improved error handling.

    • Re-enabled and audited health checks across services.

    • Conducted live testing and verification to ensure full service restoration by June 21, 2025.

    ✅ Resolution and Recovery

    The system was gradually stabilized beginning on June 16, with partial access restored within 30 minutes of our first major fix. However, additional network-level issues prolonged the resolution timeline. By June 21 at 3:35 AM, all services were fully restored and verified functional.

    📚 Lessons Learned

    • Configuration reviews must be enforced before production deployment of new infrastructure tools.

    • Network planning (IP ranges, bridges, proxies) needs to be documented and peer-reviewed.

    • Critical systems (like DNS routing, ingress, and orchestration layers) must have dedicated monitoring and rollback plans.

    🔧 Preventative Measures

    • Implement automated preflight checks in our deployment pipelines.

    • Schedule recurring audits of proxy and ingress configurations.

    • Build fallback container orchestration playbooks for Dokploy-based deployments.

    • Expand post-deploy smoke testing to catch network-level regressions earlier.

    🗣️ Final Note

    We sincerely apologize for the extended downtime and the impact it had on your experience. While our intention was to modernize our infrastructure, we recognize that our transition planning and oversight fell short. This will be addressed internally, and improvements are already underway.

    Thank you for your patience and continued support.

  • Resolved
    Resolved
    This incident has been resolved.
  • Update
    Update

    We apologize that these issues have been ongoing for so long, our team is still working to resolve the issues! And properly configure our new dokploy network!

  • Update
    Update

    Some additional issues have arised and we are working on a fix

  • Update
    Update

    We have isolated networks between our deployer and host machine to help stable out its long term usage, our team is currently finishing up with the final setup stages. Services should start being restored within the next 20 - 30 mins.

  • Identified
    Identified

    We have identified this issue is due to Dokploy. We are working resolving this issue now.

May 2025

Apr 2025

No notices reported this month

Apr 2025 to Jun 2025

Next