Welcome to Tribal Habit's home for real-time information and updates on our applications. Here you'll find live and historical data on system performance and metrics. If there are any service interruptions, a note will be posted here.
Front End User Servers
Front End Servers on AWS EC2.
Operational
90 days ago
100.0
% uptime
Today
Back End Database Servers
Back end database storage of user and topic data (AWS RDS).
Operational
90 days ago
100.0
% uptime
Today
Image and File Storage
Storage of topic images and files (AWS S3).
Operational
90 days ago
100.0
% uptime
Today
Video Storage and Distribution
Storage and distribution of topic videos (Wistia).
Operational
90 days ago
100.0
% uptime
Today
Stock image library
Access to the Pixabay stock image library.
Operational
90 days ago
100.0
% uptime
Today
Email Notifications
Automated email notifications sent by the platform.
Operational
90 days ago
100.0
% uptime
Today
Admin Chat and Knowledge Base
Our knowledge base at support.tribalhabits.com and the in-platform Admin Chat feature.
Operational
90 days ago
99.96
% uptime
Today
Customer Payment Portal
The separate customer payment portal for credit card information for monthly subscriptions.
Operational
90 days ago
100.0
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Resolved -
We had a server on AWS have a bad deployment this morning, resulting in instability in that server. As platform usage grew through the morning, the server ultimately became degraded at about 9 am AEST. At that point, users on that server may have encountered 502 Bad Gateway Errors. Reloading the bad would often fix the issue, but the error may have returned as the server continued to degrade.
Our Load Balancer was triggered to reassign users to good servers around 10 am AEST and the degraded server was then terminated and new servers rebuilt. By 10:15 am all users on the degraded server were moved to good servers and the environment was stabilised.
This situation is extremely rare with AWS but our health alarms and load balancer worked as intended and resolved the situation quickly. We apologise for any inconvenience caused to any users.
Sep 22, 09:00 AEST