exe.dev status

Due to a broken update, access to exe.dev was lost for about 12 minutes. This interrupted ssh to exe.dev, some Shelley and API access, and some website access.

We've fixed the underlying issues. Please e-mail support@exe.dev if need be.

A limited number of VMs are showing disk errors due to a broken upgrade. We are actively working to resolve the problem. At this point, if your VM isn't working, please run "ssh exe.dev restart <vm-name>" (or find the restart button in the VM detail page in the web UI). If that doesn't work, please e-mail support@exe.dev with the VM name.

We are currently monitoring the fix

A fix is currently being rolled out

A fix has been implemented and will be deployed with the next release.

We've identified an issue where a stale attached GitHub repository can cause github.int.exe.xyz clones for otherwise valid repos to fail. Users can re-grant or detach the stale GitHub repo integration while we prepare a fix

We're investigating an issue with some VMs not being able to communicate or refresh tokens from GitHub

We're actively migrating to new hardware across all regions.

One of our upstream providers entered a small maintenance window. During this time, customers may have experienced brief connectivity issues.

There was a temporary network issue with our upstream provider that caused some brief service interruption. It should be resolved.

We are investigating connectivity issues affecting a subset of VMs in the syd region.

Issue has been resolved.

We are experiencing an issue with a node that is affecting a subset of VMs in the pdx region.

Maintenance has completed.

We are performing maintenance in our LON region. Some VM connectivity may be interrupted for a short period.

Network issue in the upstream provider has been resolved. All systems are reporting healthy.

Our upstream provider has implemented a fix and is monitoring the results.

There is a network issue being investigated by our upstream provider.

We are investigating upstream connectivity issues for a subset of VMs in the nyc region.

Machine is back up. We're investigating outage cause.

The underlying issue has been fixed.

From 2026-06-20 17:32 UTC to 2026-06-20 20:06 UTC, ssh connections to exe.dev were timing out due to a bug. Connections to VMs at vm.exe.xyz continued to work. We are up now and are fixing the underlying cause.

The issue has been identified and resolved.

Network latency is resolved.

We're investigating increased ssh latency with our LAX region

Migration is now complete.

We are migrating to a new network mode that could cause some momentary connectivity issues for VMs.

Our provider has caught up.

Our outbound emails are significantly delayed.

The problem was a bad change that cause the CPU to peg on the proxy systems. We believe that this is now mitigated.

We're aware of SSH connections to exe.dev VMs. We're investigating.

All VMs are serving traffic (and have been for a while). We are leaving this incident open until we know definitively what data we will be able to rescue from the machine that we lost.

Status update. We lost a physical machine in Singapore. Our vendor is currently unresponsive. We have restored VMs from backups in order to get them running again. The data might be up to an hour old. If/when we are able to get access to the original server, we will make the contents at time of hardware failure available for download. We will update again when we have more updates.

Approximately 600 VMs are currently unreachable. We are investigating.

This is now resolved. Please let us know if you see any problems.

We had an issue that is causing some connectivity trouble for some VMs. Our services are designed to have a clean handoff of current state when they are updated. Unfortunately when rolling out a new instance an error caused some of the service state to remain with the old instance, rather than being transferred to the new one. An unrelated error caused the new instance to not behave properly. To fix these combined problems, we shut down both the old and new instances, and restarted the service from a rolled back version. This worked, but meant that the newly started instance no longer started with the state transferred from the old one. This made some VMs inaccessible in a few regions. The problem was fixed by synchronizing the full state in the new instance. Sincere apologies for the down time.

A network issue is causing VM connectivity issues for some number of VMs.

An upstream network issue is causing VM connectivity issues for a limited number of VMs.

We are having issues with our certificate registration that are causing connectivity and system availability. Update: we've identified the issue and mitigated on our side. The exe.dev service is now available however, due to an on-going issue with Let's Encrypt (https://letsencrypt.status.io/) custom domain certificate issuance may be delayed or have issues. Please reach out to support@exe.dev if you have trouble.

We are investigating an issue that could cause issues with starting or managing VMs on a small set of users.

We are investigating a network issue that is causing connection issues.

We are investigating an issue with one of our compute hosts that could impact VM availability.

We have identified an issue with TLS certificate generation for custom domains. Update: We've deployed the fix and the issue should be resolved.

A network error caused one of our compute hosts to have connectivity issues affecting a small subset of VMs. The compute host had to be restarted. All VMs are now back online.

Testing.