Skip to content

Outage tracker / Bird (MessageBird)

Is Bird (MessageBird) down?

I'm having a problem

Partially downchecked 8 minutes ago

Part of Bird (MessageBird) is not answering our probes: its web surface from Australia. Its API, the surface we treat as the service's own, answered from every region we check.

Functional endpoints verified

We have an outage open for Bird (MessageBird), 2h 38m so far.

No outage recorded in the 14 days we have measured Bird (MessageBird) (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 11:17 PM UTC
US-East466 msOperational
US-West22 msOperational
Europe117 msOperational
Asia-Pacific515 msOperational
US-Central305 msOperational
Canada351 msOperational
UK88 msOperational
Southeast Asia262 msOperational
Australia1113 msPartially down
South America779 msOperational
their status pagetheir claim, not our reading

Bird (MessageBird) reports: All systems operational (“All Systems Operational”)

from Bird (MessageBird)'s own status page, checked Sep 5, 2026, 11:10 PM UTC
Our probes are seeing errors from Bird (MessageBird) right now. Bird (MessageBird)'s own status page currently reports All Systems Operational. We are not able to explain the difference. It's possible the issue is limited to the specific request path we check, or that their status page has not updated yet.

Bird (MessageBird)'s own component breakdown, as they publish it

  • Dashboard - app.bird.comOperational
  • Dashboard - dashboard.messagebird.comOperational
  • InstanceOperational
  • Site - bird.comOperational
  • AI Hub - EuropeOperational
  • Data APIOperational
  • platform.bird.comOperational
  • SMS - Connectivity - APACOperational
  • AI Hub - US (West)Operational
  • Keeper APIOperational
  • SMS - Connectivity - EMEAOperational
  • AI Hub - Asia (India)Operational
  • SMS - Connectivity - LATAMOperational
  • Analytics - EuropeOperational
  • SMS - Connectivity - NORAMOperational
  • Analytics - US (West)Operational
  • Voice - Connectivity - GlobalOperational
  • Analytics - Asia (India)Operational
  • SMS - APIOperational
  • Campaigns - EuropeOperational
  • SMS - SMPP - EU - SMPP01Operational
  • Campaigns - US (West)Operational
  • SMS - SMPP - EU - SMPP02Operational
  • Campaigns - Asia (India)Operational
  • SMS - SMPP - EU - SMPP03Operational
  • Channels - EuropeOperational
  • SMS - SMPP - APACOperational
  • Channels - US (West)Operational
  • SMS - API V1Operational
  • Channels - Asia (India)Operational
  • SMS - Mail to SMS Relay ServiceOperational
  • Content (Products, Templates) - EuropeOperational
  • Voice - APIOperational
  • Content (Products, Templates) - US (West)Operational
  • Voice - SIP TrunkingOperational
  • Content (Products, Templates) - Asia (India)Operational
  • InboxOperational
  • Connectors - EuropeOperational
  • Flow BuilderOperational
  • Connectors - US (West)Operational
  • Omnichannel Chat WidgetOperational
  • Connectors - Asia (India)Operational
  • Numbers - APIOperational
  • Contacts - EuropeOperational
  • Conversations - APIOperational
  • Contacts - US (West)Operational
  • Messaging - APIOperational
  • Contacts - Asia (India)Operational
  • Email ChannelOperational
  • Chat Widget - EuropeOperational
  • WhatsApp ChannelOperational
  • Chat Widget - US (West)Operational
  • Chat Widget - Asia (India)Operational
  • Flows - EuropeOperational
  • Flows - US (West)Operational
  • Flows - Asia (India)Operational
  • Inbox - EuropeOperational
  • Inbox - US (West)Operational
  • Inbox - Asia (India)Operational
  • Journey - EuropeOperational
  • Journey - US (West)Operational
  • Journey - Asia (India)Operational
  • Organizations (Billing, IAM, Settings, Wallets) - EuropeOperational
  • Organizations (Billing, IAM, Settings, Wallets) - US (West)Operational
  • Organizations (Billing, IAM, Settings, Wallets) - Asia (India)Operational
  • Payments - Card - EuropeOperational
  • Payments - Card - US (West)Operational
  • Payments - Card - Asia (India)Operational
  • Payments - Pay - EuropeOperational
  • Payments - Pay - US (West)Operational
  • Payments - Pay - Asia (India)Operational

These are Bird (MessageBird)'s components, named and scored by Bird (MessageBird). We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Bird (MessageBird)'s own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Bird (MessageBird) response time, by region

US-East
616msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 765ms2026-08-23 UTC: p95 949ms2026-08-24 UTC: p95 835ms2026-08-25 UTC: p95 789ms2026-08-26 UTC: p95 626ms2026-08-27 UTC: p95 682ms2026-08-28 UTC: p95 756ms2026-08-29 UTC: p95 779ms2026-08-30 UTC: p95 881ms2026-08-31 UTC: p95 975ms2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 803ms2026-09-03 UTC: p95 817ms2026-09-04 UTC: p95 832ms2026-09-05 UTC: p95 616ms
Aug 7Aug 21Sep 5
US-West
258msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 312ms2026-08-23 UTC: p95 261ms2026-08-24 UTC: p95 202ms2026-08-25 UTC: p95 246ms2026-08-26 UTC: p95 234ms2026-08-27 UTC: p95 465ms2026-08-28 UTC: p95 681ms2026-08-29 UTC: p95 500ms2026-08-30 UTC: p95 551ms2026-08-31 UTC: p95 562ms2026-09-01 UTC: p95 515ms2026-09-02 UTC: p95 541ms2026-09-03 UTC: p95 578ms2026-09-04 UTC: p95 300ms2026-09-05 UTC: p95 258ms
Aug 7Aug 21Sep 5
Europe
295msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 218ms2026-08-23 UTC: p95 399ms2026-08-24 UTC: p95 608ms2026-08-25 UTC: p95 305ms2026-08-26 UTC: p95 326ms2026-08-27 UTC: p95 305ms2026-08-28 UTC: p95 281ms2026-08-29 UTC: p95 218ms2026-08-30 UTC: p95 193ms2026-08-31 UTC: p95 199ms2026-09-01 UTC: p95 417ms2026-09-02 UTC: p95 354ms2026-09-03 UTC: p95 426ms2026-09-04 UTC: p95 196ms2026-09-05 UTC: p95 295ms
Aug 7Aug 21Sep 5
Asia-Pacific
667msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 856ms2026-08-23 UTC: p95 1.2s2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 949ms2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 953ms2026-08-31 UTC: p95 962ms2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.5s2026-09-03 UTC: p95 1.9s2026-09-04 UTC: p95 753ms2026-09-05 UTC: p95 667ms
Aug 7Aug 21Sep 5
US-Central
634msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 748ms2026-09-04 UTC: p95 634ms2026-09-05 UTC: p95 634ms
Aug 7Aug 21Sep 5
Canada
538msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 757ms2026-09-04 UTC: p95 634ms2026-09-05 UTC: p95 538ms
Aug 7Aug 21Sep 5
UK
303msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 349ms2026-09-04 UTC: p95 514ms2026-09-05 UTC: p95 303ms
Aug 7Aug 21Sep 5
Southeast Asia
979msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 979ms
Aug 7Aug 21Sep 5
Australia
2.7sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.8s2026-09-04 UTC: p95 2.7s2026-09-05 UTC: p95 2.7s
Aug 7Aug 21Sep 5
South America
1.7sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.5s2026-09-04 UTC: p95 1.5s2026-09-05 UTC: p95 1.7s
Aug 7Aug 21Sep 5

Is it Bird (MessageBird), or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Bird (MessageBird) -- it cannot diagnose Bird (MessageBird)'s own systems.

What we measured, function by function

Bird (MessageBird) answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: DownSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

Open incident

Sep 5, 2026, 8:47 PM UTCOngoing
single region
open for 2h 38m so farAustralia: failing from Sep 5, 2026, 8:47 PM UTC, still failing

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 466msstatus code: 401checked: Sep 5, 2026, 11:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Bird (MessageBird) normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 22msstatus code: 401checked: Sep 5, 2026, 11:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Bird (MessageBird) normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 305msstatus code: 401checked: Sep 5, 2026, 10:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Bird (MessageBird) normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 351msstatus code: 401checked: Sep 5, 2026, 11:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Bird (MessageBird) normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 779msstatus code: 401checked: Sep 5, 2026, 10:50 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Bird (MessageBird) normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 117msstatus code: 401checked: Sep 5, 2026, 11:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Bird (MessageBird) normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 88msstatus code: 401checked: Sep 5, 2026, 11:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Bird (MessageBird) normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Partially downAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 515msstatus code: 401checked: Sep 5, 2026, 10:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Bird (MessageBird) normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 262msstatus code: 401checked: Sep 5, 2026, 10:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Bird (MessageBird) normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Partially downlatency: 1113msstatus code: 401checked: Sep 5, 2026, 10:48 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Bird (MessageBird) normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Bird (MessageBird), counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Bird (MessageBird) yet, which is not evidence that nothing is wrong.

Recent outages

Inbox — Service Outage, 5h 11mdeclared on their status page2026-08-13
Connectors failing for some customers., 5h 3mdeclared on their status page2026-08-06
Dashboard Search Indexing Issue, 2h 38mdeclared on their status page2026-07-22
Delay in processing Message & Contact Objects - Impact limited to customer hosted on us-west-1 region, 2h 16mdeclared on their status page2026-07-08
Journeys failure rate increase, 23mdeclared on their status page2026-07-05
WhatsApp message delivery issues, 4h 12mdeclared on their status page2026-06-12
Flows and Journeys unable to retrieve the Message Body for Conversation Messages, 49mdeclared on their status page2026-06-04
Increase of delivery latency for SMS messages, 1h 44mdeclared on their status page2026-06-04

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Bird (MessageBird) since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Bird (MessageBird) covering any window you pick, with our measurements and Bird (MessageBird)'s own claim at the time, side by side.

Full availability history for Bird (MessageBird): 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Bird (MessageBird), and again when they can reach it again. That is our own measurement from ten regions, not Bird (MessageBird)'s status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Bird (MessageBird) uptime measured by RealUptimeLive, from this page's own readings.
[![Bird (MessageBird) uptime measured by RealUptime](https://realuptime.io/outages/bird/badge.svg?days=30)](https://realuptime.io/outages/bird)
<a href="https://realuptime.io/outages/bird"><img src="https://realuptime.io/outages/bird/badge.svg?days=30" alt="Bird (MessageBird) uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Bird (MessageBird)'s SLA implies, from our measurement

At or above your target

We measured none of downtime for Bird (MessageBird) over the 359h 25m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 21 minutes over that period.

By our measurement there is no shortfall to claim for this period.

Separately, we measured 2h 37m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, not from Bird (MessageBird)'s SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.bird.com/workspaces
secondary
https://bird.com/
secondary
https://status.bird.com/api/v2/status.json
RealUptime is not affiliated with Bird (MessageBird); the name identifies what we measured, and nothing here speaks for Bird (MessageBird)'s own team. We send a single web request to Bird (MessageBird) from 10 regions on our own schedule and time the response. We do not see inside Bird (MessageBird)'s systems, do not use an account or real transaction, and are not the same signal Bird (MessageBird)'s own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Bird (MessageBird) is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.