User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
tinder.com · Social
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests tinder.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 24 ms · just now.
No status feed
Tinder does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Sun 11 | 0 | 0.0 | 352 ms | 0 |
| Sun 12 | 0 | 0.0 | 368 ms | 0 |
| Sun 13 | 0 | 0.0 | 328 ms | 0 |
| Sun 14 | 0 | 0.0 | 305 ms | 0 |
| Sun 15 | 0 | 0.0 | 227 ms | 0 |
| Sun 16 | 0 | 0.0 | 407 ms | 0 |
| Sun 17 | 0 | 0.0 | 224 ms | 0 |
| Sun 18 | 0 | 0.0 | 148 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for Tinder 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 Tinder goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Checks are succeeding and user reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.