Türkçe

When your site goes down,
be the first to know.

Uptime monitoring, status pages and incident management in one product. We check your sites, APIs and servers as often as every 30 seconds; when something breaks, you hear about it before your customers do.

Status page includedChecks as often as every 30 seconds
Start for freeSee the product

Every 200 is a successful check, every column a day. The red column is the night of October 1: HTTP 503.

Whichever country your server is in, RintUp monitors it.

Notice it first.Then fix it together.

Uptime monitoring and status pages

Your sites, APIs, cron jobs and servers are checked as often as every 30 seconds. Your customers see the status on your own domain.
Payments APIUp
Marketing siteDown
Nightly backup (cron)Up
  • Nine check types, intervals down to 30 seconds
  • False-alarm rules and maintenance windows
  • Status page on your own domain, in Turkish and English
  • Email, SMS, Slack and six more channels
Explore uptime monitoring

Incident management and on-call

Alerts reach the right person, and the next one if nobody acknowledges. Incidents from your monitors and from your Grafana land in one list.
  1. 03:12:04Triggered. SMS: Ayşe, primary on-call
  2. 03:22:05Escalated. SMS and Slack: Mehmet
  3. 03:23:40Acknowledged. Mehmet, via the SMS link
  4. 03:59:12Resolved. 47 minutes
  • One incident list, deduplication and grouping
  • On-call schedules and escalation policies
  • One-click acknowledge from SMS and email
  • Move from PagerDuty by changing one address
Explore incident management

A check every 30 seconds.Every result on one screen.

RintUp
  • Monitors
  • Servers
  • Incidents
  • Status pages
  • Notifications
  • Team
  • Settings

Monitors

6 monitors, last updated 14:05
Up
2
Down
1
Slow
1
Average response
412 ms
Sample monitor list
MonitorStatusResponseUptimeLast 30 daysLast check
Marketing site
https://www.ornek.com
Down—98.41%
14:04
Authentication
https://auth.ornek.com/status
Slow2,410 ms99.62%
14:05
Reporting database
tcp://db.ornek.com:5432
Maintenance—99.91%
14:00
Payments API
https://api.ornek.com/health
Up182 ms99.98%
14:05
Nightly backup (cron)
heartbeat, daily at 03:00
Up—100.00%
03:00
Legacy dashboard
https://legacy.ornek.com
Paused—99.12%
2 days ago
MonitorsPayments API

Payments API

https://api.ornek.com/health

Up
Response time
182 ms
Last check
14:05
Interval
30 s
90 days ago99.98% uptimeToday
Response time, last 24 hours
24 hours ago12 hours agoNow

Uptime monitoring.Nine check types, one dashboard.

Whatever you need to watch

Check intervals start at 30 seconds, depending on your plan. Passwords and custom headers are stored encrypted and never shown in plain text.
HTTP(S)
Status code, keyword, custom headers and body, Basic Auth, redirects
TCP
Is the port open, connection time
DNS
Does the record resolve, expected value
ICMP
Reachability and latency via ping
TLS
Chain and name validation; an invalid chain counts as “down”
RDAP
Domain expiry and nameserver changes
Heartbeat
Alert when a cron job doesn’t call in on time
Page Speed
Page performance and threshold
Agent
CPU, memory, disk and network on Linux servers
IP list
rintup.com/ips for your firewall, fixed User-Agent

No false alarms

You choose how many locations and how many consecutive checks must confirm an outage.
Confirmations
3 checks
Trigger delay
60 s
Maintenance window
Sun 02:00–04:00

SSL and domains

Chain and name validation; warnings 30, 14, 7 and 1 days before expiry. Your domain is tracked via RDAP.
8 days*.ornek.com certificate
  1. 30 days
  2. 14 days
  3. 1 days

Cron jobs

A unique address for every job. If the call doesn’t arrive on time, an alert goes out.
gece-yedegi
daily at 03:00
  1. Mon: called in
  2. Tue: called in
  3. Wed: called in
  4. Thu: called in
  5. Fri: called in
  6. Sat: called in
  7. Sun: missed
No call on Sunday at 03:00

Linux servers

A single-file agent with no dependencies installs with one command. If the server goes silent, you get an alert too.
CPU38%
Memory71%
Disk91%
Black line: the threshold you set, 85%.

Reports and history

Weekly and monthly email reports, incident history, CSV export.
  • 100%24 hours
  • 99.98%7 days
  • 99.96%30 days
  • 99.94%90 days
Sample: Payments API

Status page

status.yourcompany.com with automatic HTTPS. Announcements, double opt-in email subscriptions, password-protected internal pages, your own logo and color.
status.ornek.com
All systems operational
Website99.99%
Payments API99.93%
Mobile app100.00%
Subscribe to updates

Alerts on every channel

