All systems are operational.

3 months ago —
Fixed

Fixed

3 months ago —

After continued monitoring for over an hour, we observed error rates returning to normal levels.

Root Cause

The outage was caused by SRV DNS queries failing to resolve via both the primary DNS provider and our first fallback solution. The fallback method relies on a separate DNS resolution approach (not simply a secondary DNS server). During the incident, that external service was also unavailable, which caused resolution failures across both mechanisms.

Mitigation & Fix

We successfully failed over to a third, independent fallback solution, which restored service stability.

To prevent similar issues in the future, we have:

  • Added a second independent external API to increase redundancy at that layer.
  • Automated the failover process to the third fallback solution to ensure faster recovery if similar conditions occur again.

The automation update is currently rolling out. We remain committed to improving resilience and preventing outages like this in the future.

Watching

3 months ago —

We have identified the issue and have taken action. The issue was caused by a problem with upstream infrastructure. We have implemented temporary routing changes to avoid this issue. Error rates are now decreasing, and we are continuing to monitor the situation.

3 months ago —

Bots are currently experiencing issues connecting to Minecraft servers. We are investigating the problem.

Incident UUID f0f63fd0-dc36-45f7-84b3-0b8a164061fb