Jomablue Status - Incident history https://jomablue.instatus.com Jomablue Mon, 23 Feb 2026 05:05:00 +0000 Google Wallet Passes not available on e-Tickets Type: Incident Duration: 19 hours and 54 minutes Affected Components: Registration Feb 23, 05:05:00 GMT+0 - Identified - Some end-users are seeing errors when attempting to add Google Wallet Passes to their Google Wallet. We have identified the cause and are working to resolve. Feb 23, 16:33:00 GMT+0 - Identified - We have identified that issues Google Wallet Passes are failing due to a upstream Google verification restriction - while we're not yet clear on why the restriction has been put in place - We have provided the necessary requirements to Google and continue to work with them to expedite the approval. e-Tickets remain operational, this is specific to adding e-Tickets to a users Wallet. Feb 24, 00:59:24 GMT+0 - Resolved - This incident has been resolved. Our team is working with Google Wallet contacts to understand how preventive measures can be put in place to prevent similar required approvals from happening in the future. Type: Incident

Duration: 19 hours and 54 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>05:05:00</var> GMT+0</small><br><strong>Identified</strong> - Some end-users are seeing errors when attempting to add Google Wallet Passes to their Google Wallet. We have identified the cause and are working to resolve. .</p> <p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>16:33:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified that issues Google Wallet Passes are failing due to a upstream Google verification restriction - while we're not yet clear on why the restriction has been put in place - We have provided the necessary requirements to Google and continue to work with them to expedite the approval. e-Tickets remain operational, this is specific to adding e-Tickets to a users Wallet. .</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>00:59:24</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Our team is working with Google Wallet contacts to understand how preventive measures can be put in place to prevent similar required approvals from happening in the future. .</p> ]]> Mon, 23 Feb 2026 05:05:00 +0000 https://jomablue.instatus.com/incident/cmlyz2d1800oq13gu1tuzviw1 https://jomablue.instatus.com/incident/cmlyz2d1800oq13gu1tuzviw1 Video Tables Retirement Type: Maintenance Duration: 1 minute Affected Components: Community Dec 14, 22:00:00 GMT+0 - Identified - Video tables will be retired on 15 December 2025 - After this date it will no longer be available in the product. If you currently rely on video tables, need help or have questions about alternatives, our team is here to support you. Dec 14, 22:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 14, 22:01:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 minute

Affected Components:

<p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br><strong>Identified</strong> - Video tables will be retired on 15 December 2025 - After this date it will no longer be available in the product. If you currently rely on video tables, need help or have questions about alternatives, our team is here to support you..</p> <p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>22:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>22:01:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sun, 14 Dec 2025 22:00:00 +0000 https://jomablue.instatus.com/maintenance/cmi2f9y6p00fdsk9fa2tk2jf0 https://jomablue.instatus.com/maintenance/cmi2f9y6p00fdsk9fa2tk2jf0 Platform Authentication and Registration Sites Failing to Load Type: Incident Duration: 1 hour and 55 minutes Affected Components: Registration, CX, Live Streaming/Video, Portal, , Kiosk, Community, Capture, Platform → Nov 21, 05:55:13 GMT+0 - Investigating - We are currently investigating this incident. Nov 22, 07:55:00 GMT+0 - Postmortem - During an update to a subset of customer instances, a configuration error in the deployment process caused some environments to become temporarily unavailable. This resulted in affected instances being unable to load or operate as expected. Once the issue was identified, we halted the rollout and began restoring each impacted instance. Most environments were corrected quickly and all were fully restored. Our deployment process requires multiple automated and manual human verification steps to avoid situations like this, in this particular case - the third party interface we use to orchestrate deployments was misrepresenting the deployment configuration. We’ve since updated our deployment process to revoke and completely avoid this configuration issue from occurring again, and we’ve added additional monitoring that will alert us immediately if a similar condition is ever detected. Nov 21, 05:59:54 GMT+0 - Identified - We are continuing to resolve the incident, services are restoring. Nov 21, 07:37:06 GMT+0 - Monitoring - We have addressed the cause and are currently monitoring the result. More details regarding the incident will be published in due course. Nov 21, 07:50:19 GMT+0 - Resolved - This incident has been resolved. A post mortem will be provided here in due course. Type: Incident

Duration: 1 hour and 55 minutes

Affected Components: , , , , , , ,

<p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>05:55:13</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Nov <var data-var='date'> 22</var>, <var data-var='time'>07:55:00</var> GMT+0</small><br><strong>Postmortem</strong> - During an update to a subset of customer instances, a configuration error in the deployment process caused some environments to become temporarily unavailable. This resulted in affected instances being unable to load or operate as expected. Once the issue was identified, we halted the rollout and began restoring each impacted instance. Most environments were corrected quickly and all were fully restored. Our deployment process requires multiple automated and manual human verification steps to avoid situations like this, in this particular case - the third party interface we use to orchestrate deployments was misrepresenting the deployment configuration. We’ve since updated our deployment process to revoke and completely avoid this configuration issue from occurring again, and we’ve added additional monitoring that will alert us immediately if a similar condition is ever detected. .</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>05:59:54</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to resolve the incident, services are restoring. .</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>07:37:06</var> GMT+0</small><br><strong>Monitoring</strong> - We have addressed the cause and are currently monitoring the result. More details regarding the incident will be published in due course. .</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>07:50:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. A post mortem will be provided here in due course. .</p> ]]> Fri, 21 Nov 2025 05:55:13 +0000 https://jomablue.instatus.com/incident/cmi8g4org00fju4f7ropx0kwq https://jomablue.instatus.com/incident/cmi8g4org00fju4f7ropx0kwq SMS's Failing to Send Type: Incident Duration: 5 hours and 58 minutes Affected Components: SMS Sending Nov 22, 06:49:00 GMT+0 - Postmortem - Our upstream SMS provider temporarily paused outbound SMS delivery after detecting unusual traffic affecting a subset of US numbers. As a result, SMS messages sent from Jomablue were not processed during this period. Once we became aware of the interruption, we rotated all SMS-related credentials as a precaution and worked with our provider to resume normal operation. SMS sending was unavailable while this rotation was in progress, but service has since been fully restored. Nov 21, 07:49:36 GMT+0 - Resolved - This incident has been resolved. A post mortem will be made available here in due course. Nov 21, 01:51:55 GMT+0 - Investigating - We are currently investigating SMS's failing to send from Jomablue. Nov 21, 04:16:45 GMT+0 - Identified - We have identified the cause and are bringing SMS services back online. Nov 21, 05:46:53 GMT+0 - Monitoring - We had addressed the cause, SMS sending has resumed and we are currently monitoring the result. We will provide more information in due course. Type: Incident

Duration: 5 hours and 58 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 22</var>, <var data-var='time'>06:49:00</var> GMT+0</small><br><strong>Postmortem</strong> - Our upstream SMS provider temporarily paused outbound SMS delivery after detecting unusual traffic affecting a subset of US numbers. As a result, SMS messages sent from Jomablue were not processed during this period. Once we became aware of the interruption, we rotated all SMS-related credentials as a precaution and worked with our provider to resume normal operation. SMS sending was unavailable while this rotation was in progress, but service has since been fully restored..</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>07:49:36</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. A post mortem will be made available here in due course. .</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>01:51:55</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating SMS's failing to send from Jomablue..</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>04:16:45</var> GMT+0</small><br><strong>Identified</strong> - We have identified the cause and are bringing SMS services back online. .</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>05:46:53</var> GMT+0</small><br><strong>Monitoring</strong> - We had addressed the cause, SMS sending has resumed and we are currently monitoring the result. We will provide more information in due course. .</p> ]]> Fri, 21 Nov 2025 01:51:55 +0000 https://jomablue.instatus.com/incident/cmi87fsus00k2n6b9jcllt76p https://jomablue.instatus.com/incident/cmi87fsus00k2n6b9jcllt76p Sporadic Camera Permission Issue using Capture App on Google Pixel Phones Type: Incident Duration: 2 days, 10 hours and 42 minutes Affected Components: Capture Oct 7, 12:30:00 GMT+0 - Investigating - We are currently investigating this incident. We are aware that some Google Pixel users are experiencing a camera permission issue when using Jomablue Capture. Our team is working to identify the cause. Oct 9, 06:51:40 GMT+0 - Identified - We believe we have identified the cause and are implementing a workaround and additional handing for Capture App to improve the reliability of camera launching on Pixel devices. Oct 9, 23:11:52 GMT+0 - Resolved - We have implemented some changes in Capture app to better support Pixel devices and their permission management. Please ensure the latest version is downloaded from the Play or App stores. Type: Incident

