Skip to content

Outage tracker / Bird (MessageBird)

Is Bird (MessageBird) down?

I'm having a problem

Vendor reports no incidentWhat Bird (MessageBird) reports

Bird (MessageBird) reports no incident on its status page.

As of the last successful poll, 2026-10-19 21:36 UTC.

Bird (MessageBird)'s status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 4 minutes ago

Our checks of Bird (MessageBird) pass from all 10 regions we check.

As of Oct 19, 2026, 9:33 PM UTC, RealUptime's checks of Bird (MessageBird) passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 19, 2026, 9:33 PM UTC
US-East442 msChecks passing
US-West129 msChecks passing
Europe315 msChecks passing
Asia-Pacific497 msChecks passing
US-Central221 msChecks passing
Canada318 msChecks passing
UK116 msChecks passing
Southeast Asia391 msChecks passing
Australia835 msChecks passing
South America1128 msChecks passing
their status pagetheir claim, not our reading

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

from Bird (MessageBird)'s own status page, checked Oct 19, 2026, 9:23 PM UTC

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

  • Bird PlatformOperational
  • Dashboard - app.bird.comOperational
  • Dashboard - dashboard.messagebird.comOperational
  • InstanceOperational
  • AI Hub - EuropeOperational
  • Data APIOperational
  • SMS - Connectivity - APACOperational
  • Site bird.comOperational
  • 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
