Yembo Status

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)

Resolved: Yembo's underlying infra has recovered. We will be closing the incident, but if any questions come up please feel free to contact our support team via [email protected].

Per Yembo's ISO 27001 incident response policy, our engineering team will review AWS' Incident Report when it become available for potential recommended remediations or product updates that can be made.

Monitoring: AWS expects backlogged recovery to complete within the next two hours. We're continuing to monitor.

Monitoring: AWS has downgraded the severity from Degraded to Impacted. We are continuing to monitor the recovery.

Monitoring: Our monitoring shows more servers are becoming available as needed, which is an encouraging recovery sign.

Additionally, Yembo's workaround is working as expected from our monitoring. We recommend hard reloading (CTRL + F5 on Windows, Cmd + Shift + R on Mac) to force your browser to load the latest version without waiting for the update checker.

We will continue to monitor as further updates come in.

Monitoring: AWS' fix is rolling out. Additionally, Yembo has deployed a workaround that reduces dependency on the intermittent subsystem. We are continuing to monitor the recovery.

More Smart Consults should work smoothly as a result of this.

Official AWS status: https://health.aws.amazon.com/health/status

Monitoring: AWS has confirmed they are "in the process of validating a fix" with the next update expected at 10:45am PDT.

We continue to monitor and see through Smart Consults as they come through. Our support team has also found https://downdetector.com/status/aws-amazon-web-services/ to be a useful source of realtime information in between official AWS communication.

Monitoring: Yembo has identified that the AWS incident is causing slow snapshots and delays in recording availability in Smart Consult in our US-hosted data center. We are not seeing evidence of degradation in the Canada, European, or Asia Pacific data centers.

If your Smart Consult snapshot is slow, you can continue to have the call, and the video recording will be batch uploaded into Yembo when AWS capacity comes back online.

AWS has begun remediation and commiunicated their next update is expected at 10:00am PDT. Yembo will update this page after that next update.

Please continue to work with your support rep if you require specific help during this incident.

Monitoring: We are monitoring the ongoing incidents with AWS (us-east-1 region). At this time, Yembo services are operational, and we are not observing systematic degradation in our platform.

Our engineering team remains in heightened monitoring mode while AWS and other affected vendors continue to recover.

We are monitoring the following incidents:

• AWS: https://health.aws.amazon.com/health/status
• Atlassian: https://jira-software.status.atlassian.com/incidents/wh0w6jjt6g5l
• Twilio: https://status.twilio.com
• MongoDB: https://status.mongodb.com/incidents/2m8d6qr3h3nr

Should you need any support, please feel free to contact us via [email protected] (for the moving product) and [email protected] (for the insurance product)