Skip to main content

Is Signal Down?

No — Signal is up
Signal's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 120 ms

Right now

We could not read Signal's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

signal.org from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
120 ms
Checked

By region

  • Amsterdam reachable, 118 ms
  • Dallas reachable, 207 ms
  • Newark reachable, 113 ms
  • Paris reachable, 69 ms
  • San Jose reachable, 172 ms
  • Stockholm reachable, 82 ms
  • Sydney reachable, 104 ms
  • Toronto reachable, 95 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam19 ms3 ms17 ms117 ms
Dallas140 ms2 ms11 ms206 ms
Newark49 ms3 ms8 ms112 ms
Paris16 ms3 ms8 ms68 ms
San Jose76 ms2 ms14 ms169 ms
Stockholm50 ms2 ms8 ms81 ms
Sydney48 ms1 ms7 ms103 ms
Toronto53 ms1 ms10 ms94 ms
We check that signal.org loads, not every feature behind it. Test it yourself

History

Signal website availability

Measured by FlareWarden · signal.org

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
143ms

Last 30 days

91-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 29 checks
Oct 18: 100.00% uptime, 24 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of signal.org from multiple regions every 6 hours. Signal's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Signal does

Signal is an encrypted messenger run by a non-profit foundation, offering private messages, groups and calls with end-to-end encryption by default. People use it for conversations they consider sensitive, and often as their only channel with certain contacts, so an outage removes a line of communication that has no obvious substitute.

What an outage looks like

Messages stay marked as sending and never show as delivered. Incoming messages stop arriving, so a conversation looks quiet rather than broken. Voice and video calls fail to connect or drop on answer. Registering a new device or transferring to a new phone fails, which is the step that leaves people genuinely stuck rather than merely delayed.

What to do about it

Check status.signal.org, which reports whether Signal is operating rather than breaking the service into many components. Messages you send are queued on your device and deliver once the service returns, so avoid resending them repeatedly. Postpone changing phones or re-registering until the status page is clear, because that path needs Signal's servers.

Is it down for everyone, or just you?

If this page says Signal is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Signal outage FAQ

Are my messages lost if Signal goes down?
No. Messages you send are held on your device and delivered when the service returns, and messages sent to you are queued by Signal for delivery. The encryption model means Signal cannot read them regardless. What you lose is timeliness, not content, so resending the same message mostly produces duplicates for the recipient.
Is Signal down or has my contact blocked me?
Blocking produces messages that appear to send normally and are never delivered, with no error, which is deliberately indistinguishable from a delay. An outage affects everyone, so check status.signal.org and whether messages to other contacts are also stuck. If only one conversation is affected while others flow, the cause is not an incident.
Should I re-register or reinstall during an outage?
No, and this is the one action that can genuinely cost you. Registration requires Signal's servers, so reinstalling during an incident can leave you unable to complete setup, and reinstalling without a backup loses message history permanently. Wait for the status page to clear before touching the installation.
Does an outage affect the security of my messages?
No. Messages are end-to-end encrypted between devices, and an availability incident means servers cannot relay them rather than that anything is readable. Signal is designed so that the relay does not have access to content in the first place. The failure is delivery, and it has no bearing on privacy.
Why do calls fail when messages eventually arrive?
Calls need a real-time connection established through Signal's servers, while messages tolerate delay and can be queued. During a partial incident, messaging degrades gracefully and calling does not, so a call fails outright while a text arrives a minute late. Falling back to messages during a call outage usually works.

How we measure this

  • We request Signal's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Signal publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Signal itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Signal goes down

We check Signal every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required