872msp95 · 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-09-20 UTC: p95 493ms2026-09-21 UTC: p95 495ms2026-09-22 UTC: p95 517ms2026-09-23 UTC: p95 496ms2026-09-24 UTC: p95 629ms2026-09-25 UTC: p95 477ms2026-09-26 UTC: p95 504ms2026-09-27 UTC: p95 484ms2026-09-28 UTC: p95 487ms2026-09-29 UTC: p95 504ms2026-09-30 UTC: p95 488ms2026-10-01 UTC: p95 530ms2026-10-02 UTC: p95 472ms2026-10-03 UTC: p95 480ms2026-10-04 UTC: p95 520ms2026-10-05 UTC: p95 475ms2026-10-06 UTC: p95 489ms2026-10-07 UTC: p95 482ms2026-10-08 UTC: p95 498ms2026-10-09 UTC: p95 498ms2026-10-10 UTC: p95 482ms2026-10-11 UTC: p95 492ms2026-10-12 UTC: p95 508ms2026-10-13 UTC: p95 464ms2026-10-14 UTC: p95 506ms2026-10-15 UTC: p95 498ms2026-10-16 UTC: p95 481ms2026-10-17 UTC: p95 454ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 872ms
Sep 20Oct 4Oct 19
US-West
443msp95 · latest
500ms250ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 124ms2026-09-21 UTC: p95 223ms2026-09-22 UTC: p95 270ms2026-09-23 UTC: p95 194ms2026-09-24 UTC: p95 204ms2026-09-25 UTC: p95 251ms2026-09-26 UTC: p95 289ms2026-09-27 UTC: p95 223ms2026-09-28 UTC: p95 202ms2026-09-29 UTC: p95 185ms2026-09-30 UTC: p95 164ms2026-10-01 UTC: p95 342ms2026-10-02 UTC: p95 213ms2026-10-03 UTC: p95 193ms2026-10-04 UTC: p95 170ms2026-10-05 UTC: p95 197ms2026-10-06 UTC: p95 224ms2026-10-07 UTC: p95 305ms2026-10-08 UTC: p95 188ms2026-10-09 UTC: p95 253ms2026-10-10 UTC: p95 195ms2026-10-11 UTC: p95 210ms2026-10-12 UTC: p95 174ms2026-10-13 UTC: p95 201ms2026-10-14 UTC: p95 305ms2026-10-15 UTC: p95 179ms2026-10-16 UTC: p95 178ms2026-10-17 UTC: p95 241ms2026-10-18 UTC: p95 225ms2026-10-19 UTC: p95 443ms
Sep 20Oct 4Oct 19
Europe
228msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 225ms2026-09-21 UTC: p95 234ms2026-09-22 UTC: p95 231ms2026-09-23 UTC: p95 223ms2026-09-24 UTC: p95 228ms2026-09-25 UTC: p95 275ms2026-09-26 UTC: p95 236ms2026-09-27 UTC: p95 239ms2026-09-28 UTC: p95 239ms2026-09-29 UTC: p95 228ms2026-09-30 UTC: p95 205ms2026-10-01 UTC: p95 229ms2026-10-02 UTC: p95 213ms2026-10-03 UTC: p95 225ms2026-10-04 UTC: p95 224ms2026-10-05 UTC: p95 220ms2026-10-06 UTC: p95 224ms2026-10-07 UTC: p95 228ms2026-10-08 UTC: p95 217ms2026-10-09 UTC: p95 190ms2026-10-10 UTC: p95 225ms2026-10-11 UTC: p95 207ms2026-10-12 UTC: p95 223ms2026-10-13 UTC: p95 190ms2026-10-14 UTC: p95 176ms2026-10-15 UTC: p95 228ms2026-10-16 UTC: p95 187ms2026-10-17 UTC: p95 178ms2026-10-18 UTC: p95 381ms2026-10-19 UTC: p95 228ms
Sep 20Oct 4Oct 19
Asia-Pacific
808msp95 · 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-09-20 UTC: p95 751ms2026-09-21 UTC: p95 915ms2026-09-22 UTC: p95 893ms2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 879ms2026-09-25 UTC: p95 728ms2026-09-26 UTC: p95 872ms2026-09-27 UTC: p95 940ms2026-09-28 UTC: p95 848ms2026-09-29 UTC: p95 708ms2026-09-30 UTC: p95 802ms2026-10-01 UTC: p95 762ms2026-10-02 UTC: p95 710ms2026-10-03 UTC: p95 731ms2026-10-04 UTC: p95 772ms2026-10-05 UTC: p95 825ms2026-10-06 UTC: p95 697ms2026-10-07 UTC: p95 787ms2026-10-08 UTC: p95 732ms2026-10-09 UTC: p95 950ms2026-10-10 UTC: p95 794ms2026-10-11 UTC: p95 788ms2026-10-12 UTC: p95 765ms2026-10-13 UTC: p95 831ms2026-10-14 UTC: p95 775ms2026-10-15 UTC: p95 766ms2026-10-16 UTC: p95 826ms2026-10-17 UTC: p95 860ms2026-10-18 UTC: p95 735ms2026-10-19 UTC: p95 808ms
Sep 20Oct 4Oct 19
US-Central
321msp95 · latest
500ms250ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 346ms2026-09-21 UTC: p95 447ms2026-09-22 UTC: p95 392ms2026-09-23 UTC: p95 453ms2026-09-24 UTC: p95 380ms2026-09-25 UTC: p95 331ms2026-09-26 UTC: p95 372ms2026-09-27 UTC: p95 347ms2026-09-28 UTC: p95 347ms2026-09-29 UTC: p95 409ms2026-09-30 UTC: p95 347ms2026-10-01 UTC: p95 349ms2026-10-02 UTC: p95 427ms2026-10-03 UTC: p95 378ms2026-10-04 UTC: p95 402ms2026-10-05 UTC: p95 377ms2026-10-06 UTC: p95 347ms2026-10-07 UTC: p95 456ms2026-10-08 UTC: p95 459ms2026-10-09 UTC: p95 343ms2026-10-10 UTC: p95 322ms2026-10-11 UTC: p95 399ms2026-10-12 UTC: p95 372ms2026-10-13 UTC: p95 367ms2026-10-14 UTC: p95 319ms2026-10-15 UTC: p95 377ms2026-10-16 UTC: p95 396ms2026-10-17 UTC: p95 372ms2026-10-18 UTC: p95 362ms2026-10-19 UTC: p95 321ms
Sep 20Oct 4Oct 19
Canada
387msp95 · latest
500ms250ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 391ms2026-09-21 UTC: p95 442ms2026-09-22 UTC: p95 386ms2026-09-23 UTC: p95 422ms2026-09-24 UTC: p95 412ms2026-09-25 UTC: p95 419ms2026-09-26 UTC: p95 420ms2026-09-27 UTC: p95 411ms2026-09-28 UTC: p95 429ms2026-09-29 UTC: p95 410ms2026-09-30 UTC: p95 421ms2026-10-01 UTC: p95 429ms2026-10-02 UTC: p95 435ms2026-10-03 UTC: p95 449ms2026-10-04 UTC: p95 408ms2026-10-05 UTC: p95 432ms2026-10-06 UTC: p95 434ms2026-10-07 UTC: p95 431ms2026-10-08 UTC: p95 451ms2026-10-09 UTC: p95 407ms2026-10-10 UTC: p95 405ms2026-10-11 UTC: p95 438ms2026-10-12 UTC: p95 437ms2026-10-13 UTC: p95 453ms2026-10-14 UTC: p95 407ms2026-10-15 UTC: p95 383ms2026-10-16 UTC: p95 363ms2026-10-17 UTC: p95 446ms2026-10-18 UTC: p95 397ms2026-10-19 UTC: p95 387ms
Sep 20Oct 4Oct 19
UK
207msp95 · 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-20 UTC: p95 161ms2026-09-21 UTC: p95 563ms2026-09-22 UTC: p95 231ms2026-09-23 UTC: p95 180ms2026-09-24 UTC: p95 205ms2026-09-25 UTC: p95 210ms2026-09-26 UTC: p95 204ms2026-09-27 UTC: p95 204ms2026-09-28 UTC: p95 203ms2026-09-29 UTC: p95 176ms2026-09-30 UTC: p95 179ms2026-10-01 UTC: p95 226ms2026-10-02 UTC: p95 201ms2026-10-03 UTC: p95 193ms2026-10-04 UTC: p95 182ms2026-10-05 UTC: p95 187ms2026-10-06 UTC: p95 201ms2026-10-07 UTC: p95 171ms2026-10-08 UTC: p95 189ms2026-10-09 UTC: p95 221ms2026-10-10 UTC: p95 166ms2026-10-11 UTC: p95 204ms2026-10-12 UTC: p95 199ms2026-10-13 UTC: p95 135ms2026-10-14 UTC: p95 168ms2026-10-15 UTC: p95 115ms2026-10-16 UTC: p95 118ms2026-10-17 UTC: p95 161ms2026-10-18 UTC: p95 150ms2026-10-19 UTC: p95 207ms
Sep 20Oct 4Oct 19
Southeast Asia
1.9sp95 · 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-20 UTC: p95 585ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 752ms2026-09-24 UTC: p95 820ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 871ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 811ms2026-09-30 UTC: p95 941ms2026-10-01 UTC: p95 844ms2026-10-02 UTC: p95 793ms2026-10-03 UTC: p95 807ms2026-10-04 UTC: p95 835ms2026-10-05 UTC: p95 679ms2026-10-06 UTC: p95 722ms2026-10-07 UTC: p95 668ms2026-10-08 UTC: p95 819ms2026-10-09 UTC: p95 910ms2026-10-10 UTC: p95 644ms2026-10-11 UTC: p95 853ms2026-10-12 UTC: p95 792ms2026-10-13 UTC: p95 860ms2026-10-14 UTC: p95 856ms2026-10-15 UTC: p95 943ms2026-10-16 UTC: p95 575ms2026-10-17 UTC: p95 577ms2026-10-18 UTC: p95 711ms2026-10-19 UTC: p95 1.9s
Sep 20Oct 4Oct 19
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-20 UTC: p95 1.3s2026-09-21 UTC: p95 2.8s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 2.3s2026-09-26 UTC: p95 2.3s2026-09-27 UTC: p95 3.4s2026-09-28 UTC: p95 2.7s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 2.1s2026-10-04 UTC: p95 2.0s2026-10-05 UTC: p95 2.2s2026-10-06 UTC: p95 2.4s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 2.4s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 2.7s
Sep 20Oct 4Oct 19
South America
1.1sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 956ms2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
Why some readings show as awaiting data. 1 of 20 readings for Bird (MessageBird) came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Bird (MessageBird)'s health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on Bird (MessageBird)

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Awaiting dataCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Bird (MessageBird) reports an incident on its status page, and again when it reports it resolved.