Use contact groups to choose which monitor alerts whom. “Still down” reminders and “recovered” notifications included.
  • Email
  • SMS (Netgsm)
  • Slack
  • Microsoft Teams
  • Discord
  • Telegram
  • Webhook (HMAC)
  • PagerDuty
  • Opsgenie
Even if the notification service goes down, alerts are delayed but never lost.

“RintUp: www.ornek.com is not responding (HTTP 503). Confirmed by three consecutive checks.”

03:12, the SMS on your phone

A check every 30 seconds, three failures, an alert at the ninetieth second

What happened between 03:12 and 03:59?Incident management and on-call, in the same product.

Right next to uptime and status pages. No separate on-call tool, no separate bill.

Incident management

One incident list

Monitor, server and external tool incidents in one place. Who has it and how long it has been open, at a glance.
Sample incident list
StatusIncidentSourceAssigneeDuration
TriggeredPayments API returns 503MonitorMehmet4 min
TriggeredHighErrorRate: paymentsAlertmanagerMehmet1 min
Acknowledgeddb-01 disk usage at 91%ServerAyşe18 min
AcknowledgedOrder queue is backing upWebhookAyşe22 min
ResolvedTypeError count increasedSentryZeynep12 min
ResolvedDashboard response time upGrafanaZeynep9 min
4 open incidents, 2 not yet acknowledged. Sample data.

Incident timeline

Who was notified, when and on which channel; who acknowledged. One click turns an incident into a status page announcement.
  1. 03:12:04Triggered. Payments API HTTP 503
  2. 03:12:05SMS and email: Ayşe, primary on-call
  3. 03:22:05Escalated. Not acknowledged within 10 minutes
  4. 03:22:06SMS and Slack: Mehmet, secondary on-call
  5. 03:23:40Acknowledged. Mehmet, via the SMS link
  6. 03:31:10Note: “Issue at the payment provider, we’re on it.”
  7. 03:59:12Resolved. Duration 47 minutes
  8. 04:01:30Status page announcement published

No alert storms

Alerts from the same problem are collected into one incident. You set the grouping rules.
  • HTTP 503×6
  • HighErrorRate×5
  • Latency p95×3
14
alerts
1
incident

MTTA and MTTR

Your average time to acknowledge and resolve, week by week.
MTTA
2 min 40 s
MTTR
31 min
Sample data, MTTR over the last 8 weeks

Easy move from PagerDuty

Any tool with a PagerDuty integration connects by changing just the event address. Alertmanager, Grafana and a generic webhook are ready too.
- events.pagerduty.com/v2/enqueue+ events.rintup.com/v2/enqueue
  • Datadog
  • Zabbix
  • Sentry
  • Alertmanager
  • Grafana
  • Webhook

On-call and escalation

On-call schedule

Daily, weekly or custom rotations. Handoff time, layers, overrides, working-hours restrictions. Feeds into your Google and Outlook calendar.
Primary
AyşeZeynepMehmet
Secondary
MehmetGapZeynep
Gap in secondary on-call on ThursdayHandoff daily at 09:00. Dashed frame: override.

Escalation policy

An unacknowledged incident moves up to the next level. The target can be a person, a schedule or a contact group.
  1. Primary on-callSchedule: Infrastructure, primary
    If not acknowledged within 10 minutes
  2. Secondary on-callSchedule: Infrastructure, secondary
    If not acknowledged within 10 minutes
  3. Infrastructure teamContact group, 4 people
Repeat twice until acknowledged

Your own notification rules

Everyone picks their own order. A separate rule for low-urgency incidents.
  • 0 minEmail
  • 2 minSMS
  • 10 minSMS, again
  • Low urgencyEmail only

One-click acknowledge

The link in SMS and email doesn’t ask for a password at night. Email scanners prefetching links can’t acknowledge by accident.
RintUp: Payments API is down (HTTP 503). To acknowledge: rintup.com/a/ria_7Kp…
Payments API is downist-1, HTTP 503, for 4 minutes
With buttons in Slack and Telegram

“RintUp: www.ornek.com is up again. Downtime: 47 minutes.”

03:59, the second SMS

The 90-day bar on your status page updated itself too

Team and security.Designed for business teams from day one.

Two-factor authentication

Sign in with your TOTP app, recovery codes included. Unverified accounts can’t sign in.

Roles and permissions

Workspaces, invitations and role-based permissions.
  • Ayşeowner
  • Mehmetadmin
  • Zeynepmember
  • Support teamviewer

Audit log

Who did what, and when. See open sessions and sign them out.
  • 14:02 Ayşe edited a monitor: Payments API
  • 13:47 Mehmet invited a member: zeynep@ornek.com
  • 13:10 Zeynep created an API key
  • 12:58 Ayşe signed out a session

Your secrets, encrypted

Monitor passwords, custom headers and channel secrets are encrypted with AES-256-GCM under Vault (OpenBao) key management, and keys are rotated. Never shown in plain text.
Custom header: Authorization
••••••••••••••Encrypted

Your internal network and your data