Duration: 2 days, 10 hours and 42 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. We are aware that some Google Pixel users are experiencing a camera permission issue when using Jomablue Capture. Our team is working to identify the cause. .</p> <p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>06:51:40</var> GMT+0</small><br><strong>Identified</strong> - We believe we have identified the cause and are implementing a workaround and additional handing for Capture App to improve the reliability of camera launching on Pixel devices. .</p> <p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>23:11:52</var> GMT+0</small><br><strong>Resolved</strong> - We have implemented some changes in Capture app to better support Pixel devices and their permission management. Please ensure the latest version is downloaded from the Play or App stores. .</p> ]]> Tue, 7 Oct 2025 12:30:00 +0000 https://jomablue.instatus.com/incident/cmgirs25o0b3383x8t193sone https://jomablue.instatus.com/incident/cmgirs25o0b3383x8t193sone Email Template and Pages Editor Maintenance Type: Maintenance Duration: 1 hour Affected Components: Portal Sep 24, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 24, 07:00:00 GMT+0 - Identified - We are planning maintenance on our Email Template and Pages drag-and-drop editor. For one hour the editor will be unavailable. Existing email templates will be unaffected which includes templates created and attached to campaigns. Sep 24, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

Affected Components:

<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning maintenance on our Email Template and Pages drag-and-drop editor. For one hour the editor will be unavailable. Existing email templates will be unaffected which includes templates created and attached to campaigns. .</p> <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Wed, 24 Sep 2025 07:00:00 +0000 https://jomablue.instatus.com/maintenance/cmfx77p3f0043gbqdk1v8i8a9 https://jomablue.instatus.com/maintenance/cmfx77p3f0043gbqdk1v8i8a9 Issue adding e-Tickets to Apple Wallet Type: Incident Duration: 2 days, 4 hours and 34 minutes Affected Components: Registration Sep 17, 21:53:05 GMT+0 - Investigating - We are currently investigating this incident that affects some e-Ticket recipients. These users are unable to add the e-Ticket to their Apple wallet on iPhones. The e-Ticket still remains functional and can be used for admittance to events - this is specific to adding that to Apple Wallet. Will will continue to update here as new information comes to hand. Sep 18, 02:27:08 GMT+0 - Identified - We have identified the cause and are working on a change. We will provide some more information in the next update. Sep 20, 02:27:00 GMT+0 - Resolved - This incident has been resolved. While there were three seperate issues, only a subset of users - in very specific scenarios that would have been affected by this issue. There were a number of issues affecting adding the e-Tickets to Apple wallet for a subset of users. Firstly, there was an encoding issue with non-latin based characters and the handling of them within the Apple wallet pass - specifically around two byte characters. This has been resolved. Secondly, adding e-Tickets to the Apple wallet from Slack's in-app web browser would fail. We found no specific evidence why link handling has changed within Slack's in-app browser but have evidence it has - we have resolved this by changing handling of the 'Adding to Wallet' functionality to continue to support in-app browsers. Finally, we uncovered that for iOS users with hundreds of Safari tabs open - there is not resources for the device/browser to process the generation and adding of the pass to the wallet. This is some undocumented limitation, but from our testing, exceeding hundreds of tabs would cause the adding of the pass to the wallet to silently fail. Reducing the number of tabs in Safari would resolve the issue. Type: Incident

Duration: 2 days, 4 hours and 34 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>21:53:05</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident that affects some e-Ticket recipients. These users are unable to add the e-Ticket to their Apple wallet on iPhones. The e-Ticket still remains functional and can be used for admittance to events - this is specific to adding that to Apple Wallet. Will will continue to update here as new information comes to hand. .</p> <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>02:27:08</var> GMT+0</small><br><strong>Identified</strong> - We have identified the cause and are working on a change. We will provide some more information in the next update. .</p> <p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>02:27:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. While there were three seperate issues, only a subset of users - in very specific scenarios that would have been affected by this issue. There were a number of issues affecting adding the e-Tickets to Apple wallet for a subset of users. Firstly, there was an encoding issue with non-latin based characters and the handling of them within the Apple wallet pass - specifically around two byte characters. This has been resolved. Secondly, adding e-Tickets to the Apple wallet from Slack's in-app web browser would fail. We found no specific evidence why link handling has changed within Slack's in-app browser but have evidence it has - we have resolved this by changing handling of the 'Adding to Wallet' functionality to continue to support in-app browsers. Finally, we uncovered that for iOS users with hundreds of Safari tabs open - there is not resources for the device/browser to process the generation and adding of the pass to the wallet. This is some undocumented limitation, but from our testing, exceeding hundreds of tabs would cause the adding of the pass to the wallet to silently fail. Reducing the number of tabs in Safari would resolve the issue. .</p> ]]> Wed, 17 Sep 2025 21:53:05 +0000 https://jomablue.instatus.com/incident/cmfoiq4su00gf82ym9hjiibqw https://jomablue.instatus.com/incident/cmfoiq4su00gf82ym9hjiibqw Email Delivery Delays Type: Incident Duration: 3 hours and 54 minutes Affected Components: Email Sending Sep 5, 03:57:00 GMT+0 - Investigating - We are currently investigating delayed delivery of emails. We will continue to post updates here as more information comes to hand. Sep 5, 05:14:21 GMT+0 - Identified - We have identified an issue with an upstream provider for specific email queues. We have escalated the issue and are working with the upstream provider to resolve. Jomablue emails are split between Transitional and Broadcast/Marketing emails automatically ensuring high delivery rates across all your email communications. In this particular case, the Broadcast/Marketing emails are affected but transactional emails - such as for invoices, OTP's etc remain unaffected. We will continue to update here as we learn more and work towards a resolution with our upstream provider. Sep 5, 07:51:10 GMT+0 - Resolved - This has been resolved, all pending emails were queued and now have been delivered. We are working with the upstream provider to produce a autopsy and ensure we can consider how Jomablue can be more resilient to such upstream provider issue. If you have any further questions we can answer them, just reach out to support. Type: Incident

Duration: 3 hours and 54 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>03:57:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating delayed delivery of emails. We will continue to post updates here as more information comes to hand. .</p> <p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>05:14:21</var> GMT+0</small><br><strong>Identified</strong> - We have identified an issue with an upstream provider for specific email queues. We have escalated the issue and are working with the upstream provider to resolve. Jomablue emails are split between Transitional and Broadcast/Marketing emails automatically ensuring high delivery rates across all your email communications. In this particular case, the Broadcast/Marketing emails are affected but transactional emails - such as for invoices, OTP's etc remain unaffected. We will continue to update here as we learn more and work towards a resolution with our upstream provider. .</p> <p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>07:51:10</var> GMT+0</small><br><strong>Resolved</strong> - This has been resolved, all pending emails were queued and now have been delivered. We are working with the upstream provider to produce a autopsy and ensure we can consider how Jomablue can be more resilient to such upstream provider issue. If you have any further questions we can answer them, just reach out to support. .</p> ]]> Fri, 5 Sep 2025 03:57:00 +0000 https://jomablue.instatus.com/incident/cmf6b02qb001dexgj5900prdy https://jomablue.instatus.com/incident/cmf6b02qb001dexgj5900prdy Delayed Email Delivery Type: Incident Duration: 6 days and 2 minutes Affected Components: Email Sending May 9, 00:07:50 GMT+0 - Investigating - We are currently investigating reports of delayed delivery of Emails. May 9, 02:13:09 GMT+0 - Identified - We have identified that some emails send from Jomablue have taken days to deliver. While Jomablue sent the email immediately from our infrastructure, the emails appear to be held and delayed upstream with a majority of them being delivered within the last 4 hours of this notice. We continue to investigate the impact as well as have escalated the issue with an upstream provider. We recognise the time sensitive nature of emails sent from Jomablue and always endeavour to maintain an well above average delivery times, in this case something upstream that we don't have visibility on has delayed those deliveries. Once we understand the issue from our upstream provider, we will be working to provide us more visibility and control to prevent future occurrences. May 12, 02:13:00 GMT+0 - Monitoring - We continue to seek responses from upstream providers regarding the delayed delivery. It remains our priority to understand why the delay. Email delivery times remain as expected and this remains an isolated incident. May 15, 00:10:01 GMT+0 - Resolved - We have confirmation from our upstream provider that this was an isolated incident and it has been resolved. While we are closing this incident report and we confirm that delivery times are still performant and as we expect - we are re-evaluating our upstream provider engagement to ensure they continue to align to the reliability and performance our customers expect from Jomablue. Type: Incident

