User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 738 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 710 ms | 0 |
| Mon 20 | 0 | 0.0 | 699 ms | 0 |
| Mon 22 | 0 | 0.0 | 676 ms | 0 |
| Tue 00 | 0 | 0.0 | 705 ms | 0 |
| Tue 02 | 0 | 0.0 | 807 ms | 0 |
| Tue 04 | 0 | 0.0 | 982 ms | 0 |
| Tue 07 | 0 | 0.0 | 739 ms | 0 |
| Tue 09 | 0 | 0.0 | 813 ms | 0 |
| Tue 11 | 0 | 0.0 | 632 ms | 0 |
| Tue 13 | 0 | 0.0 | 639 ms | 0 |
| Tue 15 | 0 | 0.0 | 822 ms | 0 |
| Tue 17 | 0 | 0.0 | 736 ms | 0 |
| Tue 20 | 0 | 0.0 | 692 ms | 0 |
| Tue 22 | 0 | 0.0 | 667 ms | 0 |
| Wed 00 | 0 | 0.0 | 888 ms | 0 |
| Wed 02 | 0 | 0.0 | 758 ms | 0 |
| Wed 05 | 0 | 0.0 | 237 ms | 0 |
| Wed 07 | 0 | 0.0 | 681 ms | 0 |
| Wed 09 | 0 | 0.0 | 1254 ms | 0 |
| Wed 11 | 0 | 0.0 | 896 ms | 0 |
| Wed 14 | 0 | 0.0 | 820 ms | 0 |
| Wed 16 | 0 | 0.0 | 764 ms | 0 |
| Wed 18 | 0 | 0.0 | 642 ms | 0 |
| Wed 20 | 0 | 0.0 | 797 ms | 0 |
| Wed 22 | 0 | 0.0 | 960 ms | 0 |
| Thu 00 | 0 | 0.0 | 961 ms | 0 |
| Thu 03 | 0 | 0.0 | 612 ms | 0 |
| Thu 05 | 0 | 0.0 | 847 ms | 0 |
| Thu 07 | 0 | 0.0 | 909 ms | 0 |
| Thu 09 | 0 | 0.0 | 780 ms | 0 |
| Thu 11 | 0 | 0.0 | 766 ms | 0 |
| Thu 13 | 0 | 0.0 | 645 ms | 0 |
| Thu 15 | 0 | 0.0 | 847 ms | 0 |
| Thu 17 | 0 | 0.0 | 871 ms | 0 |
| Thu 19 | 0 | 0.0 | 710 ms | 0 |
| Thu 21 | 0 | 0.0 | 693 ms | 0 |
| Thu 23 | 0 | 0.0 | 776 ms | 0 |
| Fri 01 | 0 | 0.0 | 857 ms | 0 |
| Fri 03 | 0 | 0.0 | 801 ms | 0 |
| Fri 04 | 0 | 0.0 | 853 ms | 0 |
| Fri 06 | 0 | 0.0 | 928 ms | 0 |
| Fri 08 | 0 | 0.0 | 628 ms | 0 |
| Fri 10 | 0 | 0.0 | 742 ms | 0 |
| Fri 12 | 0 | 0.0 | 775 ms | 0 |
| Fri 14 | 0 | 0.0 | 791 ms | 0 |
| Fri 16 | 0 | 0.0 | 821 ms | 0 |
| Fri 18 | 0 | 0.0 | 717 ms | 0 |
| Fri 20 | 0 | 0.0 | 738 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Santiment yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Santiment goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Santiment alerts to Slack, Discord or a webhook — free.
Santiment is listed in our Money category and checked at santiment.net. We provide tools for crypto research to analyze markets and find data-driven opportunities to optimize your investing. Dive in and explore our on-chain, social and development data.
Santiment publishes an official status page at status.santiment.net; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 786 ms average, 628–928 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Santiment incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
786 ms on average over the last 24 hours (628–928 ms).
Yes, at https://status.santiment.net.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Santiment here at once, the problem is on Santiment's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Santiment. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.