Skip to content

Outage tracker / Signal

Is Signal down?

I'm having a problem

Checks passingchecked 3 minutes ago

Our checks of Signal pass from all 10 regions we check.

As of Oct 14, 2026, 4:59 AM UTC, RealUptime's checks of Signal passed in all 10 regions that returned a reading.

Front-door checks

Our checks of Signal did not fail from two or more distant regions in the 55 days we have checked it (since Aug 20, 2026). This does not show Signal works for users.

Email me when our checks of Signal fail from two or more distant regions

One email when our checks of Signal fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Signal's official status.

our check readinglive · checked Oct 14, 2026, 4:59 AM UTC
US-East186 msChecks passing
US-West536 msChecks passing
Europe87 msChecks passing
Asia-Pacific940 msChecks passing
US-Central240 msChecks passing
Canada266 msChecks passing
UK193 msChecks passing
Southeast Asia348 msChecks passing
Australia374 msChecks passing
South America585 msChecks passing
their status pagetheir claim, not our reading

Signal publishes no status feed we can read, so the only reading here is our check reading on the left.

Signal response time, by region

US-East
515msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 263ms2026-09-16 UTC: p95 284ms2026-09-17 UTC: p95 367ms2026-09-18 UTC: p95 336ms2026-09-19 UTC: p95 257ms2026-09-20 UTC: p95 271ms2026-09-21 UTC: p95 250ms2026-09-22 UTC: p95 321ms2026-09-23 UTC: p95 477ms2026-09-24 UTC: p95 490ms2026-09-25 UTC: p95 409ms2026-09-26 UTC: p95 321ms2026-09-27 UTC: p95 298ms2026-09-28 UTC: p95 349ms2026-09-29 UTC: p95 346ms2026-09-30 UTC: p95 319ms2026-10-01 UTC: p95 437ms2026-10-02 UTC: p95 316ms2026-10-03 UTC: p95 364ms2026-10-04 UTC: p95 348ms2026-10-05 UTC: p95 379ms2026-10-06 UTC: p95 340ms2026-10-07 UTC: p95 280ms2026-10-08 UTC: p95 292ms2026-10-09 UTC: p95 417ms2026-10-10 UTC: p95 444ms2026-10-11 UTC: p95 419ms2026-10-12 UTC: p95 275ms2026-10-13 UTC: p95 643ms2026-10-14 UTC: p95 515ms
Sep 15Sep 29Oct 14
US-West
723msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 492ms2026-09-16 UTC: p95 566ms2026-09-17 UTC: p95 516ms2026-09-18 UTC: p95 575ms2026-09-19 UTC: p95 550ms2026-09-20 UTC: p95 554ms2026-09-21 UTC: p95 730ms2026-09-22 UTC: p95 625ms2026-09-23 UTC: p95 558ms2026-09-24 UTC: p95 420ms2026-09-25 UTC: p95 733ms2026-09-26 UTC: p95 690ms2026-09-27 UTC: p95 424ms2026-09-28 UTC: p95 550ms2026-09-29 UTC: p95 638ms2026-09-30 UTC: p95 431ms2026-10-01 UTC: p95 599ms2026-10-02 UTC: p95 232ms2026-10-03 UTC: p95 591ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 785ms2026-10-06 UTC: p95 938ms2026-10-07 UTC: p95 859ms2026-10-08 UTC: p95 441ms2026-10-09 UTC: p95 688ms2026-10-10 UTC: p95 893ms2026-10-11 UTC: p95 980ms2026-10-12 UTC: p95 864ms2026-10-13 UTC: p95 903ms2026-10-14 UTC: p95 723ms
Sep 15Sep 29Oct 14
Europe
336msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 819ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 845ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 662ms2026-09-27 UTC: p95 684ms2026-09-28 UTC: p95 988ms2026-09-29 UTC: p95 905ms2026-09-30 UTC: p95 618ms2026-10-01 UTC: p95 433ms2026-10-02 UTC: p95 421ms2026-10-03 UTC: p95 484ms2026-10-04 UTC: p95 390ms2026-10-05 UTC: p95 430ms2026-10-06 UTC: p95 416ms2026-10-07 UTC: p95 446ms2026-10-08 UTC: p95 382ms2026-10-09 UTC: p95 346ms2026-10-10 UTC: p95 410ms2026-10-11 UTC: p95 505ms2026-10-12 UTC: p95 275ms2026-10-13 UTC: p95 334ms2026-10-14 UTC: p95 336ms
Sep 15Sep 29Oct 14
Asia-Pacific
1.2sp95 · 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-15 UTC: p95 982ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 960ms2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 942ms2026-09-22 UTC: p95 890ms2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 878ms2026-09-26 UTC: p95 961ms2026-09-27 UTC: p95 685ms2026-09-28 UTC: p95 632ms2026-09-29 UTC: p95 755ms2026-09-30 UTC: p95 873ms2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s
Sep 15Sep 29Oct 14
US-Central
460msp95 · 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-15 UTC: p95 384ms2026-09-16 UTC: p95 321ms2026-09-17 UTC: p95 313ms2026-09-18 UTC: p95 344ms2026-09-19 UTC: p95 297ms2026-09-20 UTC: p95 312ms2026-09-21 UTC: p95 325ms2026-09-22 UTC: p95 366ms2026-09-23 UTC: p95 452ms2026-09-24 UTC: p95 452ms2026-09-25 UTC: p95 376ms2026-09-26 UTC: p95 571ms2026-09-27 UTC: p95 527ms2026-09-28 UTC: p95 594ms2026-09-29 UTC: p95 490ms2026-09-30 UTC: p95 451ms2026-10-01 UTC: p95 390ms2026-10-02 UTC: p95 398ms2026-10-03 UTC: p95 401ms2026-10-04 UTC: p95 378ms2026-10-05 UTC: p95 338ms2026-10-06 UTC: p95 367ms2026-10-07 UTC: p95 401ms2026-10-08 UTC: p95 414ms2026-10-09 UTC: p95 485ms2026-10-10 UTC: p95 404ms2026-10-11 UTC: p95 508ms2026-10-12 UTC: p95 375ms2026-10-13 UTC: p95 459ms2026-10-14 UTC: p95 460ms
Sep 15Sep 29Oct 14
Canada
496msp95 · 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-15 UTC: p95 477ms2026-09-16 UTC: p95 521ms2026-09-17 UTC: p95 482ms2026-09-18 UTC: p95 313ms2026-09-19 UTC: p95 505ms2026-09-20 UTC: p95 436ms2026-09-21 UTC: p95 427ms2026-09-22 UTC: p95 413ms2026-09-23 UTC: p95 518ms2026-09-24 UTC: p95 502ms2026-09-25 UTC: p95 736ms2026-09-26 UTC: p95 509ms2026-09-27 UTC: p95 466ms2026-09-28 UTC: p95 443ms2026-09-29 UTC: p95 510ms2026-09-30 UTC: p95 499ms2026-10-01 UTC: p95 389ms2026-10-02 UTC: p95 482ms2026-10-03 UTC: p95 524ms2026-10-04 UTC: p95 495ms2026-10-05 UTC: p95 448ms2026-10-06 UTC: p95 586ms2026-10-07 UTC: p95 422ms2026-10-08 UTC: p95 339ms2026-10-09 UTC: p95 331ms2026-10-10 UTC: p95 318ms2026-10-11 UTC: p95 388ms2026-10-12 UTC: p95 341ms2026-10-13 UTC: p95 468ms2026-10-14 UTC: p95 496ms
Sep 15Sep 29Oct 14
UK
346msp95 · 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-15 UTC: p95 642ms2026-09-16 UTC: p95 585ms2026-09-17 UTC: p95 678ms2026-09-18 UTC: p95 552ms2026-09-19 UTC: p95 605ms2026-09-20 UTC: p95 634ms2026-09-21 UTC: p95 655ms2026-09-22 UTC: p95 643ms2026-09-23 UTC: p95 622ms2026-09-24 UTC: p95 751ms2026-09-25 UTC: p95 671ms2026-09-26 UTC: p95 704ms2026-09-27 UTC: p95 292ms2026-09-28 UTC: p95 402ms2026-09-29 UTC: p95 375ms2026-09-30 UTC: p95 561ms2026-10-01 UTC: p95 502ms2026-10-02 UTC: p95 461ms2026-10-03 UTC: p95 408ms2026-10-04 UTC: p95 355ms2026-10-05 UTC: p95 446ms2026-10-06 UTC: p95 477ms2026-10-07 UTC: p95 315ms2026-10-08 UTC: p95 292ms2026-10-09 UTC: p95 384ms2026-10-10 UTC: p95 392ms2026-10-11 UTC: p95 143ms2026-10-12 UTC: p95 197ms2026-10-13 UTC: p95 383ms2026-10-14 UTC: p95 346ms
Sep 15Sep 29Oct 14
Southeast Asia
951msp95 · 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-15 UTC: p95 804ms2026-09-16 UTC: p95 754ms2026-09-17 UTC: p95 775ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 580ms2026-09-20 UTC: p95 664ms2026-09-21 UTC: p95 974ms2026-09-22 UTC: p95 929ms2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 896ms2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 629ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 867ms2026-10-06 UTC: p95 942ms2026-10-07 UTC: p95 741ms2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 792ms2026-10-11 UTC: p95 707ms2026-10-12 UTC: p95 946ms2026-10-13 UTC: p95 564ms2026-10-14 UTC: p95 951ms
Sep 15Sep 29Oct 14
Australia
1.2sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.7s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 575ms2026-09-22 UTC: p95 470ms2026-09-23 UTC: p95 560ms2026-09-24 UTC: p95 515ms2026-09-25 UTC: p95 309ms2026-09-26 UTC: p95 276ms2026-09-27 UTC: p95 458ms2026-09-28 UTC: p95 458ms2026-09-29 UTC: p95 448ms2026-09-30 UTC: p95 555ms2026-10-01 UTC: p95 536ms2026-10-02 UTC: p95 514ms2026-10-03 UTC: p95 412ms2026-10-04 UTC: p95 645ms2026-10-05 UTC: p95 860ms2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 576ms2026-10-08 UTC: p95 650ms2026-10-09 UTC: p95 562ms2026-10-10 UTC: p95 472ms2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.2s
Sep 15Sep 29Oct 14
South America
732msp95 · 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-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 982ms2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 732ms
Sep 15Sep 29Oct 14