Duration: 6 days and 2 minutes

Affected Components:

<p><small>May <var data-var='date'> 9</var>, <var data-var='time'>00:07:50</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating reports of delayed delivery of Emails..</p> <p><small>May <var data-var='date'> 9</var>, <var data-var='time'>02:13:09</var> GMT+0</small><br><strong>Identified</strong> - We have identified that some emails send from Jomablue have taken days to deliver. While Jomablue sent the email immediately from our infrastructure, the emails appear to be held and delayed upstream with a majority of them being delivered within the last 4 hours of this notice. We continue to investigate the impact as well as have escalated the issue with an upstream provider. We recognise the time sensitive nature of emails sent from Jomablue and always endeavour to maintain an well above average delivery times, in this case something upstream that we don't have visibility on has delayed those deliveries. Once we understand the issue from our upstream provider, we will be working to provide us more visibility and control to prevent future occurrences. .</p> <p><small>May <var data-var='date'> 12</var>, <var data-var='time'>02:13:00</var> GMT+0</small><br><strong>Monitoring</strong> - We continue to seek responses from upstream providers regarding the delayed delivery. It remains our priority to understand why the delay. Email delivery times remain as expected and this remains an isolated incident. .</p> <p><small>May <var data-var='date'> 15</var>, <var data-var='time'>00:10:01</var> GMT+0</small><br><strong>Resolved</strong> - We have confirmation from our upstream provider that this was an isolated incident and it has been resolved. While we are closing this incident report and we confirm that delivery times are still performant and as we expect - we are re-evaluating our upstream provider engagement to ensure they continue to align to the reliability and performance our customers expect from Jomablue. .</p> ]]> Fri, 9 May 2025 00:07:50 +0000 https://jomablue.instatus.com/incident/cmag1ez4l001m3u8vttdtykoa https://jomablue.instatus.com/incident/cmag1ez4l001m3u8vttdtykoa [Upstream] Errors for some email recipients when accessing links via emails Type: Incident Duration: 3 days, 19 hours and 28 minutes Affected Components: Email Sending May 2, 06:55:00 GMT+0 - Identified - A very small subset of email campaign recipients are receiving a DNS error when following a link via the received email. We have identified the issue with an upstream provider and awaiting their immediate response. The issue appears to be related to DNS services in the European region. May 2, 18:49:10 GMT+0 - Identified - We continue to work with an upstream provider and are wait on them for a resolution. We are actively in communication with them and supporting them toward a resolution. May 3, 18:18:36 GMT+0 - Identified - We are still seeking a resolution from an upstream provider. We are constantly monitoring and requesting updates. May 5, 05:28:32 GMT+0 - Identified - We continue to wait for updates from upstream providers. The problem is identified as a issue with specific upstream DNS servers that affect some users. May 5, 22:01:54 GMT+0 - Monitoring - We have received an update that a fix has been deployed upstream and they are monitoring. Additionally, we are in discussions with the upstream provider regarding their time to resolution on this matter. We continue to seek more information from them. May 6, 02:23:03 GMT+0 - Resolved - This has been resolved, awaiting a post mortem form upstream supplier. The summary of the issue was that certain ISP's in the UK were domain blocking a tracking link used in emails, because it was a DNS level block, the redirection couldn't happen for users attempting to follow the email links if using that ISP. Type: Incident

Duration: 3 days, 19 hours and 28 minutes

Affected Components:

<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>06:55:00</var> GMT+0</small><br><strong>Identified</strong> - A very small subset of email campaign recipients are receiving a DNS error when following a link via the received email. We have identified the issue with an upstream provider and awaiting their immediate response. The issue appears to be related to DNS services in the European region. .</p> <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>18:49:10</var> GMT+0</small><br><strong>Identified</strong> - We continue to work with an upstream provider and are wait on them for a resolution. We are actively in communication with them and supporting them toward a resolution. .</p> <p><small>May <var data-var='date'> 3</var>, <var data-var='time'>18:18:36</var> GMT+0</small><br><strong>Identified</strong> - We are still seeking a resolution from an upstream provider. We are constantly monitoring and requesting updates. .</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>05:28:32</var> GMT+0</small><br><strong>Identified</strong> - We continue to wait for updates from upstream providers. The problem is identified as a issue with specific upstream DNS servers that affect some users. .</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>22:01:54</var> GMT+0</small><br><strong>Monitoring</strong> - We have received an update that a fix has been deployed upstream and they are monitoring. Additionally, we are in discussions with the upstream provider regarding their time to resolution on this matter. We continue to seek more information from them. .</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>02:23:03</var> GMT+0</small><br><strong>Resolved</strong> - This has been resolved, awaiting a post mortem form upstream supplier. The summary of the issue was that certain ISP's in the UK were domain blocking a tracking link used in emails, because it was a DNS level block, the redirection couldn't happen for users attempting to follow the email links if using that ISP. .</p> ]]> Fri, 2 May 2025 06:55:00 +0000 https://jomablue.instatus.com/incident/cma6m98or000213kr6yubifyy https://jomablue.instatus.com/incident/cma6m98or000213kr6yubifyy Credit Card Checkout Errors for some users Type: Incident Duration: 51 minutes Affected Components: Registration Oct 13, 23:03:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 13, 23:40:26 GMT+0 - Monitoring - The incident has been resolved. A post mortem will be provided in due course. Oct 13, 23:53:37 GMT+0 - Resolved - 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. Type: Incident

Duration: 51 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>23:03:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>23:40:26</var> GMT+0</small><br><strong>Monitoring</strong> - The incident has been resolved. A post mortem will be provided in due course. .</p> <p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>23:53:37</var> GMT+0</small><br><strong>Resolved</strong> - 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. .</p> ]]> Sun, 13 Oct 2024 23:03:00 +0000 https://jomablue.instatus.com/incident/cm287w6xq00fb127a8b32nxpl https://jomablue.instatus.com/incident/cm287w6xq00fb127a8b32nxpl Unresponsive Services for some customers from some regions Type: Incident Duration: 2 hours and 49 minutes Affected Components: Live Streaming/Video, Push API, Community, CX, Registration, Portal, Kiosk, Capture, Data Warehouse Connector, Bulk Import API, Public API, Email Sending, SMS Sending Sep 12, 01:56:03 GMT+0 - Investigating - We are currently investigating an incident that is causing unresponsive services and timeouts. Sep 12, 02:21:26 GMT+0 - Investigating - 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. Sep 12, 02:57:48 GMT+0 - Investigating - Service response times are back to normal, but we continue to investigate the root cause. Sep 12, 04:45:20 GMT+0 - Resolved - Thank you for your patience while we worked through this issue. Services are now restored. Sep 25, 10:00:23 GMT+0 - Resolved - 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. Type: Incident

Duration: 2 hours and 49 minutes

Affected Components: , , , , , , , , , , , ,