Our checks can’t be pointed at internal networks, cloud metadata addresses or local addresses, and DNS rebinding can’t get around that. Tenants are isolated in the application and in the database.
  • SSRF protection
  • Row-level security
  • rintup.com/ips
  • RintUp/1.0
  • Encrypted backups

Vibe coding?Tell your assistant “monitor this”.

$ codex mcp add rintup --url https://mcp.rintup.com/mcp
$ codex mcp login rintup
✓ Signed in via the browser

› Monitor the API routes in this project
  Found 6 routes: /health, /api/orders,
  /api/payments …
  I suggest 6 HTTP monitors. Create them?

› Why did it go down last night?
  At 03:12 /api/payments returned 503,
  it lasted 47 minutes.

Remote MCP server

Sign in through the browser from Codex, Claude Code, Claude.ai, Cursor and VS Code. 21 tools.
  • “Monitor the API routes in this project.”
  • “Why did it go down last night?”
  • “Open a status page.”
The content of the sites you monitor never goes to the AI.

Connected apps

See which assistant can access what, and remove it with one click.
  • Codexread and write
  • Cursorread only
Deletions always ask for confirmation.

REST API

With API keys. One error format, machine-readable error codes, messages in Turkish and English. A “Try it” button in the OpenAPI reference.
API docsMCP setup

A simple API

One request per monitor; only the type and the address are required. Every list paginates the same way, and updates are partial with PATCH.
PATCH /api/v1/monitors/<id>
{ "intervalSeconds": 30 }
API quickstart

No commitment.Always keeping watch.

  • Pro

    Products with customers, agencies and small teams.

    ₺899 / month

    • 200 monitors, intervals down to 30 seconds
    • 10 status pages on your own domain
    • 10 members
    • 250 SMS per month
    • 90-day data retention
    • 1 on-call schedule, 1 escalation policy

  • TeamRecommended

    Growing teams and companies.

    ₺2,499 / month

    • 1,000 monitors, intervals down to 30 seconds
    • Unlimited status pages on your own domain
    • Unlimited members
    • 1,000 SMS per month
    • 90-day data retention
    • Unlimited on-call schedules and policies

  • Free

    Personal projects and your first site.

    ₺0 / month

    • 10 monitors, 5-minute interval
    • 1 status page
    • 7-day data retention

  • Starter

    Startups with a few sites.

    ₺299 / month

    • 50 monitors, 1-minute interval
    • 3 status pages
    • 3 members
    • 50 SMS per month
    • 30-day data retention

Need more?

Let’s talk about custom limits and contracts. All plans are paid by card, in Turkish lira.

Start for freeTalk to sales

Questions.Answers.

  • What can RintUp monitor?

    HTTP and HTTPS addresses (status code, keyword, custom headers and body, Basic Auth), TCP ports, DNS records, ping, SSL certificates, domain expiry via RDAP, page speed and cron jobs. With a small agent it also monitors CPU, memory, disk and network on Linux servers.

  • Where are checks run from?

    Currently from our Istanbul location (ist-1). The outbound IP addresses to allow in your firewall and the current list of locations are on the Check IPs page; the User-Agent is always RintUp/1.0.

  • How do you prevent false alarms?

    You choose how many consecutive checks and how many locations must confirm an outage: any, majority or all. You can add a trigger delay, and no alerts go out during maintenance windows.

  • Which channels can notify me?

    Email, SMS (Netgsm), Slack, Discord, Microsoft Teams, Telegram, HMAC-signed webhooks, and delivery to PagerDuty and Opsgenie. Contact groups decide which monitor alerts whom.

  • Can the status page be on my own domain?

    Yes, on Pro and higher plans. Add one CNAME and one TXT record for status.yourcompany.com; the HTTPS certificate is issued automatically.

  • Can I set it up with my AI assistant?

    Yes. Add the remote MCP server at mcp.rintup.com/mcp to Codex, Claude Code, Claude.ai, Cursor or VS Code and sign in through the browser. Read and write permissions are separate, and deletions ask for confirmation.

  • Is my data safe?

    Secrets such as passwords and headers are encrypted with AES-256-GCM using Vault. Tenants are isolated both in the application and in the database. Our checks can’t be pointed at internal networks or cloud metadata addresses. How personal data is processed is described in the KVKK privacy notice.

  • Which plans include incident management and on-call?

    The incident list, deduplication and timeline are in every plan. On-call schedules and escalation policies: one of each on Pro, unlimited on Team.

  • How do I move from PagerDuty?

    Thanks to our PagerDuty-compatible event endpoint, tools such as Datadog, Zabbix and Sentry only need a new event address. Prometheus Alertmanager and Grafana connect directly as well.

  • How do I pay?

    By card, in Turkish lira; monthly or yearly.

  • Do I need a credit card for the free plan?

    No. You start right away on the free plan; payment details are only asked for when you move to a paid plan.

For more, see the API docs or our status page.