Check your own site while you wait on Signal

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 Signal. It cannot diagnose Signal's own systems.

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: 186msstatus code: 200checked: Oct 14, 2026, 4:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Signal normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 536msstatus code: 200checked: Oct 14, 2026, 4:57 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Signal normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 240msstatus code: 200checked: Oct 14, 2026, 4:59 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Signal normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 266msstatus code: 200checked: Oct 14, 2026, 4:52 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Signal normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 585msstatus code: 200checked: Oct 14, 2026, 4:52 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Signal 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: 87msstatus code: 200checked: Oct 14, 2026, 4:58 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Signal normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 193msstatus code: 200checked: Oct 14, 2026, 4:52 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Signal 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: 940msstatus code: 200checked: Oct 14, 2026, 4:55 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Signal normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 348msstatus code: 200checked: Oct 14, 2026, 4:51 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Signal normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 374msstatus code: 200checked: Oct 14, 2026, 4:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Signal 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 Signal, 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 Signal yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Signal.

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

We have been measuring Signal since August 20, 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 Signal covering any window you pick, with our check readings and Signal's own claim at the time, side by side.

Full check history for Signal: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

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

The badge shows the share of our checks that passed 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 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 Signal down?", https://realuptime.io/outages/signal. 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.

How our checks compare with Signal's stated SLA

At or above your target

Our checks of Signal failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Signal'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

secondary
https://status.signal.org/
primary
https://signal.org/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: signal.org

RealUptime is not affiliated with Signal; the name identifies what we checked, and nothing here speaks for Signal's own team. We send a single web request to Signal from 10 regions on our own schedule and time the response. We do not see inside Signal's systems, do not use an account or real transaction, and are not the same signal Signal's own team has access to. Treat this as one external data point, not a verdict. What we check for Signal is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Read the full methodology.