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 49 min ago. Last stored result reached it in 680 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 564 ms | 0 |
| Tue 05 | 0 | 0.0 | 660 ms | 0 |
| Tue 07 | 0 | 0.0 | 531 ms | 0 |
| Tue 09 | 0 | 0.0 | 366 ms | 0 |
| Tue 11 | 0 | 0.0 | 675 ms | 0 |
| Tue 13 | 0 | 0.0 | 738 ms | 0 |
| Tue 15 | 0 | 0.0 | 726 ms | 0 |
| Tue 18 | 0 | 0.0 | 681 ms | 0 |
| Tue 20 | 0 | 0.0 | 743 ms | 0 |
| Tue 22 | 0 | 0.0 | 736 ms | 0 |
| Wed 00 | 0 | 0.0 | 699 ms | 0 |
| Wed 03 | 0 | 0.0 | 645 ms | 0 |
| Wed 05 | 0 | 0.0 | 611 ms | 0 |
| Wed 07 | 0 | 0.0 | 482 ms | 0 |
| Wed 09 | 0 | 0.0 | 557 ms | 0 |
| Wed 10 | 0 | 0.0 | 488 ms | 0 |
| Wed 12 | 0 | 0.0 | 690 ms | 0 |
| Wed 14 | 0 | 0.0 | 750 ms | 0 |
| Wed 16 | 0 | 0.0 | 729 ms | 0 |
| Wed 18 | 0 | 0.0 | 648 ms | 0 |
| Wed 20 | 0 | 0.0 | 738 ms | 0 |
| Wed 22 | 0 | 0.0 | 594 ms | 0 |
| Thu 01 | 0 | 0.0 | 519 ms | 0 |
| Thu 03 | 0 | 0.0 | 451 ms | 0 |
| Thu 05 | 0 | 0.0 | 782 ms | 0 |
| Thu 07 | 0 | 0.0 | 647 ms | 0 |
| Thu 09 | 0 | 0.0 | 610 ms | 0 |
| Thu 11 | 0 | 0.0 | 928 ms | 0 |
| Thu 13 | 0 | 0.0 | 487 ms | 0 |
| Thu 15 | 0 | 0.0 | 480 ms | 0 |
| Thu 17 | 0 | 0.0 | 634 ms | 0 |
| Thu 19 | 0 | 0.0 | 656 ms | 0 |
| Thu 21 | 0 | 0.0 | 855 ms | 0 |
| Thu 22 | 0 | 0.0 | 874 ms | 0 |
| Fri 00 | 0 | 0.0 | 429 ms | 0 |
| Fri 02 | 0 | 0.0 | 664 ms | 0 |
| Fri 04 | 0 | 0.0 | 804 ms | 0 |
| Fri 06 | 0 | 0.0 | 998 ms | 0 |
| Fri 08 | 0 | 0.0 | 614 ms | 0 |
| Fri 11 | 0 | 0.0 | 695 ms | 0 |
| Fri 13 | 0 | 0.0 | 647 ms | 0 |
| Fri 15 | 0 | 0.0 | 572 ms | 0 |
| Fri 17 | 0 | 0.0 | 583 ms | 0 |
| Fri 19 | 0 | 0.0 | 633 ms | 0 |
| Fri 20 | 0 | 0.0 | 617 ms | 0 |
| Fri 21 | 0 | 0.0 | 705 ms | 0 |
| Fri 23 | 0 | 0.0 | 605 ms | 0 |
| Sat 01 | 0 | 0.0 | 680 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 Telerivet 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 Telerivet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Telerivet alerts to Slack, Discord or a webhook — free.
Telerivet, at telerivet.com, is one of the Telecom services we monitor. Send, automate, and orchestrate communications across SMS, WhatsApp, Viber, voice, USSD, and more in 150+ countries. Built for teams of any size, in any sector.
Telerivet publishes an official status page at status.telerivet.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with telecom services: no service or data, account and billing pages failing, and app sign-in problems.
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: 663 ms average, 530–998 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Telerivet incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
663 ms on average over the last 24 hours (530–998 ms).
Yes, at https://status.telerivet.com.
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 Telerivet here at once, the problem is on Telerivet'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 Telerivet. 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.