How SutramX detects Bird (MessageBird) problems
SutramX customers monitor Bird (MessageBird) and the services that call it. When those checks fail for at least 3 different customer accounts at the same time, with timeouts, 5xx errors, connection or TLS failures, SutramX marks Bird (MessageBird) as degraded and adds “likely external” to the affected customers' incidents and alerts. Only aggregate signals are published here: never a customer, a monitored URL, a response time or an exact number of accounts. How vendor outage detection works.
Frequently asked questions
How do I know if Bird (MessageBird) is down?
This page shows what SutramX's own uptime checks of Bird (MessageBird) see, across customer accounts, updated every minute. For the vendor's own word on an incident, see Bird (MessageBird)'s official status page. To tell whether a failure is yours or Bird (MessageBird)'s, monitor your own integration: SutramX marks an incident "likely external" when Bird (MessageBird) is failing for several customers at once.
Is this Bird (MessageBird)'s official status page?
No. These are signals from SutramX checks, not an official Bird (MessageBird) status page. SutramX often sees a problem before a status page is updated, but not always.
Why does it say "Not enough data"?
SutramX only says Bird (MessageBird) has no problems when enough different customer accounts are checking it at that time. With too few checks it says it does not know rather than guess.
What counts as a disruption?
Checks of Bird (MessageBird) failing for at least 3 different SutramX customer accounts at the same time, with timeouts, 5xx errors, connection failures or TLS errors. Errors that point at the caller, such as 401 or 404 responses or rate limits, do not count. "Likely outage" means it was failing for most of the accounts that check it.
Other communication vendors
Learn more
- Features: Vendor Outage Detection and API Monitoring
- Free tools: Is It Down?
- Documentation: Vendor health and Third-party status