An underlying AWS networking issue with our primary database server has caused a complete API outage for a total duration of 10 minutes. Since the networking outage was only partial, it prevented secondary database members from stepping in to become the primary and continuing to serving requests as they have been able to connect, while the rest of the servers have not.
After 10 minutes of API downtime, the Pushy API is now back in working order. We apologize for any inconvenience this has had on your reliable notification delivery experience. Thanks for your patience and understanding as we worked to investigate and resolve this issue ASAP.
