User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Correction: On Nov 10, 2026 we retracted an incident report for Setu published in error on Nov 10, 2026. No outage occurred. Read the retraction →
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 39 min ago. Last stored result reached it in 253 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 199 ms | 0 |
| Mon 17 | 0 | 0.0 | 411 ms | 0 |
| Mon 19 | 0 | 0.0 | 178 ms | 0 |
| Mon 21 | 0 | 0.0 | 278 ms | 0 |
| Mon 23 | 0 | 0.0 | 170 ms | 0 |
| Tue 01 | 0 | 0.0 | 348 ms | 0 |
| Tue 04 | 0 | 0.0 | 218 ms | 0 |
| Tue 06 | 0 | 0.0 | 198 ms | 0 |
| Tue 08 | 0 | 0.0 | 181 ms | 0 |
| Tue 10 | 0 | 0.0 | 195 ms | 0 |
| Tue 12 | 0 | 0.0 | 376 ms | 0 |
| Tue 14 | 0 | 0.0 | 325 ms | 0 |
| Tue 17 | 0 | 0.0 | 169 ms | 0 |
| Tue 19 | 0 | 0.0 | 186 ms | 0 |
| Tue 21 | 0 | 0.0 | 370 ms | 0 |
| Tue 23 | 0 | 0.0 | 192 ms | 0 |
| Wed 02 | 0 | 0.0 | 193 ms | 0 |
| Wed 04 | 0 | 0.0 | 183 ms | 0 |
| Wed 06 | 0 | 0.0 | 219 ms | 0 |
| Wed 08 | 0 | 0.0 | 176 ms | 0 |
| Wed 11 | 0 | 0.0 | 227 ms | 0 |
| Wed 13 | 0 | 0.0 | 211 ms | 0 |
| Wed 15 | 0 | 0.0 | 138 ms | 0 |
| Wed 17 | 0 | 0.0 | 231 ms | 0 |
| Wed 19 | 0 | 0.0 | 352 ms | 0 |
| Wed 21 | 0 | 0.0 | 213 ms | 0 |
| Thu 00 | 0 | 0.0 | 209 ms | 0 |
| Thu 02 | 0 | 0.0 | 215 ms | 0 |
| Thu 04 | 0 | 0.0 | 192 ms | 0 |
| Thu 06 | 0 | 0.0 | 215 ms | 0 |
| Thu 08 | 0 | 0.0 | 161 ms | 0 |
| Thu 10 | 0 | 0.0 | 205 ms | 0 |
| Thu 12 | 0 | 0.0 | 236 ms | 0 |
| Thu 14 | 0 | 0.0 | 168 ms | 0 |
| Thu 16 | 0 | 0.0 | 209 ms | 0 |
| Thu 18 | 0 | 0.0 | 186 ms | 0 |
| Thu 20 | 0 | 0.0 | 328 ms | 0 |
| Thu 22 | 0 | 0.0 | 635 ms | 0 |
| Fri 00 | 0 | 0.0 | 201 ms | 0 |
| Fri 02 | 0 | 0.0 | 199 ms | 0 |
| Fri 04 | 0 | 0.0 | 188 ms | 0 |
| Fri 06 | 0 | 0.0 | 438 ms | 0 |
| Fri 08 | 0 | 0.0 | 411 ms | 0 |
| Fri 10 | 0 | 0.0 | 177 ms | 0 |
| Fri 11 | 0 | 0.0 | 368 ms | 0 |
| Fri 12 | 0 | 0.0 | 210 ms | 0 |
| Fri 14 | 0 | 0.0 | 160 ms | 0 |
| Fri 16 | 0 | 0.0 | 253 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Setu 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 Setu goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Setu alerts to Slack, Discord or a webhook — free.
We track Setu (setu.co) as part of the Cloud & developer group. Identity verification, onboarding, Account Aggregator, UPI collections and Bharat Connect APIs—the infrastructure behind India’s digital economy.
Setu publishes an official status page at status.setu.co; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 289 ms average, 160–635 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Setu incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
289 ms on average over the last 24 hours (160–635 ms).
Yes, at https://status.setu.co.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Setu here at once, the problem is on Setu'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 Setu. 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.