<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>01:56:03</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an incident that is causing unresponsive services and timeouts. .</p> <p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>02:21:26</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>02:57:48</var> GMT+0</small><br><strong>Investigating</strong> - Service response times are back to normal, but we continue to investigate the root cause. .</p> <p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>04:45:20</var> GMT+0</small><br><strong>Resolved</strong> - Thank you for your patience while we worked through this issue. Services are now restored..</p> <p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>10:00:23</var> GMT+0</small><br><strong>Resolved</strong> - 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. .</p> ]]> Thu, 12 Sep 2024 01:56:03 +0000 https://jomablue.instatus.com/incident/cm0yn1lca007r5z1dz7ep8yb0 https://jomablue.instatus.com/incident/cm0yn1lca007r5z1dz7ep8yb0 Email Template images appear broken in the preview Type: Incident Duration: 3 days, 6 hours and 6 minutes Affected Components: Portal Jun 25, 03:27:00 GMT+0 - Identified - We are aware and have identified a cause of broken images appearing in the portal email preview. This is due to a security configuration within Jomablue performing as expected due to a change from an upstream hosting provider. We are working on a fix. Jun 26, 09:33:17 GMT+0 - Identified - We have confirmation from our upstream provider of an unexpected change that has caused this issue. We continue to work on a fix and expect to have this resoled in appox 24hrs. Jun 28, 09:33:00 GMT+0 - Resolved - This incident has been resolved, all customers will see the fix for broken images in the Email preview rollout over the next few days. Type: Incident

Duration: 3 days, 6 hours and 6 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>03:27:00</var> GMT+0</small><br><strong>Identified</strong> - We are aware and have identified a cause of broken images appearing in the portal email preview. This is due to a security configuration within Jomablue performing as expected due to a change from an upstream hosting provider. We are working on a fix. .</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>09:33:17</var> GMT+0</small><br><strong>Identified</strong> - We have confirmation from our upstream provider of an unexpected change that has caused this issue. We continue to work on a fix and expect to have this resoled in appox 24hrs. .</p> <p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>09:33:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved, all customers will see the fix for broken images in the Email preview rollout over the next few days. .</p> ]]> Tue, 25 Jun 2024 03:27:00 +0000 https://jomablue.instatus.com/incident/clxuafuc59328ben4n0upx2kv https://jomablue.instatus.com/incident/clxuafuc59328ben4n0upx2kv Email Delivery Delays Type: Incident Duration: 2 hours and 15 minutes Affected Components: Email Sending Jun 17, 18:08:00 GMT+0 - Identified - Outbound emails are currently being queued for delivery - causing a delay in them reaching inboxes. The queueing is happening upstream of Jomablue and we are working with an upstream provider to restore expected delivery times. No messages have been lost and will be sent. Jun 17, 20:23:00 GMT+0 - Resolved - This incident has been resolved. All queued messages have now been sent and delivery times have returned to normal. Type: Incident

Duration: 2 hours and 15 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>18:08:00</var> GMT+0</small><br><strong>Identified</strong> - Outbound emails are currently being queued for delivery - causing a delay in them reaching inboxes. The queueing is happening upstream of Jomablue and we are working with an upstream provider to restore expected delivery times. No messages have been lost and will be sent. .</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>20:23:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. All queued messages have now been sent and delivery times have returned to normal. .</p> ]]> Mon, 17 Jun 2024 18:08:00 +0000 https://jomablue.instatus.com/incident/clxjn8b3q83008awooz1p72z51 https://jomablue.instatus.com/incident/clxjn8b3q83008awooz1p72z51 SMS Processing Delays Type: Incident Duration: 1 hour and 46 minutes Affected Components: SMS Sending Jan 30, 06:13:49 GMT+0 - Identified - We are aware of a SMS processing delay at an upstream provider, resulting in delayed SMS delivery. At this stage we understand SMS's are being queued with the upstream provider and will be delivered as their services are restored. We will continue to monitor the situation and provide updates here. Jan 30, 06:51:12 GMT+0 - Identified - Australia Telco Telstra have advised our upstream provider that there is currently a National issue with intermittent failures in sending and receiving SMS to/from their network handsets. This looks to affect only Australian Telstra customers, other carriers appear unaffected. Jan 30, 07:59:34 GMT+0 - Resolved - We have been advised this incident has been resolved. SMS delivery times have returned to normal. Type: Incident

Duration: 1 hour and 46 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>06:13:49</var> GMT+0</small><br><strong>Identified</strong> - We are aware of a SMS processing delay at an upstream provider, resulting in delayed SMS delivery. At this stage we understand SMS's are being queued with the upstream provider and will be delivered as their services are restored. We will continue to monitor the situation and provide updates here. .</p> <p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>06:51:12</var> GMT+0</small><br><strong>Identified</strong> - Australia Telco Telstra have advised our upstream provider that there is currently a National issue with intermittent failures in sending and receiving SMS to/from their network handsets. This looks to affect only Australian Telstra customers, other carriers appear unaffected. .</p> <p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>07:59:34</var> GMT+0</small><br><strong>Resolved</strong> - We have been advised this incident has been resolved. SMS delivery times have returned to normal. .</p> ]]> Tue, 30 Jan 2024 06:13:49 +0000 https://jomablue.instatus.com/incident/clrzyqk1445240bdobdgy6rigj https://jomablue.instatus.com/incident/clrzyqk1445240bdobdgy6rigj Investigating Duplicate Campaigns being triggered Type: Incident Duration: 1 day, 8 hours and 20 minutes Affected Components: Email Sending, SMS Sending Aug 9, 21:09:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 10, 00:53:29 GMT+0 - Identified - We have identified the issue and are working on an immediate fix. Only a subset of customers are affected. Customers are welcome to use campaigns, but we're advising to stagger campaign schedule times by 5 minutes for campaigns that exceed 2000 recipients. This is a temporary soft limit while we continue to work to a resolution. A full summary will be provided in due course. Aug 9, 21:48:05 GMT+0 - Investigating - We continue to investigate the cause. Aug 10, 05:19:45 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. We expect resolution within the next few hours. Aug 10, 10:42:31 GMT+0 - Monitoring - We continue to monitor the results before marking as resolved. Expected resolution is now Friday morning AEDT. Aug 11, 01:23:59 GMT+0 - Monitoring - We're working on writing up the resolution now, the resolution will be available here shortly. Aug 11, 05:29:25 GMT+0 - Resolved - This has been resolved. The issue was due to an unforeseen case where processing a previously scheduled campaign, or a campaign scheduled at the exact same time as another larger campaign, would take much longer than expected to process (ie, minutes instead of seconds). While resources were allocated to process the first larger campaign, seperate campaign watchdogs (designed as a failsafe solution) would identify campaign that was scheduled for minutes ago has not yet been processed and would trigger their own campaign start procedure to ensure the send happened. The watchdogs would continue to do this until the first campaign send was completed. **What we have done to remedy this: ** We have identified the exact cause and have been able to replicate the issue within test environments. Using that we have implemented a fix that introduces a locking process to ensure the watchdogs don't interpret campaigns as 'not sent' when they're in fact processing and erroneously re-triggering the campaign. We have also reviewed and added additional processes and additional automated validation in our workflows to ensure this type of issue is not presented again. Type: Incident

Duration: 1 day, 8 hours and 20 minutes

Affected Components: ,

