Skip to content

Outage tracker / Bird (MessageBird)

Is Bird (MessageBird) down?

I'm having a problem

Partially downchecked 4 minutes ago

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

As of Sep 13, 2026, 4:11 PM UTC, Bird (MessageBird) answered RealUptime's probes in all 10 regions that returned a reading. Our Australia and South America probes reached some of its surfaces and not others.

Functional endpoints verified

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

Last outage: 2h 32m on Sep 12, 2026 (web surface, from South America).

Bird (MessageBird) reports an active incident: "Incoming calls to UK with one-way audio" (minor incident, since Sep 11, 2026, 11:38 AM UTC). That is their claim, shown alongside what we measured above; neither reading changes the other.

our independent probeslive · checked Sep 13, 2026, 4:11 PM UTC
US-East402 msOperational
US-West19 msOperational
Europe123 msOperational
Asia-Pacific546 msOperational
US-Central257 msOperational
Canada341 msOperational
UK72 msOperational
Southeast Asia372 msOperational
Australia940 msPartially down
South America910 msPartially down
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 13, 2026, 4:06 PM UTC

Bird (MessageBird) reports an active incident: Incoming calls to UK with one-way audio (minor incident, since Sep 11, 2026, 11:38 AM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.

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
532msp95 · 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 616ms2026-09-06 UTC: p95 463ms2026-09-07 UTC: p95 446ms2026-09-08 UTC: p95 522ms2026-09-09 UTC: p95 513ms2026-09-10 UTC: p95 491ms2026-09-11 UTC: p95 445ms2026-09-12 UTC: p95 484ms2026-09-13 UTC: p95 532ms
Aug 15Aug 29Sep 13
US-West
272msp95 · 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 258ms2026-09-06 UTC: p95 358ms2026-09-07 UTC: p95 288ms2026-09-08 UTC: p95 265ms2026-09-09 UTC: p95 118ms2026-09-10 UTC: p95 192ms2026-09-11 UTC: p95 333ms2026-09-12 UTC: p95 108ms2026-09-13 UTC: p95 272ms
Aug 15Aug 29Sep 13
Europe
215msp95 · 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 294ms2026-09-06 UTC: p95 202ms2026-09-07 UTC: p95 231ms2026-09-08 UTC: p95 200ms2026-09-09 UTC: p95 217ms2026-09-10 UTC: p95 238ms2026-09-11 UTC: p95 235ms2026-09-12 UTC: p95 215ms2026-09-13 UTC: p95 215ms
Aug 15Aug 29Sep 13
Asia-Pacific
880msp95 · 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 663ms2026-09-06 UTC: p95 778ms2026-09-07 UTC: p95 818ms2026-09-08 UTC: p95 789ms2026-09-09 UTC: p95 738ms2026-09-10 UTC: p95 756ms2026-09-11 UTC: p95 957ms2026-09-12 UTC: p95 675ms2026-09-13 UTC: p95 880ms
Aug 15Aug 29Sep 13
US-Central
311msp95 · 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 627ms2026-09-06 UTC: p95 346ms2026-09-07 UTC: p95 388ms2026-09-08 UTC: p95 554ms2026-09-09 UTC: p95 347ms2026-09-10 UTC: p95 337ms2026-09-11 UTC: p95 364ms2026-09-12 UTC: p95 428ms2026-09-13 UTC: p95 311ms
Aug 15Aug 29Sep 13
Canada
434msp95 · 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 537ms2026-09-06 UTC: p95 355ms2026-09-07 UTC: p95 417ms2026-09-08 UTC: p95 379ms2026-09-09 UTC: p95 401ms2026-09-10 UTC: p95 362ms2026-09-11 UTC: p95 423ms2026-09-12 UTC: p95 407ms2026-09-13 UTC: p95 434ms
Aug 15Aug 29Sep 13
UK
231msp95 · 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 300ms2026-09-06 UTC: p95 216ms2026-09-07 UTC: p95 162ms2026-09-08 UTC: p95 134ms2026-09-09 UTC: p95 142ms2026-09-10 UTC: p95 173ms2026-09-11 UTC: p95 98ms2026-09-12 UTC: p95 121ms2026-09-13 UTC: p95 231ms
Aug 15Aug 29Sep 13
Southeast Asia
676msp95 · 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 969ms2026-09-06 UTC: p95 810ms2026-09-07 UTC: p95 782ms2026-09-08 UTC: p95 812ms2026-09-09 UTC: p95 754ms2026-09-10 UTC: p95 680ms2026-09-11 UTC: p95 952ms2026-09-12 UTC: p95 884ms2026-09-13 UTC: p95 676ms
Aug 15Aug 29Sep 13
Australia
1.1sp95 · 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.7s2026-09-06 UTC: p95 2.5s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.1s
Aug 15Aug 29Sep 13
South America
1.2sp95 · 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.6s2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s
Aug 15Aug 29Sep 13

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: Down
  • 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 13, 2026, 2:48 PM UTCOngoing
multiple regions
open for 1h 27m so farAustralia: failing from Sep 13, 2026, 2:48 PM UTC, still failingSouth America: failing from Sep 13, 2026, 2:48 PM UTC, still failing

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 402msstatus code: 401checked: Sep 13, 2026, 3:53 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: 19msstatus code: 401checked: Sep 13, 2026, 3:49 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: 257msstatus code: 401checked: Sep 13, 2026, 3:50 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: 341msstatus code: 401checked: Sep 13, 2026, 3:49 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
    Partially downlatency: 910msstatus code: 401checked: Sep 13, 2026, 3:48 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: 123msstatus code: 401checked: Sep 13, 2026, 3:53 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: 72msstatus code: 401checked: Sep 13, 2026, 3:50 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: 546msstatus code: 401checked: Sep 13, 2026, 4:11 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: 372msstatus code: 401checked: Sep 13, 2026, 3: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: 940msstatus code: 401checked: Sep 13, 2026, 3: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

Partial outage, 2h 32mmeasured by our probes · South America2026-09-12
Incoming calls to UK with one-way audiodeclared on their status page2026-09-11
SMS processing disruption, 1mdeclared on their status page2026-09-10
Partial outage, 1hmeasured by our probes · South America2026-09-08
Partial outage, 2h 58mmeasured by our probes · South America2026-09-06
Partial outage, 7h 31mmeasured by our probes · Australia2026-09-05
Inbox — Service Outage, 5h 11mdeclared on their status page2026-08-13
Connectors failing for some customers., 5h 3mdeclared on their status page2026-08-06

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

Below your target

We measured 1h 27m of downtime for Bird (MessageBird) over the 544h 15m since we started watching it on 2026-08-22, which is 99.7326% uptime by our reading. A 99.9% target allows 32 minutes over that period.

That is 54 minutes more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.

Separately, we measured 14h 1m 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.