User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is iLost 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 → ilost.co—
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 41 min ago. Last stored result reached it in 768 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 673 ms | 0 |
| Mon 17 | 0 | 0.0 | 765 ms | 0 |
| Mon 19 | 0 | 0.0 | 759 ms | 0 |
| Mon 21 | 0 | 0.0 | 856 ms | 0 |
| Mon 23 | 0 | 0.0 | 799 ms | 0 |
| Tue 01 | 0 | 0.0 | 803 ms | 0 |
| Tue 03 | 0 | 0.0 | 803 ms | 0 |
| Tue 05 | 0 | 0.0 | 784 ms | 0 |
| Tue 07 | 0 | 0.0 | 780 ms | 0 |
| Tue 10 | 0 | 0.0 | 757 ms | 0 |
| Tue 12 | 0 | 0.0 | 793 ms | 0 |
| Tue 14 | 0 | 0.0 | 770 ms | 0 |
| Tue 16 | 0 | 0.0 | 800 ms | 0 |
| Tue 18 | 0 | 0.0 | 838 ms | 0 |
| Tue 21 | 0 | 0.0 | 825 ms | 0 |
| Tue 23 | 0 | 0.0 | 779 ms | 0 |
| Wed 01 | 0 | 0.0 | 854 ms | 0 |
| Wed 03 | 0 | 0.0 | 745 ms | 0 |
| Wed 06 | 0 | 0.0 | 826 ms | 0 |
| Wed 08 | 0 | 0.0 | 743 ms | 0 |
| Wed 10 | 0 | 0.0 | 1486 ms | 0 |
| Wed 12 | 0 | 0.0 | 745 ms | 0 |
| Wed 14 | 0 | 0.0 | 791 ms | 0 |
| Wed 16 | 0 | 0.0 | 713 ms | 0 |
| Wed 19 | 0 | 0.0 | 815 ms | 0 |
| Wed 21 | 0 | 0.0 | 849 ms | 0 |
| Wed 23 | 0 | 0.0 | 752 ms | 0 |
| Thu 01 | 0 | 0.0 | 781 ms | 0 |
| Thu 03 | 0 | 0.0 | 779 ms | 0 |
| Thu 05 | 0 | 0.0 | 827 ms | 0 |
| Thu 07 | 0 | 0.0 | 778 ms | 0 |
| Thu 09 | 0 | 0.0 | 790 ms | 0 |
| Thu 11 | 0 | 0.0 | 855 ms | 0 |
| Thu 13 | 0 | 0.0 | 769 ms | 0 |
| Thu 16 | 0 | 0.0 | 807 ms | 0 |
| Thu 18 | 0 | 0.0 | 915 ms | 0 |
| Thu 20 | 0 | 0.0 | 760 ms | 0 |
| Thu 22 | 0 | 0.0 | 712 ms | 0 |
| Fri 00 | 0 | 0.0 | 761 ms | 0 |
| Fri 03 | 0 | 0.0 | 848 ms | 0 |
| Fri 05 | 0 | 0.0 | 814 ms | 0 |
| Fri 07 | 0 | 0.0 | 770 ms | 0 |
| Fri 09 | 0 | 0.0 | 858 ms | 0 |
| Fri 11 | 0 | 0.0 | 788 ms | 0 |
| Fri 13 | 0 | 0.0 | 804 ms | 0 |
| Fri 15 | 0 | 0.0 | 793 ms | 0 |
| Fri 17 | 0 | 0.0 | 725 ms | 0 |
| Fri 18 | 0 | 0.0 | 768 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live iLost 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 iLost yet. Outages of 10 minutes or more get their own page here.
Having trouble with iLost?
One report per service every 10 minutes from this network. No account.
Follow iLost
Get an email when iLost goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send iLost alerts to Slack, Discord or a webhook — free.
About iLost
We track iLost (ilost.co) as part of the Cloud & developer group. Connect organizations with their customers through efficient lost and found management
iLost publishes an official status page at status.ilost.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: 779 ms average, 712–858 ms range across 14 successful checks.
Questions
Is iLost down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was iLost last down?
We have not recorded a public iLost incident since monitoring began 7 days ago.
What is iLost's uptime?
From our own checks: 100% over 7 days of checks.
How fast does iLost respond?
779 ms on average over the last 24 hours (712–858 ms).
Does iLost have an official status page?
Yes, at https://status.ilost.co.
iLost 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report iLost here at once, the problem is on iLost'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 iLost. 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.