<p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>21:09:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>00:53:29</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue and are working on an immediate fix. Only a subset of customers are affected. Customers are welcome to use campaigns, but we're advising to stagger campaign schedule times by 5 minutes for campaigns that exceed 2000 recipients. This is a temporary soft limit while we continue to work to a resolution. A full summary will be provided in due course. .</p> <p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>21:48:05</var> GMT+0</small><br><strong>Investigating</strong> - We continue to investigate the cause. .</p> <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>05:19:45</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. We expect resolution within the next few hours. .</p> <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>10:42:31</var> GMT+0</small><br><strong>Monitoring</strong> - We continue to monitor the results before marking as resolved. Expected resolution is now Friday morning AEDT. .</p> <p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>01:23:59</var> GMT+0</small><br><strong>Monitoring</strong> - We're working on writing up the resolution now, the resolution will be available here shortly. .</p> <p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>05:29:25</var> GMT+0</small><br><strong>Resolved</strong> - This has been resolved. The issue was due to an unforeseen case where processing a previously scheduled campaign, or a campaign scheduled at the exact same time as another larger campaign, would take much longer than expected to process (ie, minutes instead of seconds). While resources were allocated to process the first larger campaign, seperate campaign watchdogs (designed as a failsafe solution) would identify campaign that was scheduled for minutes ago has not yet been processed and would trigger their own campaign start procedure to ensure the send happened. The watchdogs would continue to do this until the first campaign send was completed. **What we have done to remedy this: ** We have identified the exact cause and have been able to replicate the issue within test environments. Using that we have implemented a fix that introduces a locking process to ensure the watchdogs don't interpret campaigns as 'not sent' when they're in fact processing and erroneously re-triggering the campaign. We have also reviewed and added additional processes and additional automated validation in our workflows to ensure this type of issue is not presented again. .</p> ]]> Wed, 9 Aug 2023 21:09:00 +0000 https://jomablue.instatus.com/incident/cll48w70f24262bcn0iwckcrn9 https://jomablue.instatus.com/incident/cll48w70f24262bcn0iwckcrn9 Contract API Response Changes Type: Maintenance Duration: 10 minutes Affected Components: Push API Aug 4, 03:18:00 GMT+0 - Completed - Maintenance has completed successfully Aug 4, 02:18:01 GMT+0 - Identified - Maintenance is now in progress Aug 4, 02:18:00 GMT+0 - Identified - This change may affect customers using our Contract Validation API if logic is applied to the exact string that is returned for a failed API request. ### Affected Endpoint POST `/api/validate/payload` ### Summary of Changes: When a given payload fails validation the root level, the *message* key of the response to this endpoint will now return a dynamically generated summary of the validation errors instead of the fixed string `"The given data was invalid".` The summary includes the first failed validation rule message, and an indication of the number of additional error messages in parentheses if there are more than one. **Previous Message:** "message": "The given data was invalid.", **After planned change:** "message": "The generated at field is required. (and 14 more errors)", ### New Response Behaviour A message key contains a dynamically generated string in the format `"{first validation rule failure message} (and {n} more errors)"`. The errors key contains an object with keys matching each field which has failed validation and values. Each key has a value comprising an array of failed validation rule messages. (The errors key is unchanged). ``` `{ "message": "The generated at field is required. (and 14 more errors)", "errors": { "generated_at": [ "The generated at field is required." ], "identifiers.id": [ "The identifiers.id field is required." ], "data.name": [ "The data.name field is required." ], "data.start_time": [ "The data.start time field is required." ], "data.end_time": [ "The data.end time field is required." ], "data.short_description": [ "The data.short description field must be present." ], "data.description": [ "The data.description field must be present." ], "data.person_count_goal": [ "The data.person count goal field must be present." ], "data.venue_name": [ "The data.venue name field must be present." ], "data.venue_address": [ "The data.venue address field must be present." ], "data.timezone": [ "The data.timezone field must be present." ], "data.updated_at": [ "The data.updated at field is required." ], "data.created_at": [ "The data.created at field is required." ], "data.metadata": [ "The data.metadata field must be present." ], "data.categories": [ "The data.categories field must be present." ] } }` ``` Aug 4, 02:18:00 GMT+0 - Identified - We have revised the maintenance date. Type: Maintenance

Duration: 10 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>03:18:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>02:18:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>02:18:00</var> GMT+0</small><br><strong>Identified</strong> - This change may affect customers using our Contract Validation API if logic is applied to the exact string that is returned for a failed API request. ### Affected Endpoint POST `/api/validate/payload` ### Summary of Changes: When a given payload fails validation the root level, the *message* key of the response to this endpoint will now return a dynamically generated summary of the validation errors instead of the fixed string `"The given data was invalid".` The summary includes the first failed validation rule message, and an indication of the number of additional error messages in parentheses if there are more than one. **Previous Message:** "message": "The given data was invalid.", **After planned change:** "message": "The generated at field is required. (and 14 more errors)", ### New Response Behaviour A message key contains a dynamically generated string in the format `"{first validation rule failure message} (and {n} more errors)"`. The errors key contains an object with keys matching each field which has failed validation and values. Each key has a value comprising an array of failed validation rule messages. (The errors key is unchanged). ``` `{ "message": "The generated at field is required. (and 14 more errors)", "errors": { "generated_at": [ "The generated at field is required." ], "identifiers.id": [ "The identifiers.id field is required." ], "data.name": [ "The data.name field is required." ], "data.start_time": [ "The data.start time field is required." ], "data.end_time": [ "The data.end time field is required." ], "data.short_description": [ "The data.short description field must be present." ], "data.description": [ "The data.description field must be present." ], "data.person_count_goal": [ "The data.person count goal field must be present." ], "data.venue_name": [ "The data.venue name field must be present." ], "data.venue_address": [ "The data.venue address field must be present." ], "data.timezone": [ "The data.timezone field must be present." ], "data.updated_at": [ "The data.updated at field is required." ], "data.created_at": [ "The data.created at field is required." ], "data.metadata": [ "The data.metadata field must be present." ], "data.categories": [ "The data.categories field must be present." ] } }` ``` .</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>02:18:00</var> GMT+0</small><br><strong>Identified</strong> - We have revised the maintenance date. .</p> ]]> Fri, 4 Aug 2023 02:18:00 +0000 https://jomablue.instatus.com/maintenance/cljc8dumu111457belqjbacimjt https://jomablue.instatus.com/maintenance/cljc8dumu111457belqjbacimjt Planned Maintenance - Data Store Type: Maintenance Duration: 30 minutes Affected Components: Live Streaming/Video, Community, Push API, CX, Registration, Portal, Kiosk, Capture, Data Warehouse Connector, Bulk Import API, Public API, Email Sending, SMS Sending Jul 3, 11:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 3, 11:00:00 GMT+0 - Identified - We are planning for scheduled maintenance during this time as we will be performing necessary updates on data stores. While we don't expect any downtime, this notice is provided for transparency. If you have any concerns, please don't hesitate to reach out to our support desk or your account manager. Jul 3, 11:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 30 minutes

Affected Components: , , , , , , , , , , , ,

<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for scheduled maintenance during this time as we will be performing necessary updates on data stores. While we don't expect any downtime, this notice is provided for transparency. If you have any concerns, please don't hesitate to reach out to our support desk or your account manager. .</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 3 Jul 2023 11:00:00 +0000 https://jomablue.instatus.com/maintenance/cljm6yw5s54319bwocwmzcmxb7 https://jomablue.instatus.com/maintenance/cljm6yw5s54319bwocwmzcmxb7 Checkout Error for Addons Type: Incident Duration: 2 days, 4 hours and 50 minutes Affected Components: Registration Jun 19, 00:53:00 GMT+0 - Monitoring - We have identified a issue when attempting to checkout an Addon purchase. The issue relates to an overly aggressive security policy blocking the transactions which results in a validation error upon submitting billing details. We have made changes and are monitoring the result before rolling out the update. Existing or newly created addons will remain valid and can be checked out after resolution. We expect to resolve this within 48hrs. Jun 21, 05:42:35 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days, 4 hours and 50 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>00:53:00</var> GMT+0</small><br><strong>Monitoring</strong> - We have identified a issue when attempting to checkout an Addon purchase. The issue relates to an overly aggressive security policy blocking the transactions which results in a validation error upon submitting billing details. We have made changes and are monitoring the result before rolling out the update. Existing or newly created addons will remain valid and can be checked out after resolution. We expect to resolve this within 48hrs. .</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>05:42:35</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 19 Jun 2023 00:53:00 +0000 https://jomablue.instatus.com/incident/clj2h5fti103016bhobl0c38mni https://jomablue.instatus.com/incident/clj2h5fti103016bhobl0c38mni Jomablue CX failing to recognise eTickets Type: Incident Duration: 23 hours and 51 minutes Affected Components: Registration May 4, 22:27:00 GMT+0 - Investigating - We are currently investigating this incident. May 5, 22:18:00 GMT+0 - Resolved - This incident has been resolved and an iOS app store update has been published. The cause was due to the implementation of a new 'experience uid' qr code within the application that can be used in conjunction with Jomablue Kiosk and Jomablue Capture. The eTicket scanning function was applying incorrect validation when differentiating between an e-Ticket QR code and a experience UID QR code. We are reviewing our internal processes for improvement as well as ensuring test coverage across the affected components to prevent reoccurrence. Please ensure you update your CX app to the latest version available in the iOS app store. May 5, 00:12:00 GMT+0 - Identified - We have identified the cause and are working to implement a fix. May 5, 02:57:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result and publishing updates via iOS app store. Type: Incident

