No reported issuesAn email when it goes down, and when it’s back.
As of 03:28 UTC on 12 November 2026, Rinkel's status page reports no issues. Its last reported problem was on 5 November 2026: “Issue with outbound calls via third-party provider”, major outage, for 21 h 50 min from 10:18 UTC.
- Last problem
- 5 Nov · 21 h 50 min
- Problems, last 30 days
- 1
- Typical incident
- 21 h 50 min
- Longest in 90 days
- 21 h 50 min · 5 Nov
Uptime
Rinkel, last 30 days
96.87 %
Biggest dip: Rinkel, 21.8 h of major outage on Nov 5.
Incidents
Started in the last 7 days
0
This week Week before
No incidents this week. The last one: Rinkel, major outage on Nov 5.
Recovery
Median time back online
21 h 50 min
0 of 1 were over within an hour. Each dot is one incident; the dashed line is the median.
Components 6
All online
- API
- Outbound calls
- Inbound calls
- My Rinkel (Web)
- My Rinkel (App)
- Webhooks
Last 90 days
1 incident in 48 days tracked · no reported issues 98.1% of the time · typical incident 21 h 50 min
Recent incidents
Times in UTC
- Issue with outbound calls via third-party provider 21 h 50 min
Major outage
Having issues right now
Paribu Humanity (H) Yatırma ve Çekme İşlemleri
CriticalAWS · Bahrain (me-south-1) Region Availability
CriticalAWS · UAE (me-central-1) Region Availability
CriticalGW Sistemas O componente “SAAS Webtrans” e alguns outros componentes estão Inativos
Critical
Popular services
All servicesWhere this comes from
Stackpulse reads Rinkel’s official status page at status.rinkel.com every 5 minutes and keeps 90 days of what changed. We don’t test Rinkel ourselves, so a problem shows here once Rinkel reports it.
Stackpulse isn’t affiliated with Rinkel. Names and logos belong to their owners.
For agents and scripts
The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.