User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
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 692 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 01 | 0 | 0.0 | 274 ms | 0 |
| Mon 03 | 0 | 0.0 | 390 ms | 0 |
| Mon 05 | 0 | 0.0 | 774 ms | 0 |
| Mon 08 | 0 | 0.0 | 4948 ms | 0 |
| Mon 10 | 0 | 0.0 | — | 0 |
| Mon 12 | 0 | 0.0 | — | 0 |
| Mon 14 | 0 | 0.0 | 6932 ms | 0 |
| Mon 16 | 0 | 0.0 | 540 ms | 0 |
| Mon 18 | 0 | 0.0 | 807 ms | 0 |
| Mon 20 | 0 | 0.0 | 635 ms | 0 |
| Mon 22 | 0 | 0.0 | 818 ms | 0 |
| Tue 00 | 0 | 0.0 | 715 ms | 0 |
| Tue 03 | 0 | 0.0 | 282 ms | 0 |
| Tue 05 | 0 | 0.0 | 821 ms | 0 |
| Tue 07 | 0 | 0.0 | 267 ms | 0 |
| Tue 09 | 0 | 0.0 | 726 ms | 0 |
| Tue 11 | 0 | 0.0 | 986 ms | 0 |
| Tue 13 | 0 | 0.0 | 576 ms | 0 |
| Tue 15 | 0 | 0.0 | 243 ms | 0 |
| Tue 18 | 0 | 0.0 | 406 ms | 0 |
| Tue 20 | 0 | 0.0 | 623 ms | 0 |
| Tue 22 | 0 | 0.0 | 873 ms | 0 |
| Wed 00 | 0 | 0.0 | 694 ms | 0 |
| Wed 03 | 0 | 0.0 | 790 ms | 0 |
| Wed 05 | 0 | 0.0 | 1134 ms | 0 |
| Wed 07 | 0 | 0.0 | 1074 ms | 0 |
| Wed 09 | 0 | 0.0 | 920 ms | 0 |
| Wed 10 | 0 | 0.0 | 259 ms | 0 |
| Wed 12 | 0 | 0.0 | 707 ms | 0 |
| Wed 14 | 0 | 0.0 | 917 ms | 0 |
| Wed 16 | 0 | 0.0 | 423 ms | 0 |
| Wed 18 | 0 | 0.0 | 934 ms | 0 |
| Wed 20 | 0 | 0.0 | 372 ms | 0 |
| Wed 22 | 0 | 0.0 | 282 ms | 0 |
| Thu 01 | 0 | 0.0 | 258 ms | 0 |
| Thu 03 | 0 | 0.0 | 773 ms | 0 |
| Thu 05 | 0 | 0.0 | 1037 ms | 0 |
| Thu 07 | 0 | 0.0 | 711 ms | 0 |
| Thu 09 | 0 | 0.0 | 261 ms | 0 |
| Thu 11 | 0 | 0.0 | 255 ms | 0 |
| Thu 13 | 0 | 0.0 | 857 ms | 0 |
| Thu 15 | 0 | 0.0 | 897 ms | 0 |
| Thu 17 | 0 | 0.0 | 827 ms | 0 |
| Thu 19 | 0 | 0.0 | 755 ms | 0 |
| Thu 21 | 0 | 0.0 | 260 ms | 0 |
| Thu 23 | 0 | 0.0 | 272 ms | 0 |
| Fri 01 | 0 | 0.0 | 684 ms | 0 |
| Fri 04 | 0 | 0.0 | 692 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for SMSCode 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 SMSCode goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SMSCode alerts to Slack, Discord or a webhook — free.
SMSCode, at smscode.gg, is one of the Telecom services we monitor. Buy virtual numbers to receive SMS online for OTP verification. Temporary phone numbers with real SIM, fast activation, 200+ countries. A reliable sms-activate alternative.
SMSCode publishes an official status page at status.smscode.gg; when we can read it, its incident level is folded into the status shown here.
Common problems for telecom services: no service or data, account and billing pages failing, and app sign-in problems.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 588 ms average, 255–897 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public SMSCode incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
588 ms on average over the last 24 hours (255–897 ms).
Yes, at https://status.smscode.gg.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For telecom services, watch for no service or data, account and billing pages failing, and app sign-in problems. If many people report SMSCode here at once, the problem is on SMSCode'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 SMSCode. 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.