Infinity Bots - Geschichte beachten

Teilweise herabgesetzte Leistung festgestellt

93% - Betriebszeit

Production - Funktionsfähig

93% - Betriebszeit
Mai 2025 · 93.9135%Juni · 84.5278%Juli · 100.000%
Mai 2025
Juni 2025
Juli 2025

Development - Funktionsfähig

94% - Betriebszeit
Mai 2025 · 96.7115%Juni · 84.7894%Juli · 100.000%
Mai 2025
Juni 2025
Juli 2025

Documentation - Funktionsfähig

95% - Betriebszeit
Mai 2025 · 100.000%Juni · 85.4074%Juli · 100.000%
Mai 2025
Juni 2025
Juli 2025

Staff Panel - Funktionsfähig

94% - Betriebszeit
Mai 2025 · 95.4099%Juni · 85.4074%Juli · 100.000%
Mai 2025
Juni 2025
Juli 2025

Widgets - Funktionsfähig

90% - Betriebszeit
Mai 2025 · 83.6022%Juni · 85.1412%Juli · 100.000%
Mai 2025
Juni 2025
Juli 2025
92% - Betriebszeit

Production - Beeinträchtigte Leistung

91% - Betriebszeit
Mai 2025 · 89.1873%Juni · 84.8056%Juli · 100.000%
Mai 2025
Juni 2025
Juli 2025

Development - Funktionsfähig

93% - Betriebszeit
Mai 2025 · 94.1470%Juni · 84.7778%Juli · 100.000%
Mai 2025
Juni 2025
Juli 2025
100% - Betriebszeit

Cloudflare → Always Online - Funktionsfähig

Cloudflare → DNS Firewall - Funktionsfähig

Cloudflare → DNS Root Servers - Funktionsfähig

Cloudflare → DNS Updates - Funktionsfähig

Cloudflare → Firewall - Funktionsfähig

Cloudflare → Gateway - Funktionsfähig

Cloudflare → Network - Beeinträchtigte Leistung

Cloudflare → Pages - Funktionsfähig

Discord → API - Funktionsfähig

Discord → Gateway - Funktionsfähig

Github → Actions - Funktionsfähig

Github → API Requests - Funktionsfähig

Github → Git Operations - Funktionsfähig

Github → Issues - Funktionsfähig

Github → Pull Requests - Funktionsfähig

Github → Webhooks - Funktionsfähig

Ionos → Cloud Backup - Funktionsfähig

Ionos → Cloud Server - Funktionsfähig

Stripe → Stripe API - Funktionsfähig

Vercel → Baut - Funktionsfähig

Vercel → Build & Deploy - Funktionsfähig

Vercel → DNS - Funktionsfähig

Geschichte beachten

Juli 2025

Diesen Monat wurden keine Benachrichtigungen gemeldet

Juni 2025

Server Downtime
  • Nach dem Tod
    Nach dem Tod

    📝 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.

  • Gelöst
    Gelöst
    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.

  • Identifizierung
    Identifizierung

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

Mai 2025

Mai 2025 zu Juli 2025

Nächste