System Status
Last manual check: May 4, 2026 — TwoLine is in early launch and runs a manual status check daily. Automated status feed is on the roadmap for Q3 2026.
This page reports the current operational status of TwoLine's user-facing systems and the upstream SMS provider routes we depend on. For incident updates, follow @serhatdgn on X or email [email protected].
Current Status
Web dashboard — twoline.io
Login, wallet, rentals, inbox
Operational
Login, wallet, rentals, inbox
iOS app — App Store
Latest version available
Operational
Latest version available
Android app — Google Play
Latest version available
Operational
Latest version available
Stripe checkout
Card top-ups
Operational
Card top-ups
NOWPayments crypto
USDT, BTC, ETH top-ups
Operational
USDT, BTC, ETH top-ups
US SMS routes — primary + fallback
SMSPool primary, JuicySMS fallback
Operational
SMSPool primary, JuicySMS fallback
UK SMS routes
SMSPool + JuicySMS
Operational
SMSPool + JuicySMS
NL SMS routes
JuicySMS primary
Operational
JuicySMS primary
Status Legend
| Indicator | Meaning |
|---|---|
| Operational | System working normally; no known issues |
| Degraded | Slower than normal or partial functionality; investigation in progress |
| Outage | System unavailable; active incident |
Incident History
No incidents reported since launch (May 2026). When an incident occurs we publish here within 1 hour and post a follow-up summary within 24 hours of resolution.
How We Handle Incidents
- Detection: Manual checks daily plus user reports via email and X. Automated monitoring on the roadmap for Q3 2026.
- Notification: Active outages are posted on this page and on @serhatdgn within 1 hour.
- Mitigation: SMS provider outages route to fallback providers automatically (SMSPool ↔ JuicySMS).
- Refund: Verifications that failed due to confirmed downtime get automatic credit-back. See Refund & Dispute Policy.
- Post-mortem: Major incidents (>30 minutes user-visible impact) get a written post-mortem within 7 days, published on the blog.
Contact
Status questions or incident reports: [email protected]. Real-time incident updates: @serhatdgn on X.