User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
secomea.com · Productivity
Something is off: the vendor has scheduled maintenance. Official status: Service Under Maintenance
Estimated fix: Past Secomea outages lasted 18 min (median, typically 14 min–32 min; 3 outages we recorded).
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 935 ms · 1 min ago.
Maintenance
Service Under Maintenance Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 2 | 0 | 0.0 | 1922 ms | 0 |
| Nov 2 | 0 | 0.0 | 1518 ms | 0 |
| Nov 2 | 0 | 0.0 | 1802 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.
One report per service every 10 minutes from this network. No account.
Get an email when Secomea goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Secomea alerts to Slack, Discord or a webhook — free.
Something is off: the vendor has scheduled maintenance. Official status: Service Under Maintenance
If Secomea is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Secomea's side.
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.