User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 53 min ago. Last stored result reached it in 105 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 261 ms | 0 |
| Mon 23 | 0 | 0.0 | 196 ms | 0 |
| Tue 01 | 0 | 0.0 | 160 ms | 0 |
| Tue 03 | 0 | 0.0 | 126 ms | 0 |
| Tue 05 | 0 | 0.0 | 81 ms | 0 |
| Tue 07 | 0 | 0.0 | 143 ms | 0 |
| Tue 09 | 0 | 0.0 | 103 ms | 0 |
| Tue 12 | 0 | 0.0 | 23 ms | 0 |
| Tue 14 | 0 | 0.0 | 202 ms | 0 |
| Tue 16 | 0 | 0.0 | 179 ms | 0 |
| Tue 18 | 0 | 0.0 | 152 ms | 0 |
| Tue 21 | 0 | 0.0 | 53 ms | 0 |
| Tue 23 | 0 | 0.0 | 133 ms | 0 |
| Wed 01 | 0 | 0.0 | 134 ms | 0 |
| Wed 03 | 0 | 0.0 | 122 ms | 0 |
| Wed 05 | 0 | 0.0 | 165 ms | 0 |
| Wed 08 | 0 | 0.0 | 140 ms | 0 |
| Wed 10 | 0 | 0.0 | 184 ms | 0 |
| Wed 12 | 0 | 0.0 | 129 ms | 0 |
| Wed 14 | 0 | 0.0 | 49 ms | 0 |
| Wed 16 | 0 | 0.0 | 144 ms | 0 |
| Wed 18 | 0 | 0.0 | 104 ms | 0 |
| Wed 21 | 0 | 0.0 | 129 ms | 0 |
| Wed 23 | 0 | 0.0 | 126 ms | 0 |
| Thu 01 | 0 | 0.0 | 102 ms | 0 |
| Thu 03 | 0 | 0.0 | 96 ms | 0 |
| Thu 05 | 0 | 0.0 | 127 ms | 0 |
| Thu 07 | 0 | 0.0 | 115 ms | 0 |
| Thu 09 | 0 | 0.0 | 132 ms | 0 |
| Thu 11 | 0 | 0.0 | 83 ms | 0 |
| Thu 13 | 0 | 0.0 | 58 ms | 0 |
| Thu 15 | 0 | 0.0 | 99 ms | 0 |
| Thu 18 | 0 | 0.0 | 88 ms | 0 |
| Thu 20 | 0 | 0.0 | 32 ms | 0 |
| Thu 22 | 0 | 0.0 | 211 ms | 0 |
| Fri 00 | 0 | 0.0 | 195 ms | 0 |
| Fri 02 | 0 | 0.0 | 170 ms | 0 |
| Fri 04 | 0 | 0.0 | 137 ms | 0 |
| Fri 06 | 0 | 0.0 | 57 ms | 0 |
| Fri 08 | 0 | 0.0 | 237 ms | 0 |
| Fri 09 | 0 | 0.0 | 135 ms | 0 |
| Fri 11 | 0 | 0.0 | 164 ms | 0 |
| Fri 12 | 0 | 0.0 | 80 ms | 0 |
| Fri 14 | 0 | 0.0 | 201 ms | 0 |
| Fri 16 | 0 | 0.0 | 102 ms | 0 |
| Fri 18 | 0 | 0.0 | 110 ms | 0 |
| Fri 20 | 0 | 0.0 | 161 ms | 0 |
| Fri 22 | 0 | 0.0 | 105 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 Ingresso 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 Ingresso goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ingresso alerts to Slack, Discord or a webhook — free.
We track Ingresso (ingresso.co.uk) as part of the Productivity group. Unlock global ticket sales with ingresso's powerful API, connecting you to over 1 billion consumers for seamless growth and increased revenue.
Ingresso publishes an official status page at status.ingresso.co.uk; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
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: 143 ms average, 57–237 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 Ingresso incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
143 ms on average over the last 24 hours (57–237 ms).
Yes, at https://status.ingresso.co.uk.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Ingresso here at once, the problem is on Ingresso'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 Ingresso. 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.