Jomablue - Notice history

For customers using paid registration, if 'Manual Payment instructions' were not configured or provided as part of setup, the checkout process would display an error and block user progress at the point of checkout. This has been addressed and we are working to add clearer definition for event administrators to understand the requirements of this field.

The incident has been resolved. A post mortem will be provided in due course.

Since this incident, we have been working with our service provider, AWS, to identify the root cause of some of our services being unresponsive for some customers - which was dependent on their geographical location.

After Jomablue brought it to the attention of AWS and since the issue was reported, AWS support has undertaken a detailed analysis of the issue and confirmed it was due to an unexpected surge in traffic (external to Jomablue) through their Singapore and Sydney Cloudfront edge locations, which resulted in 98% error rates for periods throughout a 1 hour window.

We continue to work with AWS support to ensure that factors beyond our control do not impact the quality of service Jomablue delivers.

Thank you for your patience while we worked through this issue. Services are now restored.

Service response times are back to normal, but we continue to investigate the root cause.

Services remain sporadically unresponsive or slow, we continue to investigate.
At this stage it appears to be a localised/location based issue with routing traffic to ap-southeast-2 AWS region.