api.sms4sats.com: sms4sats receive-sms other
https://api.sms4sats.com/v2/l402/ordersms4sats receive-sms other
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
99.8% avgResponse time
p50 1619ms · p95 1938msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 7/24/2026, 12:00:00 AM | 100% | 1 | 1585ms |
| 7/25/2026, 12:00:00 AM | 100% | 1 | 1826ms |
| 7/26/2026, 12:00:00 AM | 100% | 1 | 1681ms |
| 7/27/2026, 12:00:00 AM | 100% | 1 | 1619ms |
| 7/28/2026, 12:00:00 AM | 100% | 1 | 1614ms |
| 7/29/2026, 12:00:00 AM | 100% | 1 | 1605ms |
| 7/30/2026, 12:00:00 AM | 100% | 1 | 1575ms |
| 7/31/2026, 12:00:00 AM | 100% | 1 | 1741ms |
| 8/1/2026, 12:00:00 AM | 100% | 1 | 1606ms |
| 8/2/2026, 12:00:00 AM | 100% | 1 | 1589ms |
| 8/3/2026, 12:00:00 AM | 100% | 1 | 1593ms |
| 8/4/2026, 12:00:00 AM | 100% | 1 | 1541ms |
| 8/5/2026, 12:00:00 AM | 100% | 1 | 1640ms |
| 8/6/2026, 12:00:00 AM | 100% | 1 | 1579ms |
| 8/7/2026, 12:00:00 AM | 100% | 1 | 1750ms |
| 8/8/2026, 12:00:00 AM | 100% | 1 | 1780ms |
| 8/9/2026, 12:00:00 AM | 100% | 1 | 1612ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 1677ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 1795ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 1796ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 1595ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 2142ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 1559ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 1583ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 1636ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 1530ms |
| 8/19/2026, 12:00:00 AM | 100% | 20 | 1584ms |
| 8/20/2026, 12:00:00 AM | 95% | 21 | 1600ms |
| 8/21/2026, 12:00:00 AM | 100% | 22 | 1606ms |
| 8/22/2026, 12:00:00 AM | 100% | 1 | 1626ms |
- Availability
- 99
- Latency
- 51
- Security
- 99
- Transparency
- 24
- Activity
- not yet measured
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- BTC
- Networks
- lightning
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- CLOUDFLARENET
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.