8 incidente Opteo înregistrate începând din ianuarie 2020, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.
We are currently experiencing issues with our API and are investigating why.
This is an issue with our caching database. Working on a fix.
This incident has been resolved.
The Google Ads API is experiencing some downtime. Due to our dependency for Google ads data the experience will be degraded until they come back online. Thanks for your patience
This incident has been resolved.
We are currently investigating issues causing this downtime
We are continuing to investigate this issue.
This incident has been resolved.
One of our servers is experiencing some downtime. We are currently investigating the issue and should be back online shortly. Check our status page for more information.
We have resolved the issue and will continue to monitor
We are working with our server provider to resolve this issue as swiftly as possible.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolves. We will continue to monitor the results over the coming days
Our Google Ads data provider, Google, is working to fix a bug affecting our services. Their internal team is working to resolve this issue.
Google has resolved their bug, and our services are now back online.
Since around 11:30am UTC, we have been experiencing database connectivity issues due to our database provider, AWS. We are monitoring AWS's progress with resolving this issue at https://status.aws.amazon.com/#EU_block.
We are continuing to monitor this issue.
Our database provider, Amazon AWS, has resolved their connectivity issues. But in doing so, they accidentally triggered a bug in their systems affecting our services. Their team is working to resolve this issue.
The incident has been resolved, and Opteo is back online.
Our web application provider is currently experiencing a partial outage. We'll be back up and running once they resolve this issue.
This incident has now been resolved. Apologies for any inconvenience.
