Wireguard peer down in Amsterdam?

You should be OK again. You’re catching the tail end of a migration we’re doing to a new system for managing WireGuard peers (as of tomorrow, it should take single-digit seconds to create and bring up WireGuard for a new peer, rather than 1.5 minutes).

I think you created and then deleted a peer, which snagged a corner case — I had a UNIQUE constraint on a sqlite column that the peer you’re talking about was hitting.

I’ve rolled back AMS to the old (slow) behavior (boo!) — it should be fine for you now.