Duration: 23 hours and 51 minutes

Affected Components:

<p><small>May <var data-var='date'> 4</var>, <var data-var='time'>22:27:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>22:18:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved and an iOS app store update has been published. The cause was due to the implementation of a new 'experience uid' qr code within the application that can be used in conjunction with Jomablue Kiosk and Jomablue Capture. The eTicket scanning function was applying incorrect validation when differentiating between an e-Ticket QR code and a experience UID QR code. We are reviewing our internal processes for improvement as well as ensuring test coverage across the affected components to prevent reoccurrence. Please ensure you update your CX app to the latest version available in the iOS app store. .</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>00:12:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified the cause and are working to implement a fix. .</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>02:57:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result and publishing updates via iOS app store. .</p> ]]> Thu, 4 May 2023 22:27:00 +0000 https://jomablue.instatus.com/incident/clhb4pxdp41527gznjzn44rx3r https://jomablue.instatus.com/incident/clhb4pxdp41527gznjzn44rx3r Incorrect Date/Time displayed and campaigns being triggered early for NSW/VIC AU events Type: Incident Duration: 11 hours and 37 minutes Affected Components: Portal, Email Sending, SMS Sending Apr 2, 21:20:00 GMT+0 - Investigating - We are currently investigating this incident that causes campaigns schedule prior to Daylight Savings change on Sunday 2nd April, triggering an hour earlier than the scheduled time. Apr 2, 23:54:44 GMT+0 - Identified - We have identified that for Events configured in NSW/VIC Australia timezone, the ending of daylight savings was not recognised. This affects timestamps displayed within the product (appearing an hour ahead) as well as campaigns (they will be sent an hour early) and session start times. We are working on addressing the issue. Apr 3, 00:50:21 GMT+0 - Identified - We have identified the issue and are working on a priority fix. Apr 3, 01:37:19 GMT+0 - Identified - We have resolved the issue and are beginning rollout of a fix for the lack of adherence to the end of daylight savings time in NSW/VIC Australia. We will continue to provide updates here as we work towards resolving this. Apr 3, 04:28:32 GMT+0 - Monitoring - We continue to rollout the changes to all customers. Apr 3, 08:56:51 GMT+0 - Resolved - This incident has been resolved. The data we use to calculated timezone offsets and daylight savings lacked 2023 daylight savings information. The result was that Jomablue considered NSW/VIC, Australia as GMT+11 when it changed to GMT+10 less than 24hours ago. We have corrected the dataset, extended the dataset to year 2050 and corrected any incorrectly set times within Jomablue due to this incorrect offset. We ask customers to double check any time/date stamps that may have been created prior to 3rd April 2023, for events after 3rd April 2023 for certainty. If you have any concerns, please don't hesitate to reach out to support. Type: Incident

Duration: 11 hours and 37 minutes

Affected Components: , ,

<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>21:20:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident that causes campaigns schedule prior to Daylight Savings change on Sunday 2nd April, triggering an hour earlier than the scheduled time. .</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>23:54:44</var> GMT+0</small><br><strong>Identified</strong> - We have identified that for Events configured in NSW/VIC Australia timezone, the ending of daylight savings was not recognised. This affects timestamps displayed within the product (appearing an hour ahead) as well as campaigns (they will be sent an hour early) and session start times. We are working on addressing the issue. .</p> <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>00:50:21</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue and are working on a priority fix. .</p> <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>01:37:19</var> GMT+0</small><br><strong>Identified</strong> - We have resolved the issue and are beginning rollout of a fix for the lack of adherence to the end of daylight savings time in NSW/VIC Australia. We will continue to provide updates here as we work towards resolving this. .</p> <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>04:28:32</var> GMT+0</small><br><strong>Monitoring</strong> - We continue to rollout the changes to all customers. .</p> <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>08:56:51</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. The data we use to calculated timezone offsets and daylight savings lacked 2023 daylight savings information. The result was that Jomablue considered NSW/VIC, Australia as GMT+11 when it changed to GMT+10 less than 24hours ago. We have corrected the dataset, extended the dataset to year 2050 and corrected any incorrectly set times within Jomablue due to this incorrect offset. We ask customers to double check any time/date stamps that may have been created prior to 3rd April 2023, for events after 3rd April 2023 for certainty. If you have any concerns, please don't hesitate to reach out to support. .</p> ]]> Sun, 2 Apr 2023 21:20:00 +0000 https://jomablue.instatus.com/incident/clfzyv4up416116bboibz5mpfa8 https://jomablue.instatus.com/incident/clfzyv4up416116bboibz5mpfa8 Error displayed on viewing events list Type: Incident Duration: 2 hours and 16 minutes Affected Components: Portal Mar 15, 22:25:00 GMT+0 - Investigating - We are currently investigating this incident. It is a non-blocking error notification, you can continue to use Jomablue while we investigate the cause. Mar 15, 22:38:30 GMT+0 - Identified - We have identified the cause and are working on a resolution. Affected components include: - Viewing subscription information - Viewing and obtaining live stream recordings Mar 15, 23:10:12 GMT+0 - Monitoring - We have restored supporting services so the error notification no longer appears when loading the events list in the portal. We will continue to monitor for some time before resolving. Mar 16, 00:41:29 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 16 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>22:25:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. It is a non-blocking error notification, you can continue to use Jomablue while we investigate the cause. .</p> <p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>22:38:30</var> GMT+0</small><br><strong>Identified</strong> - We have identified the cause and are working on a resolution. Affected components include: - Viewing subscription information - Viewing and obtaining live stream recordings.</p> <p><small>Mar <var data-var='date'> 15</var>, <var data-var='time'>23:10:12</var> GMT+0</small><br><strong>Monitoring</strong> - We have restored supporting services so the error notification no longer appears when loading the events list in the portal. We will continue to monitor for some time before resolving. .</p> <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>00:41:29</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 15 Mar 2023 22:25:00 +0000 https://jomablue.instatus.com/incident/clfa95mrx81431dlmvpu815pti https://jomablue.instatus.com/incident/clfa95mrx81431dlmvpu815pti Inability to generate people exports under certain conditions Type: Incident Duration: 22 days and 12 hours Affected Components: Portal Feb 27, 07:16:00 GMT+0 - Resolved - This has been resolved. Type: Incident

Duration: 22 days and 12 hours

Affected Components:

<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>07:16:00</var> GMT+0</small><br><strong>Resolved</strong> - This has been resolved. .</p> ]]> Mon, 27 Feb 2023 07:16:00 +0000 https://jomablue.instatus.com/incident/clem0nnmq385700taot4qrxg3x8 https://jomablue.instatus.com/incident/clem0nnmq385700taot4qrxg3x8 Database Maintenance Type: Maintenance Duration: 3 hours Affected Components: Portal, Community, Live Streaming/Video, Registration, Data Warehouse Connector, Email Sending, SMS Sending, Bulk Import API, Public API Sep 17, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 17, 07:00:00 GMT+0 - Identified - We are working on migrating some backend data stores. No data will be lost during this time. During the Maintenance window, customers will be unable to access their instances for approx 30 mins. A Maintenance message will be displayed during the 30 mins. Sep 17, 10:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 3 hours

Affected Components: , , , , , , , ,

