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 1 hr ago. Last stored result reached it in 50 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 04 | 0 | 0.0 | 226 ms | 0 |
| Tue 06 | 0 | 0.0 | 35 ms | 0 |
| Tue 08 | 0 | 0.0 | 102 ms | 0 |
| Tue 10 | 0 | 0.0 | 69 ms | 0 |
| Tue 13 | 0 | 0.0 | 50 ms | 0 |
| Tue 15 | 0 | 0.0 | 140 ms | 0 |
| Tue 17 | 0 | 0.0 | 42 ms | 0 |
| Tue 19 | 0 | 0.0 | 106 ms | 0 |
| Tue 22 | 0 | 0.0 | 100 ms | 0 |
| Wed 00 | 0 | 0.0 | 91 ms | 0 |
| Wed 02 | 0 | 0.0 | 104 ms | 0 |
| Wed 04 | 0 | 0.0 | 113 ms | 0 |
| Wed 06 | 0 | 0.0 | 119 ms | 0 |
| Wed 09 | 0 | 0.0 | 74 ms | 0 |
| Wed 11 | 0 | 0.0 | 25 ms | 0 |
| Wed 13 | 0 | 0.0 | 32 ms | 0 |
| Wed 15 | 0 | 0.0 | 66 ms | 0 |
| Wed 17 | 0 | 0.0 | 121 ms | 0 |
| Wed 20 | 0 | 0.0 | 34 ms | 0 |
| Wed 22 | 0 | 0.0 | 158 ms | 0 |
| Thu 00 | 0 | 0.0 | 58 ms | 0 |
| Thu 02 | 0 | 0.0 | 79 ms | 0 |
| Thu 04 | 0 | 0.0 | 90 ms | 0 |
| Thu 06 | 0 | 0.0 | 114 ms | 0 |
| Thu 08 | 0 | 0.0 | 94 ms | 0 |
| Thu 10 | 0 | 0.0 | 62 ms | 0 |
| Thu 12 | 0 | 0.0 | 76 ms | 0 |
| Thu 14 | 0 | 0.0 | 338 ms | 0 |
| Thu 16 | 0 | 0.0 | 343 ms | 0 |
| Thu 18 | 0 | 0.0 | 78 ms | 0 |
| Thu 21 | 0 | 0.0 | 89 ms | 0 |
| Thu 23 | 0 | 0.0 | 68 ms | 0 |
| Fri 01 | 0 | 0.0 | 64 ms | 0 |
| Fri 04 | 0 | 0.0 | 82 ms | 0 |
| Fri 06 | 0 | 0.0 | 223 ms | 0 |
| Fri 08 | 0 | 0.0 | 193 ms | 0 |
| Fri 10 | 0 | 0.0 | 50 ms | 0 |
| Fri 12 | 0 | 0.0 | 68 ms | 0 |
| Fri 14 | 0 | 0.0 | 29 ms | 0 |
| Fri 16 | 0 | 0.0 | 71 ms | 0 |
| Fri 17 | 0 | 0.0 | 70 ms | 0 |
| Fri 19 | 0 | 0.0 | 111 ms | 0 |
| Fri 20 | 0 | 0.0 | 190 ms | 0 |
| Fri 21 | 0 | 0.0 | 237 ms | 0 |
| Fri 22 | 0 | 0.0 | 77 ms | 0 |
| Sat 00 | 0 | 0.0 | 236 ms | 0 |
| Sat 01 | 0 | 0.0 | 133 ms | 0 |
| Sat 03 | 0 | 0.0 | 50 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 9 days of data so far, so the 90-day numbers fill in over time.
PIM PaaS - Scheduled Certificate Rotation
We will perform a scheduled certificate rotation on the cloud.akeneo.com subdomain for all PaaS instances. This maintenance operation should not trigger any downtime, and the certificate update should be transparent.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Akeneo 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 Akeneo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Akeneo alerts to Slack, Discord or a webhook — free.
Akeneo, at akeneo.com, is one of the Productivity services we monitor. Centralize, enrich, and syndicate product data to deliver consistent omnichannel experiences that drive sales.
Akeneo publishes an official status page at status.akeneo.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 126 ms average, 29–241 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Akeneo incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
126 ms on average over the last 24 hours (29–241 ms).
Yes, at https://status.akeneo.com.
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 Akeneo here at once, the problem is on Akeneo'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 Akeneo. 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.