Skip to content

Outage tracker

Bird (MessageBird): the full evidence record

The last 24 hours in detail, 11 days of measured availability, a 12-month summary, our own incident log, Bird (MessageBird)'s declared record, and how the two compare.

← Back to Bird (MessageBird)'s live status

We started measuring Bird (MessageBird) on August 22, 2026, which is 11 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Bird (MessageBird)'s own status page declared. Below it, any public chatter we saw about Bird (MessageBird) and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Bird (MessageBird)'s own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Bird (MessageBird) in the last 24 hours, which is not evidence that nothing is wrong.
Bird (MessageBird)'s status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Bird (MessageBird)'s own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Bird (MessageBird) next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

  • Bluesky posts1 in the last hour (prior day averaged 0.5/hour)

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%418
US-West100.00%418
Europe100.00%415
Asia-Pacific100.00%407

Monthly summary

Tracking Bird (MessageBird) since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Sep 2025not tracked
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Bird (MessageBird): two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Bird (MessageBird)'s own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Bird (MessageBird) in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Bird (MessageBird)'s own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Bird (MessageBird) since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Bird (MessageBird)'s own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Inbox — Service OutageMinor incident
Aug 13, 2026, 5:06 PM UTC to Aug 13, 2026, 10:17 PM UTC (5h 11m)resolved
their latest update (Aug 13, 2026, 10:17 PM UTC): This incident has been resolved.
Connectors failing for some customers.Partial outage
Aug 6, 2026, 5:05 PM UTC to Aug 6, 2026, 10:08 PM UTC (5h 3m)resolved
their latest update (Aug 6, 2026, 10:08 PM UTC): This incident has been resolved.
Dashboard Search Indexing IssueAll systems operational
Jul 22, 2026, 12:16 PM UTC to Jul 22, 2026, 2:54 PM UTC (2h 38m)resolved
their latest update (Jul 22, 2026, 2:54 PM UTC): This incident has been resolved.
Delay in processing Message & Contact Objects - Impact limited to customer hosted on us-west-1 regionMinor incident
Jul 8, 2026, 8:12 PM UTC to Jul 8, 2026, 10:28 PM UTC (2h 16m)resolved
their latest update (Jul 8, 2026, 10:28 PM UTC): This incident has been resolved.
Journeys failure rate increaseMinor incident
Jul 5, 2026, 3:50 PM UTC to Jul 5, 2026, 4:12 PM UTC (23 min)resolved
their latest update (Jul 5, 2026, 4:12 PM UTC): This incident has been resolved.
WhatsApp message delivery issuesMinor incident
Jun 12, 2026, 2:10 PM UTC to Jun 12, 2026, 6:22 PM UTC (4h 12m)resolved
their latest update (Jun 12, 2026, 6:22 PM UTC): This incident has been resolved.
Flows and Journeys unable to retrieve the Message Body for Conversation MessagesAll systems operational
Jun 4, 2026, 11:13 AM UTC to Jun 4, 2026, 12:02 PM UTC (49 min)resolved
their latest update (Jun 4, 2026, 12:02 PM UTC): This incident has been resolved.
Increase of delivery latency for SMS messagesAll systems operational
Jun 4, 2026, 9:57 AM UTC to Jun 4, 2026, 11:42 AM UTC (1h 44m)resolved
their latest update (Jun 4, 2026, 11:42 AM UTC): This incident has been resolved.
Conversations data processing is behindMinor incident
Jun 1, 2026, 4:33 PM UTC to Jun 1, 2026, 5:22 PM UTC (50 min)resolved
their latest update (Jun 1, 2026, 5:22 PM UTC): This incident has been resolved.
Overview pages and Search downAll systems operational
May 20, 2026, 10:06 AM UTC to May 20, 2026, 10:16 AM UTC (10 min)resolved
their latest update (May 20, 2026, 10:16 AM UTC): This incident has been resolved.

Showing the 10 most recent of 50 incidents Bird (MessageBird) has declared in the history we hold.

These entries are Bird (MessageBird)'s own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Bird (MessageBird)'s status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Bird (MessageBird)'s own status page on August 22, 2026, 9 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Bird (MessageBird) since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Bird (MessageBird) decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Bird (MessageBird) believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.