Skip to content

Outage tracker / Signal

Is Signal down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Signal from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Signal (since Aug 20, 2026).

our independent probeslive · checked Sep 3, 2026, 1:28 AM UTC
US-East469 msOperational
US-West267 msOperational
Europe72 msOperational
Asia-Pacific453 msOperational
their status pagetheir claim, not our reading

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

Signal response time, by region

US-East
759msp95 · 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-20 UTC: p95 742ms2026-08-21 UTC: p95 1.1s2026-08-22 UTC: p95 1.1s2026-08-23 UTC: p95 810ms2026-08-24 UTC: p95 799ms2026-08-25 UTC: p95 1.4s2026-08-26 UTC: p95 1.4s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 671ms2026-08-29 UTC: p95 766ms2026-08-30 UTC: p95 817ms2026-08-31 UTC: p95 605ms2026-09-01 UTC: p95 595ms2026-09-02 UTC: p95 773ms2026-09-03 UTC: p95 759ms
Aug 5Aug 19Sep 3
US-West
534msp95 · 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-20 UTC: p95 526ms2026-08-21 UTC: p95 520ms2026-08-22 UTC: p95 441ms2026-08-23 UTC: p95 410ms2026-08-24 UTC: p95 385ms2026-08-25 UTC: p95 553ms2026-08-26 UTC: p95 559ms2026-08-27 UTC: p95 612ms2026-08-28 UTC: p95 611ms2026-08-29 UTC: p95 525ms2026-08-30 UTC: p95 626ms2026-08-31 UTC: p95 594ms2026-09-01 UTC: p95 471ms2026-09-02 UTC: p95 464ms2026-09-03 UTC: p95 534ms
Aug 5Aug 19Sep 3
Europe
298msp95 · 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-20 UTC: p95 327ms2026-08-21 UTC: p95 280ms2026-08-22 UTC: p95 256ms2026-08-23 UTC: p95 432ms2026-08-24 UTC: p95 777ms2026-08-25 UTC: p95 550ms2026-08-26 UTC: p95 397ms2026-08-27 UTC: p95 368ms2026-08-28 UTC: p95 471ms2026-08-29 UTC: p95 409ms2026-08-30 UTC: p95 373ms2026-08-31 UTC: p95 383ms2026-09-01 UTC: p95 425ms2026-09-02 UTC: p95 370ms2026-09-03 UTC: p95 298ms
Aug 5Aug 19Sep 3
Asia-Pacific
749msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 322ms2026-08-21 UTC: p95 250ms2026-08-22 UTC: p95 261ms2026-08-23 UTC: p95 717ms2026-08-24 UTC: p95 784ms2026-08-25 UTC: p95 643ms2026-08-26 UTC: p95 755ms2026-08-27 UTC: p95 613ms2026-08-28 UTC: p95 491ms2026-08-29 UTC: p95 366ms2026-08-30 UTC: p95 372ms2026-08-31 UTC: p95 496ms2026-09-01 UTC: p95 620ms2026-09-02 UTC: p95 704ms2026-09-03 UTC: p95 749ms
Aug 5Aug 19Sep 3

Is it Signal, 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 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 we measured, and what people reported

  • US-East
    Operationallatency: 469msstatus code: 200checked: Sep 3, 2026, 1:03 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
    Operationallatency: 267msstatus code: 200checked: Sep 3, 2026, 1:01 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.
  • Europe
    Operationallatency: 72msstatus code: 200checked: Sep 3, 2026, 1:28 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.
  • Asia-Pacific
    Operationallatency: 453msstatus code: 200checked: Sep 3, 2026, 1:09 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.
  • US-Central
    Not monitored from this regionSignal is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionSignal is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionSignal is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionSignal is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionSignal is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionSignal is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

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 outages

No outages on record yet for Signal.

measured 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 measurements and Signal's own claim at the time, side by side.

Full availability history for Signal: 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 Signal, and again when they can reach it again. That is our own measurement from ten regions, not Signal'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

Signal uptime measured by RealUptimeLive, from this page's own readings.
[![Signal uptime measured by RealUptime](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 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 Signal's SLA implies, from our measurement

At or above your target

We measured none of downtime for Signal over the 337h 30m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

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

This is computed from our own probe measurements, 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

primaryfunctional
https://status.signal.org/api/v2/status.json
secondary
https://signal.org/
RealUptime is not affiliated with Signal; the name identifies what we measured, and nothing here speaks for Signal's own team. We send a single web request to Signal from 4 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. At least one endpoint we check for Signal 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. Signal operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.