<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are working on migrating some backend data stores. No data will be lost during this time. During the Maintenance window, customers will be unable to access their instances for approx 30 mins. A Maintenance message will be displayed during the 30 mins. .</p> <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sat, 17 Sep 2022 07:00:00 +0000 https://jomablue.instatus.com/maintenance/cl83nyuci1831j9oq1ln32bq2 https://jomablue.instatus.com/maintenance/cl83nyuci1831j9oq1ln32bq2 SMS Delivery Delays [upstream provider delays] Type: Incident Duration: 47 minutes Affected Components: SMS Sending Sep 6, 01:02:00 GMT+0 - Identified - Our upstream provider has notified us that they're experiencing up to 20min delays in SMS delivery. We will continue to monitor the situation and provide updates as we learn more. Sep 6, 01:49:17 GMT+0 - Resolved - We have been notified and confirmed SMS's are now delivering within the expected timeframe. Type: Incident

Duration: 47 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>01:02:00</var> GMT+0</small><br><strong>Identified</strong> - Our upstream provider has notified us that they're experiencing up to 20min delays in SMS delivery. We will continue to monitor the situation and provide updates as we learn more. .</p> <p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>01:49:17</var> GMT+0</small><br><strong>Resolved</strong> - We have been notified and confirmed SMS's are now delivering within the expected timeframe. .</p> ]]> Tue, 6 Sep 2022 01:02:00 +0000 https://jomablue.instatus.com/incident/cl7piev1v0746hsoelczjtdj0 https://jomablue.instatus.com/incident/cl7piev1v0746hsoelczjtdj0 SMS delivery failures or delays [upstream provider outage] Type: Incident Duration: 19 days and 10 hours Affected Components: SMS Sending Sep 1, 16:13:00 GMT+0 - Identified - Our upstream service provider has confirmed SMS delivery failures or delays. We will continue to monitor the situation and provide updates here as we learn more. At this stage we recommend avoiding the use of SMS as we are yet to understand if these are being queued for delivery of dropped by our service provider. This affects OTP logins and SMS campaigns. For administrators recommend switching to App Based 2FA login to Jomablue to avoid the SMS delays. If not already setup and you can progress due the sms issue, please email Jomablue support for assistance. Sep 1, 23:42:05 GMT+0 - Monitoring - We continue to monitor for updates from our upstream providers. We are not seeing any improvements of services at this stage. Sep 1, 23:59:00 GMT+0 - Resolved - An update has been provided by our upstream provider, summarised below: - The issue has been identified and they are working on a resolution - They estimate a resolution in the next few hours - SMS’s are being queued For Jomablue users, you can expect to receive the SMS triggered from Jomablue over the last 6 hours when this has been resolved. This includes OTP’s or any campaign related SMS’s. It’s likely you will receive these all at once at that time. We will continue to monitor and provide updates here. Sep 2, 02:11:24 GMT+0 - Resolved - Our upstream provider has confirmed the backlog of queued SMS messages has been cleared/delivered. No messages were lost in the process. SMS sending from Jomablue how now returned to normal. Type: Incident

Duration: 19 days and 10 hours

Affected Components:

<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>16:13:00</var> GMT+0</small><br><strong>Identified</strong> - Our upstream service provider has confirmed SMS delivery failures or delays. We will continue to monitor the situation and provide updates here as we learn more. At this stage we recommend avoiding the use of SMS as we are yet to understand if these are being queued for delivery of dropped by our service provider. This affects OTP logins and SMS campaigns. For administrators recommend switching to App Based 2FA login to Jomablue to avoid the SMS delays. If not already setup and you can progress due the sms issue, please email Jomablue support for assistance. .</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>23:42:05</var> GMT+0</small><br><strong>Monitoring</strong> - We continue to monitor for updates from our upstream providers. We are not seeing any improvements of services at this stage. .</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>23:59:00</var> GMT+0</small><br><strong>Resolved</strong> - An update has been provided by our upstream provider, summarised below: - The issue has been identified and they are working on a resolution - They estimate a resolution in the next few hours - SMS’s are being queued For Jomablue users, you can expect to receive the SMS triggered from Jomablue over the last 6 hours when this has been resolved. This includes OTP’s or any campaign related SMS’s. It’s likely you will receive these all at once at that time. We will continue to monitor and provide updates here..</p> <p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>02:11:24</var> GMT+0</small><br><strong>Resolved</strong> - Our upstream provider has confirmed the backlog of queued SMS messages has been cleared/delivered. No messages were lost in the process. SMS sending from Jomablue how now returned to normal. .</p> ]]> Thu, 1 Sep 2022 16:13:00 +0000 https://jomablue.instatus.com/incident/cl7jkv1fi193975ogpog4tzef https://jomablue.instatus.com/incident/cl7jkv1fi193975ogpog4tzef Backend Database Maintenance Type: Maintenance Duration: 52 minutes Affected Components: Portal, Public API, Community, Live Streaming/Video, Registration, Data Warehouse Connector, Email Sending, SMS Sending Aug 2, 12:30:00 GMT+0 - Identified - Based on advice from our hosting provider AWS. We are migrating some customers away from particular AWS services. Aug 2, 13:22:23 GMT+0 - Completed - Maintenance has completed successfully. Aug 2, 12:30:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 52 minutes

Affected Components: , , , , , , ,

<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Identified</strong> - Based on advice from our hosting provider AWS. We are migrating some customers away from particular AWS services. .</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>13:22:23</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>12:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Tue, 2 Aug 2022 12:30:00 +0000 https://jomablue.instatus.com/maintenance/cl6c2azio48066unloi918ip3s https://jomablue.instatus.com/maintenance/cl6c2azio48066unloi918ip3s Backend Service Migration Type: Maintenance Duration: 3 hours and 24 minutes Affected Components: Portal, Registration, Community Jul 16, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 16, 07:00:00 GMT+0 - Identified - For less than 5% of customers their instances will be unavailable during this time while we migrate some infrastructure. This includes accessing portal, community and registration forms. If you have any questions you can reach us during this window at support@jomablue.com Jul 16, 10:23:37 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 3 hours and 24 minutes

Affected Components: , ,

<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - For less than 5% of customers their instances will be unavailable during this time while we migrate some infrastructure. This includes accessing portal, community and registration forms. If you have any questions you can reach us during this window at support@jomablue.com.</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>10:23:37</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Sat, 16 Jul 2022 07:00:00 +0000 https://jomablue.instatus.com/maintenance/cl5lrxabt0509lgnbr48pkobm https://jomablue.instatus.com/maintenance/cl5lrxabt0509lgnbr48pkobm Investigating possible hardware failure in a Sydney data centre Type: Incident Duration: 2 hours and 51 minutes Affected Components: Registration, Data Warehouse Connector, Live Streaming/Video, Portal, Public API, Community, Email Sending, SMS Sending Jun 21, 13:46:00 GMT+0 - Investigating - We are currently investigating this incident. Failover processes are underway. This may be affecting 1% of customers. Jun 21, 01:55:00 GMT+0 - Monitoring - Services have been restored, we are continuing to investigate the underlying cause with upstream service providers. Jun 21, 04:46:00 GMT+0 - Resolved - The issue is resolved. AWS confirmed an underlying hardware failure was the cause of this issue. Type: Incident

Duration: 2 hours and 51 minutes

Affected Components: , , , , , , ,

