Is Bettermode Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We have identified an issue with our search service in US region. The issue has been identified and we are working on a fix.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

The incident had been resolved. However, we are still closely monitoring the situation.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This has been resolved.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

Our email delivery system experienced a reduction in the rate of outgoing email deliveries. The root cause of this reduction in email delivery rate was identified and resolved.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

The US region community services experienced technical difficulties today from 19:34 UTC to 19:49. We have resolved the issue and all services are up now.

This issue has been resolved. There was a problem with our DNS provider that is resolved now. We will take the necessary actions to prevent these kinds of issues from happening again.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved now. The issue was with one of our web servers. It had a bug that was happening in an edge-case scenario, by upgrading the tool and patching a fix, it is working correctly now. The incident was just affecting communities on .tribeplatform.com and was happening randomly from time to time.

The root cause of the issue is still under investigation, we are still seeing that it is popping up from time to time and we are actively working on a solution to permanently fix the issue.

Communities are now accessible, but we are still investigating the root cause of the problem.

A fix has been implemented and we are monitoring the results.

Communities on `.tribeplatform.com` domain are inaccessible at the moment, we are investigating the issue.

This incident has been resolved.

We identified the issue and we are monitoring the fix.

The issue has been solved since 6:28 p.m. UTC, we are still investigating the root cause.

We are continuing to investigate this issue.

Sine 5:16 p.m. UTC there have been some random issues with community access, we are investigating the issue.

On October 13, 2023, we experienced a session issue affecting user access to our community platforms. Our monitoring systems, which automatically update our status page, did not detect this problem at first because our servers and main services were still okay. The issue was complicated, arising from a mix of updates over the past year that together led to this unexpected behavior. It took a special sequence of events to set off, making it hard to catch during our usual testing. After hearing from our users around 03:00 AM UTC, our engineering team acted swiftly to look into and correct the issue. Solving it was not straightforward; it demanded careful pinpointing of the problem areas within our backend systems. Despite the challenging nature of the issue, our team was able to fix it within a few hours, ensuring that services were back to normal. We understand the questions our customers may have about the late update on our status page. This delay happened because our automatic monitoring focuses on server health and common mistakes. This time, the distinct nature of the issue avoided these checks. In light of this incident, we are taking steps to improve our systems. These include: 1. Tweaking our automatic monitoring to catch a broader set of errors. 2. Adding new tools to make updates more reliable. 3. Improving our small-scale test releases to catch issues early before rolling out to everyone. 4. Enhancing our emergency response process to speed up problem-solving. We're dedicated to making our platforms reliable and secure. The lessons learned from this will help guide our future work and system enhancements. We deeply value your patience and understanding as we keep working to boost the dependability and experience of our platforms.

Starting on October 13, at 03:00 AM UTC, we experienced an issue affecting access to our communities. Users intermittently received "Community Not Found" or "Internal Server Error" messages when attempting to access their respective communities. Our team commenced an investigation into the issue at 03:30 AM UTC. A fix patch was deployed by 04:15 AM UTC on October 13, temporarily resolving the issue. However, at 12:00 PM UTC on October 13, the issue re-emerged. Our team resumed investigations at 12:30 PM and successfully deployed a stable fix by 01:30 PM. The root cause of the issue was identified and resolved. Access to communities has been restored and is now stable. We are closely monitoring the situation to ensure that the fix holds and to prevent any recurrence of this issue. We appreciate your patience and understanding as we worked to resolve this matter quickly.

We've resolved the issue regarding community service. Everything is back up.

The community service is experiencing technical difficulties. Our tech team is notified.

This incident has been resolved.

The community service is back up and our team is monitoring the infrastructure.

We are currently experiencing a downtime on the community service in the US region. We are investigating the issue.

This incident has been resolved.

The issue is now resolved. We're monitoring our servers to ensure all servers are healthy.

We are continuing to work on a fix for this issue.

We have identified the issue and are working on a fix.

This incident has been resolved.

We have patched the issue and will continue monitoring the situation.

We are experiencing a partial outage in our US region where the content of our posts for some post types are not accessible. We have identified the issue and are working on a fix.

This incident has been resolved.

We are continuing to monitor for any further issues.

We have identified and fixed the issue. Communities are operational now. We are still monitoring the servers.

We are investigating the cause of the issue.

We've resolved the issue regarding community service. Everything is back up.

The community service is experiencing technical difficulties. Our tech team is notified.

We've resolved the issue regarding community service. Everything is back up.

The community service is experiencing technical difficulties. Our tech team is notified.

We've resolved the issue regarding community service. Everything is back up.

The community service is experiencing technical difficulties. Our tech team is notified.

We've resolved the issue regarding community service. Everything is back up.

The community service is experiencing technical difficulties. Our tech team is notified.

On November 17th from 15:55 ET to 16:27 ET we experienced 15 minutes of downtime and 17 minutes of extreme slowness \(7-10 seconds P95 response time\). The issue was a hardware issue in one of our load balancers provided by our infrastructure provider. All our load balancers have a fail-safe mechanism that fallback faulty load balancers to the backup one. After the incident was fixed, over the past day we’ve worked closely with our infrastructure provider engineers to figure out the reason the load balancer did not fallback to the backup LB. We can confirm that our infrastructure provider found out the issue and have patched their infrastructure and added tests to prevent similar issue from happening.

We've resolved the issue regarding community service. Everything is back up.

The community service is experiencing technical difficulties. Our tech team is notified.

We've resolved the issue regarding community service. Everything is back up.

The community service is experiencing technical difficulties. Our tech team is notified.

The incident has been resolved.

Systems are back up. We're monitoring our servers to make sure everything is working properly.

We have identified the issue and are working on a fix.

We have experienced 18 minutes of downtime on V1 communities under tribe.so subdomain and some V2 communities. This issue did not V1 communities under custom domain or tribeplatform.com. The root cause of this issue was expiration of an intermediate SSL certificate. Our engineers identified the issue right away and patched the servers with an updated intermediate SSL certificate. If you're still experiencing this issue, please close and reopen your browser and try again.

The incident has been resolved. We apologize for any inconvenience caused. We're going to release the post-mortem here.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

This partial outage impacts communities under `.tribeplatform.com` subdomains and the ones that were moved to a custom domain from a `.tribeplatform.com` subdomain (Tribe 2.0 communities). We are experiencing a problem in one of our microservices, therefore, although the home page of communities is loaded properly and member authentication works, the space and post pages are experiencing problems. The team has identified the issue and we're working on releasing a fix.

This incident has been resolved.

The issue was identified and resolved. We're closely monitoring to make sure everything is in order.

We are experiencing downtime on Tribe 1.0 communities. The team is looking into the issue.

The issue is now resolved and we're back up. Sorry for the inconvenience.

We are still working on a fix.

Our feed is not loading in some of our new Tribe Platform communities (communities under *.tribeplatform.com). We have identified the issue and are working on a fix.

This incident has been resolved.

We have identified the issue and the service was patched. The Post service and the feed are back up. We're actively monitoring all the services.

We are experiencing a partial outage on Tribe communities (*.tribeplatform.com) in our US east region. There is an issue with our Posts service and the community feed takes a long time to show up. We are investigating the issue.

The issue is now fully resolved. It was a DDoS attack on some of our key services. We have taken a few immediate actions that prevent the same type of DDoS attack on our services. In addition, we are going to run a post-mortem to see how we could have prevented this attack from happening.

We are back up and monitoring the issue as we speak.

The engineering team has identified the issue and we're working on resolving it.

Currently, we're experiencing downtime on Tribe 2.0 US servers. Our engineering team is investigating the issue.