AWS experienced an issue within the region where the Spreedly application is deployed, which caused a disruption in outbound network traffic.

What Happened

Spreedly’s internal systems recognized communication issues with a number of gateways. Internal response teams immediately started to investigate the issue.  As a number of working theories were tested, it became clear that the communication issues were not limited to communication with gateways, but also between Spreedly systems within AWS.

As this correlation was discovered, more reports were cropping up with other users of AWS of network communication issues.   At that point, AWS posted an update on their status page regarding issues had been detected and they were working to resolve.

Prior to confirmation of resolution on the AWS status page, our internal systems showed signs of returning to normal.  This occurred twice in the span of two hours.

Next Steps

Spreedly has identified the following steps as actions to proactively alert our customers:

• Bolster monitoring and alerting mechanisms for external network communications.
• Provide more real-time notification via Status Page when the Spreedly team discovers evidence of service degradation.