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 7 min ago. Last stored result reached it in 646 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 691 ms | 0 |
| Mon 20 | 0 | 0.0 | 762 ms | 0 |
| Mon 22 | 0 | 0.0 | 801 ms | 0 |
| Tue 00 | 0 | 0.0 | 660 ms | 0 |
| Tue 02 | 0 | 0.0 | 818 ms | 0 |
| Tue 05 | 0 | 0.0 | 689 ms | 0 |
| Tue 07 | 0 | 0.0 | 717 ms | 0 |
| Tue 09 | 0 | 0.0 | 721 ms | 0 |
| Tue 11 | 0 | 0.0 | 712 ms | 0 |
| Tue 13 | 0 | 0.0 | 638 ms | 0 |
| Tue 15 | 0 | 0.0 | 788 ms | 0 |
| Tue 18 | 0 | 0.0 | 691 ms | 0 |
| Tue 20 | 0 | 0.0 | 564 ms | 0 |
| Tue 22 | 0 | 0.0 | 877 ms | 0 |
| Wed 00 | 0 | 0.0 | 621 ms | 0 |
| Wed 03 | 0 | 0.0 | 644 ms | 0 |
| Wed 05 | 0 | 0.0 | 721 ms | 0 |
| Wed 07 | 0 | 0.0 | 661 ms | 0 |
| Wed 09 | 0 | 0.0 | 326 ms | 0 |
| Wed 12 | 0 | 0.0 | 772 ms | 0 |
| Wed 14 | 0 | 0.0 | 656 ms | 0 |
| Wed 16 | 0 | 0.0 | 588 ms | 0 |
| Wed 18 | 0 | 0.0 | 481 ms | 0 |
| Wed 20 | 0 | 0.0 | 625 ms | 0 |
| Wed 22 | 0 | 0.0 | 775 ms | 0 |
| Thu 01 | 0 | 0.0 | 888 ms | 0 |
| Thu 03 | 0 | 0.0 | 784 ms | 0 |
| Thu 05 | 0 | 0.0 | 597 ms | 0 |
| Thu 07 | 0 | 0.0 | 657 ms | 0 |
| Thu 09 | 0 | 0.0 | 723 ms | 0 |
| Thu 11 | 0 | 0.0 | 644 ms | 0 |
| Thu 13 | 0 | 0.0 | 678 ms | 0 |
| Thu 15 | 0 | 0.0 | 814 ms | 0 |
| Thu 16 | 0 | 0.0 | 716 ms | 0 |
| Thu 18 | 0 | 0.0 | 703 ms | 0 |
| Thu 20 | 0 | 0.0 | 700 ms | 0 |
| Thu 22 | 0 | 0.0 | 606 ms | 0 |
| Fri 00 | 0 | 0.0 | 706 ms | 0 |
| Fri 02 | 0 | 0.0 | 748 ms | 0 |
| Fri 04 | 0 | 0.0 | 708 ms | 0 |
| Fri 06 | 0 | 0.0 | 668 ms | 0 |
| Fri 08 | 0 | 0.0 | 354 ms | 0 |
| Fri 10 | 0 | 0.0 | 601 ms | 0 |
| Fri 11 | 0 | 0.0 | 665 ms | 0 |
| Fri 12 | 0 | 0.0 | 658 ms | 0 |
| Fri 14 | 0 | 0.0 | 728 ms | 0 |
| Fri 16 | 0 | 0.0 | 763 ms | 0 |
| Fri 18 | 0 | 0.0 | 747 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Rinkel 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 Rinkel goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rinkel alerts to Slack, Discord or a webhook — free.
Rinkel, at rinkel.com, is one of the Telecom services we monitor. Rinkel is the business phone provider for startups, entrepreneurs and teams. A virtual phone system from the comfort of your own mobile phone.
Rinkel publishes an official status page at status.rinkel.com; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 671 ms average, 354–847 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Rinkel incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
671 ms on average over the last 24 hours (354–847 ms).
Yes, at https://status.rinkel.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 Rinkel here at once, the problem is on Rinkel'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 Rinkel. 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.