<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>13:46:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Failover processes are underway. This may be affecting 1% of customers. .</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>01:55:00</var> GMT+0</small><br><strong>Monitoring</strong> - Services have been restored, we are continuing to investigate the underlying cause with upstream service providers. .</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>04:46:00</var> GMT+0</small><br><strong>Resolved</strong> - The issue is resolved. AWS confirmed an underlying hardware failure was the cause of this issue. .</p> ]]> Tue, 21 Jun 2022 13:46:00 +0000 https://jomablue.instatus.com/incident/cl4njd51q11299n6n1h5uo9bs8 https://jomablue.instatus.com/incident/cl4njd51q11299n6n1h5uo9bs8 Delayed outbound Email sending to some providers Type: Incident Duration: 1 hour and 53 minutes Affected Components: Email Sending Feb 22, 00:50:27 GMT+0 - Identified - We have identified an upstream incident that has caused delays to Email delivery to some providers including Gmail, Hotmail, Yahoo and AOL. These delays can be in excess of 5 mins for delivery. We continue to seek updates from our upstream providers and are in the process of rerouting email queues. Feb 22, 01:55:15 GMT+0 - Monitoring - We continue to monitor upstream networks for improved delivery times and have rerouted some of our mail queues to improve email delivery performance for our customers. Feb 22, 02:43:16 GMT+0 - Resolved - Sending is back to normal. This was communicated by upstream networks and we have confirmed we are seeing normal delivery times for campaigns and transactional OTPs. Type: Incident

Duration: 1 hour and 53 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>00:50:27</var> GMT+0</small><br><strong>Identified</strong> - We have identified an upstream incident that has caused delays to Email delivery to some providers including Gmail, Hotmail, Yahoo and AOL. These delays can be in excess of 5 mins for delivery. We continue to seek updates from our upstream providers and are in the process of rerouting email queues. .</p> <p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>01:55:15</var> GMT+0</small><br><strong>Monitoring</strong> - We continue to monitor upstream networks for improved delivery times and have rerouted some of our mail queues to improve email delivery performance for our customers. .</p> <p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>02:43:16</var> GMT+0</small><br><strong>Resolved</strong> - Sending is back to normal. This was communicated by upstream networks and we have confirmed we are seeing normal delivery times for campaigns and transactional OTPs. .</p> ]]> Tue, 22 Feb 2022 00:50:27 +0000 https://jomablue.instatus.com/incident/ckzxevf4g69206efmtnpbjl83x https://jomablue.instatus.com/incident/ckzxevf4g69206efmtnpbjl83x Backend Services Migration Type: Maintenance Duration: 6 days, 19 hours and 10 minutes Affected Components: Registration, Email Sending, SMS Sending, Community, Data Warehouse Connector, Portal, Public API Jan 25, 03:24:14 GMT+0 - Completed - Maintenance has completed successfully. Jan 18, 08:14:43 GMT+0 - Identified - Within the following windows, for each customer Jomablue will not be accessible for a period of 90 minutes. Tuesday 18th Jan 2022 - Sunday 23rd Jan Between. 8:00pm - 11:00pm AEST (GMT+10) Jan 18, 09:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance for customers over the coming days. This is a normal procedure to migrate some of our backend services. As we are migrating customers in small batches to ensure success, we are allocating maintenance windows each night for the following remainder of the week. Within those windows your particular instance/account will only be affected for up to 90 minutes. During your allocated 90 minutes Jomablue will not be accessible. Tuesday 18th Jan 2022 - Sunday 23rd Jan Between. 8:00pm - 11:00pm AEST (GMT+10) Type: Maintenance

Duration: 6 days, 19 hours and 10 minutes

Affected Components: , , , , , ,

<p><small>Jan <var data-var='date'> 25</var>, <var data-var='time'>03:24:14</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>08:14:43</var> GMT+0</small><br><strong>Identified</strong> - Within the following windows, for each customer Jomablue will not be accessible for a period of 90 minutes. Tuesday 18th Jan 2022 - Sunday 23rd Jan Between. 8:00pm - 11:00pm AEST (GMT+10) .</p> <p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance for customers over the coming days. This is a normal procedure to migrate some of our backend services. As we are migrating customers in small batches to ensure success, we are allocating maintenance windows each night for the following remainder of the week. Within those windows your particular instance/account will only be affected for up to 90 minutes. During your allocated 90 minutes Jomablue will not be accessible. Tuesday 18th Jan 2022 - Sunday 23rd Jan Between. 8:00pm - 11:00pm AEST (GMT+10).</p> ]]> Tue, 18 Jan 2022 08:14:43 +0000 https://jomablue.instatus.com/maintenance/ckyjlrsj714123edo58mhthe8b https://jomablue.instatus.com/maintenance/ckyjlrsj714123edo58mhthe8b SMS Delivery Delays Type: Incident Duration: 13 minutes Affected Components: Portal, SMS Sending Dec 1, 22:25:47 GMT+0 - Investigating - We are currently investigating this incident with our upstream provider. This affects all SMS's (Including passcodes and SMS campaigns) Dec 1, 22:38:30 GMT+0 - Resolved - They have confirmed the issue was resolved and we are seeing expected latency and delivery times on our side. Dec 1, 22:37:35 GMT+0 - Identified - Our upstream SMS provider executed some unannounced and unplanned emergency maintenance causing API requests to timeout or fail. Type: Incident

Duration: 13 minutes

Affected Components: ,

<p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>22:25:47</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident with our upstream provider. This affects all SMS's (Including passcodes and SMS campaigns).</p> <p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>22:38:30</var> GMT+0</small><br><strong>Resolved</strong> - They have confirmed the issue was resolved and we are seeing expected latency and delivery times on our side. .</p> <p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>22:37:35</var> GMT+0</small><br><strong>Identified</strong> - Our upstream SMS provider executed some unannounced and unplanned emergency maintenance causing API requests to timeout or fail. .</p> ]]> Wed, 1 Dec 2021 22:25:47 +0000 https://jomablue.instatus.com/incident/ckwo3ljth1197888n7j2a0y2e4 https://jomablue.instatus.com/incident/ckwo3ljth1197888n7j2a0y2e4 Longer than expected Email Delivery Times for some customers Type: Incident Duration: 25 minutes Affected Components: Email Sending Sep 15, 08:19:00 GMT+0 - Identified - We have identified the upstream provider has throttled some outbound emails to review for spam or fraudulent emails. We are working with them to clear the email queue. Sep 15, 08:28:00 GMT+0 - Monitoring - Throttle removed and email queue is clearing rapidly. We will continue to monitor performance before marking this as resolved. Sep 15, 08:39:00 GMT+0 - Resolved - Email queue is clear and delivery rates are back to below 10 seconds. Sep 15, 08:14:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 25 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>08:19:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified the upstream provider has throttled some outbound emails to review for spam or fraudulent emails. We are working with them to clear the email queue. .</p> <p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>08:28:00</var> GMT+0</small><br><strong>Monitoring</strong> - Throttle removed and email queue is clearing rapidly. We will continue to monitor performance before marking this as resolved. .</p> <p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>08:39:00</var> GMT+0</small><br><strong>Resolved</strong> - Email queue is clear and delivery rates are back to below 10 seconds. .</p> <p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>08:14:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Wed, 15 Sep 2021 08:14:00 +0000 https://jomablue.instatus.com/incident/cktm5nkj2290986tlltxdgw5eri https://jomablue.instatus.com/incident/cktm5nkj2290986tlltxdgw5eri Planned Maintenance - Backend Services Upgrades Type: Maintenance Affected Components: Registration, Email Sending, SMS Sending, Community, Public API, Portal, Data Warehouse Connector Jun 12, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully. Jun 12, 08:30:00 GMT+0 - Identified - Maintenance is now in progress. During a 24-hour window, customers will experience up to 30mins of maintenance on their instance. Jun 12, 08:00:00 GMT+0 - Identified - Planned maintenance has been scheduled to perform some required infrastructure upgrades. This will affect all customer's instances for a period of approximately 30 minutes during the set maintenance window. During this 30 minute window no Jomablue services will be accessible. Type: Maintenance

Affected Components: , , , , , ,

<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress. During a 24-hour window, customers will experience up to 30mins of maintenance on their instance. .</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Identified</strong> - Planned maintenance has been scheduled to perform some required infrastructure upgrades. This will affect all customer's instances for a period of approximately 30 minutes during the set maintenance window. During this 30 minute window no Jomablue services will be accessible. .</p> ]]> Sat, 12 Jun 2021 08:00:00 +0000 https://jomablue.instatus.com/maintenance/ckpooq9y890523b4mya3gz407z https://jomablue.instatus.com/maintenance/ckpooq9y890523b4mya3gz407z