Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for MessengerPeople GmbH and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for MessengerPeople GmbH.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
App (Frontend) | Active |
AWS s3-eu-central-1 | Active |
Chatbot-Engine | Active |
Google Cloud Platform Google Compute Engine | Active |
Google Cloud Platform Google Kubernetes Engine | Active |
Rest-API | Active |
Messenger Gateways | Active |
Apple Business Chat | Active |
Facebook Messenger | Active |
Active | |
Notify | Active |
Telegram | Active |
Viber | Active |
WhatsApp Business | Active |
View the latest incidents for MessengerPeople GmbH and check for official updates:
Description: All numbers updated. We keep monitoring. If you have a problem with your WhatsApp Business API Account, please contact us asap via [email protected]
Status: Resolved
Impact: Minor | Started At: Aug. 11, 2020, 9:33 a.m.
Description: All numbers have been upgraded
Status: Resolved
Impact: None | Started At: July 30, 2020, 7:54 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: April 1, 2020, 9:35 p.m.
Description: After WhatsApp had problems with sending / receiving media files this sunday we are still experiencing problems on some accounts. These problems are resolved by simply restarting the container, which is why we're currently restarting all WhatsApp Business Accounts / Containers. This results in a downtime of ~10-15 seconds for each restarted container.
Status: Resolved
Impact: None | Started At: Jan. 21, 2020, 10:29 a.m.
Description: Today we upgraded to the newest WhatsApp Business API version (2.25.3). After testing all features on our internal test numbers, we decided to roll out the upgrade. Shortly after that, we saw several errors upcoming and tried to figure out the source of the problem. After restarting single containers, it looked good at first, until new problems showed up. Too many connections on the database. Long story short: After upgrading to the new version it seems like every container spawned ~100 unused database connections and kept them open, in an infinite loop, trying to create already existing tables. This caused a breakdown on the database, and containers were unable to start up / connect. We did a rollback test which worked fine and rolled back all VMs to the previous version at around 12:30 UTC and saw everything coming back to normal.
Status: Resolved
Impact: None | Started At: Oct. 8, 2019, 9 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.