User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is s.id down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → home.s.id—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 1160 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 1446 ms | 0 |
| Tue 02 | 0 | 0.0 | 920 ms | 0 |
| Tue 04 | 0 | 0.0 | 1445 ms | 0 |
| Tue 07 | 0 | 0.0 | 976 ms | 0 |
| Tue 09 | 0 | 0.0 | 819 ms | 0 |
| Tue 11 | 0 | 0.0 | 1161 ms | 0 |
| Tue 13 | 0 | 0.0 | 944 ms | 0 |
| Tue 15 | 0 | 0.0 | 1734 ms | 0 |
| Tue 17 | 0 | 0.0 | 1378 ms | 0 |
| Tue 20 | 0 | 0.0 | 849 ms | 0 |
| Tue 22 | 0 | 0.0 | 1462 ms | 0 |
| Wed 00 | 0 | 0.0 | 1744 ms | 0 |
| Wed 02 | 0 | 0.0 | 820 ms | 0 |
| Wed 05 | 0 | 0.0 | 853 ms | 0 |
| Wed 07 | 0 | 0.0 | 841 ms | 0 |
| Wed 09 | 0 | 0.0 | 1458 ms | 0 |
| Wed 11 | 0 | 0.0 | 1489 ms | 0 |
| Wed 14 | 0 | 0.0 | 1397 ms | 0 |
| Wed 16 | 0 | 0.0 | 1409 ms | 0 |
| Wed 18 | 0 | 0.0 | 1456 ms | 0 |
| Wed 20 | 0 | 0.0 | 1453 ms | 0 |
| Wed 22 | 0 | 0.0 | 1431 ms | 0 |
| Thu 00 | 0 | 0.0 | 1444 ms | 0 |
| Thu 03 | 0 | 0.0 | 1446 ms | 0 |
| Thu 05 | 0 | 0.0 | 1015 ms | 0 |
| Thu 07 | 0 | 0.0 | 1607 ms | 0 |
| Thu 09 | 0 | 0.0 | 1457 ms | 0 |
| Thu 11 | 0 | 0.0 | 1540 ms | 0 |
| Thu 13 | 0 | 0.0 | 356 ms | 0 |
| Thu 15 | 0 | 0.0 | 1367 ms | 0 |
| Thu 17 | 0 | 0.0 | 1521 ms | 0 |
| Thu 19 | 0 | 0.0 | 856 ms | 0 |
| Thu 21 | 0 | 0.0 | 1655 ms | 0 |
| Thu 23 | 0 | 0.0 | 944 ms | 0 |
| Fri 01 | 0 | 0.0 | 4019 ms | 0 |
| Fri 03 | 0 | 0.0 | 898 ms | 0 |
| Fri 04 | 0 | 0.0 | 1038 ms | 0 |
| Fri 06 | 0 | 0.0 | 2495 ms | 0 |
| Fri 08 | 0 | 0.0 | 365 ms | 0 |
| Fri 10 | 0 | 0.0 | 1088 ms | 0 |
| Fri 11 | 0 | 0.0 | 916 ms | 0 |
| Fri 13 | 0 | 0.0 | 865 ms | 0 |
| Fri 15 | 0 | 0.0 | 1460 ms | 0 |
| Fri 17 | 0 | 0.0 | 1155 ms | 0 |
| Fri 18 | 0 | 0.0 | 864 ms | 0 |
| Fri 19 | 0 | 0.0 | 1384 ms | 0 |
| Fri 21 | 0 | 0.0 | 1349 ms | 0 |
| Fri 23 | 0 | 0.0 | 1160 ms | 0 |
Reliability
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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live s.id badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for s.id yet. Outages of 10 minutes or more get their own page here.
Having trouble with s.id?
One report per service every 10 minutes from this network. No account.
Follow s.id
Get an email when s.id goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send s.id alerts to Slack, Discord or a webhook — free.
About s.id
s.id is listed in our AI category and checked at home.s.id. Launch branded short links, campaign microsites, and dynamic QR codes from one platform. Built for marketing, growth, SaaS, and AI teams.
s.id publishes an official status page at status.s.id; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1317 ms average, 365–4019 ms range across 16 successful checks.
Questions
Is s.id down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was s.id last down?
We have not recorded a public s.id incident since monitoring began 8 days ago.
What is s.id's uptime?
From our own checks: 100% over 8 days of checks.
How fast does s.id respond?
1317 ms on average over the last 24 hours (365–4019 ms).
Does s.id have an official status page?
Yes, at https://status.s.id.
s.id not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report s.id here at once, the problem is on s.id'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 s.id. 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.