Get an email when Bird (MessageBird) reports an incident

Email me when Bird (MessageBird) reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Bird (MessageBird)'s own statement from its status page, with our regional reading beside it.

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.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 442msstatus code: 401checked: Oct 19, 2026, 9:13 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
      Checks passinglatency: 129msstatus code: 401checked: Oct 19, 2026, 9:15 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
      Checks passinglatency: 221msstatus code: 401checked: Oct 19, 2026, 8:47 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
      Checks passinglatency: 318msstatus code: 401checked: Oct 19, 2026, 9:33 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
    Checks passinglatency: 1128msstatus code: 401checked: Oct 19, 2026, 8:44 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 315msstatus code: 401checked: Oct 19, 2026, 9:19 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
      Checks passinglatency: 116msstatus code: 401checked: Oct 19, 2026, 8:42 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 497msstatus code: 401checked: Oct 19, 2026, 9:14 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
      Checks passinglatency: 391msstatus code: 401checked: Oct 19, 2026, 8:38 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
      Checks passinglatency: 835msstatus code: 401checked: Oct 19, 2026, 8:40 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 probe events

Bird.com Platform: Increased 5xx errors and delivery deliays, 53mdeclared on their status page2026-10-05
Increased delivery latency for SMS service, 47mdeclared on their status page2026-10-04
Increased Error rates on USA Bird Platform API, 19mdeclared on their status page2026-09-26
Flow Logs failures in EU, 3h 29mdeclared on their status page2026-09-21
Elevated processing delays — US region, 1h 29mdeclared on their status page2026-09-18
Elevated API errors and voice call setup failures (US), 1h 22mdeclared on their status page2026-09-17
Incoming calls to UK with one-way audio, 120h 5mdeclared on their status page2026-09-11
SMS processing disruption, 1mdeclared on their status page2026-09-10

check 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 check readings and Bird (MessageBird)'s own claim at the time, side by side.

Full check history for Bird (MessageBird): 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Bird (MessageBird) uptime by RealUptime's checksLive, from this page's own readings.
[![Bird (MessageBird) uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Bird (MessageBird) down?", https://realuptime.io/outages/bird. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.bird.com/workspaces
secondary
https://bird.com/
secondary
https://status.bird.com/api/v2/status.json

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.bird.com

RealUptime is not affiliated with Bird (MessageBird); the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.