Wakam Outage History

Started Aug 12, 2026, 04:00 PM UTC· resolved Aug 12, 2026, 06:47 PM UTC

1. investigating Aug 12, 2026, 04:52 PM UTC

   We are currently investigating this issue.

2. identified Aug 12, 2026, 05:15 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Aug 12, 2026, 06:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 27, 2026, 09:20 AM UTC· resolved Jul 27, 2026, 09:20 AM UTC

1. resolved Jul 27, 2026, 09:20 AM UTC

   Our monitoring system triggered a **Major Outage** alert on the **Pricing API** starting at 06:37 (GMT+2). Following investigation, we have confirmed that this alert was caused by an issue with our **automatic monitoring probe** and did not reflect any actual service degradation. All pricing products and services were **fully operational** throughout this entire period and were not impacted in any way. No action is required from our clients or partners. - **Alert start time:** 06:37 (GMT+2), 27 Jul 2026 - **Alert end time:** 11:19 (GMT+2), 27 Jul 2026 - **Duration:** 4 hours 42 minutes - **Impacted services:** None – Pricing API remained fully operational - **Root cause:** Automatic monitoring probe failure (no customer impact) We apologize for any concern this alert may have caused.

Read the full incident report →

Started Jul 24, 2026, 11:02 AM UTC· resolved Jul 27, 2026, 07:55 AM UTC

1. investigating Jul 24, 2026, 11:02 AM UTC

   We are currently investigating a complete unavailability of our **Developer Portal** (developer.wakam.com). The portal is not responding and users are unable to access it. - **Detection time:** 12:47 (GMT+2), 24 Jul 2026 - **Impacted services:** Developer Portal - **Status:** Under investigation The issue appears to be related to an infrastructure problem with one of our external service providers. Our team is actively working to restore the service as quickly as possible. We will provide updates as soon as new information becomes available, and **at least every 60 minutes**. We sincerely apologize for any inconvenience this may cause.

2. monitoring Jul 24, 2026, 01:40 PM UTC

   A fix has been applied by our external service provider and the **Developer Portal** (developer.wakam.com) is now responding again. The interruption was caused by an infrastructure component restart on the service provider side. We are closely monitoring the service to confirm full stability before closing this incident. - **Detection time:** 12:47 (GMT+2), 24 Jul 2026 - **Stabilization time:** 14:52 (GMT+2), 24 Jul 2026 - **Impacted services:** Developer Portal - **Status:** Monitoring – service appears stable We will provide a final update shortly. Thank you for your patience.

3. monitoring Jul 24, 2026, 02:07 PM UTC

   While access to the **Developer Portal** (developer.wakam.com) has been restored, we are observing intermittent performance degradation. Some users may experience slower than usual response times. Our team continues to closely monitor the service and is working to ensure full stability is achieved. - **Detection time:** 12:47 (GMT+2), 24 Jul 2026 - **Stabilization time:** 14:52 (GMT+2), 24 Jul 2026 - **Last update:** 16:05 (GMT+2), 24 Jul 2026 - **Impacted services:** Developer Portal - **Status:** Monitoring – intermittent slowness observed We will provide a further update by **17:05 (GMT+2)** at the latest. We apologize for the continued inconvenience.

4. resolved Jul 27, 2026, 07:55 AM UTC

   The **Developer Portal** (developer.wakam.com) has been fully restored and is operating normally. The incident was caused by an infrastructure component failure on the side of one of our external service providers. The issue was resolved following a restart of the affected component, after which intermittent slowness was observed before full stability was confirmed. - **Detection time:** 12:47 (GMT+2), 24 Jul 2026 - **Stabilization time:** 14:52 (GMT+2), 24 Jul 2026 - **Resolution time:** 05:46 (GMT+2), 25 Jul 2026 - **Total duration:** ~17 hours - **Impacted services:** Developer Portal We sincerely apologize for the disruption caused. Our team is conducting a post-incident review to identify preventive measures and ensure this type of issue does not recur. Thank you for your patience and understanding.

Read the full incident report →

Started Jul 02, 2026, 07:45 AM UTC· resolved Jul 02, 2026, 07:45 AM UTC

1. resolved Jul 02, 2026, 07:45 AM UTC

   The **Pricing APIs** are now fully operational. All services have been restored and the component status has been updated accordingly. Thank you for your patience.

Read the full incident report →

Started Jul 01, 2026, 04:56 PM UTC· resolved Jul 02, 2026, 07:39 AM UTC

1. identified Jul 01, 2026, 04:56 PM UTC

   We have identified the root cause of the ongoing issue affecting our **Pricing APIs**. Since **26 Jun 2026**, some partners experienced failures when attempting to look up a quote by reference or create an insurance policy after a successful pricing call. The API returned an error indicating the quote reference could not be found, even when it had been successfully generated moments earlier. This was caused by **an unexpected failure in one of our internal backend processing components**, which resulted in significant delays in quote recording. No quote data has been lost; all quotes are being processed, with delays. Corrective actions have been deployed to restore normal processing and improve the resilience of the affected component. We are closely monitoring the service. **Quote lookup delays of several hours are still currently being observed.** - **Detection time:** 08:05 (GMT+2), 26 Jun 2026 - **Identification time:** 29 Jun 2026 - **Impacted services:** Pricing APIs – Quote Lookup (getPrice by QuoteReference) / Policy Creation - **Status:** Fix deployed — residual delays of several hours under active monitoring We will provide a further update by **19:54 (GMT+2), 01 Jul 2026** at the latest. We sincerely apologize for the continued disruption to your operations.

2. identified Jul 01, 2026, 06:24 PM UTC

   We have identified the root cause of the ongoing issue affecting our **Pricing APIs**. Since **26 Jun 2026**, some partners experienced failures when attempting to look up a quote by reference or create an insurance policy after a successful pricing call. The API returned an error indicating the quote reference could not be found, even when it had been successfully generated moments earlier. This was caused by **an unexpected failure in one of our internal backend processing components**, which resulted in significant delays in quote recording. No quote data has been lost; all quotes are being processed, with delays. Corrective actions have been deployed to restore normal processing and improve the resilience of the affected component. **Quote lookup delays of several hours are still currently being observed.** - **Detection time:** 08:05 (GMT+2), 26 Jun 2026 - **Identification time:** 29 Jun 2026 - **Impacted services:** Pricing APIs – Quote Lookup (getPrice by QuoteReference) / Policy Creation - **Status:** Fix deployed — residual delays of several hours under active monitoring Our team is **closely monitoring the service throughout the night** to ensure a full and stable return to normal operations. We sincerely apologize for the continued disruption to your operations.

3. monitoring Jul 01, 2026, 08:00 PM UTC

   Following infrastructure adjustments carried out by our team, the processing backlog affecting **Quote Lookup and Policy Creation** has been fully cleared as of **21:44 (GMT+2), 01 Jul 2026**. No further delays are being observed. We are **closely monitoring** the service to confirm that operations remain stable before closing this incident. - **Detection time:** 08:05 (GMT+2), 26 Jun 2026 - **Stabilization time:** 21:44 (GMT+2), 01 Jul 2026 - **Impacted services:** Pricing APIs – Quote Lookup (getPrice by QuoteReference) / Policy Creation - **Status:** Monitoring – backlog cleared, service appears stable We will provide a final update shortly. We sincerely apologize for the disruption this incident has caused to your operations.

4. resolved Jul 02, 2026, 07:39 AM UTC

   The **Pricing APIs** — including Quote Lookup (getPrice by QuoteReference) and Policy Creation — have been fully restored. Following infrastructure adjustments carried out by our team, the processing backlog was fully cleared on **01 Jul 2026 at 21:44 (GMT+2)**. The service has been stable overnight and is now confirmed fully operational. - **Detection time:** 08:05 (GMT+2), 26 Jun 2026 - **Stabilization time:** 21:44 (GMT+2), 01 Jul 2026 - **Resolution time:** 09:38 (GMT+2), 02 Jul 2026 - **Total duration:** ~5 days 13 hours - **Impacted services:** Pricing APIs – Quote Lookup (getPrice by QuoteReference) / Policy Creation We sincerely apologize for the significant disruption this incident caused to your operations. Our team is conducting a post-incident review to identify preventive measures and ensure this type of issue does not recur. Thank you for your patience and understanding.

Read the full incident report →

Started Apr 28, 2026, 08:04 AM UTC· resolved Apr 28, 2026, 05:10 PM UTC

1. identified Apr 28, 2026, 08:04 AM UTC

   Contrary to our previous update, the incident has not been fully resolved. We are currently experiencing intermittent availability issues affecting the Wakam Developer Portal. Users may experience difficulties accessing the portal or encounter unexpected errors during their session. Our engineering team has been notified and is actively investigating the root cause to stabilize the service as quickly as possible. We apologize for the inconvenience and will provide updates as the situation evolves.

2. monitoring Apr 28, 2026, 09:44 AM UTC

   A mitigation action has been implemented to restore service. We are closely monitoring the Wakam developer portal. We are currently awaiting further information from our cloud hosting provider to identify the cause of the problem and define a long-term solution. We will keep you informed as soon as we have more information. Thank you for your patience.

3. monitoring Apr 28, 2026, 11:35 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Apr 28, 2026, 05:10 PM UTC

   The Developer Portal has been stable for the past 8 hours. This incident is now closed. The root cause was traced to an issue on one of our cloud provider's services, which appears to have been resolved. We will continue to monitor availability going forward.

Read the full incident report →

Started Apr 02, 2026, 01:30 PM UTC· resolved Apr 02, 2026, 02:30 PM UTC

1. resolved Apr 03, 2026, 12:29 PM UTC

   Play&Plug distributor users experienced a partial disruption on the Distributor Portal between 16:30 and 16:56. The following features were temporarily unavailable: - Product Oversight and Governance (Compliance) - Some dashboard elements, including actuarial reviews The incident has been resolved. All services are now fully operational.

Read the full incident report →

Started Feb 25, 2026, 03:20 PM UTC· resolved Feb 25, 2026, 03:26 PM UTC

1. resolved Feb 25, 2026, 05:32 PM UTC

   The Pricing APIs experienced a brief service interruption between **15:20 and 15:26 (GMT)** due to a planned infrastructure update. The impact on the service was not anticipated ahead of the maintenance window. The service has been **fully restored** as of 15:26 GMT. We apologize for any inconvenience caused and are reviewing our change management process to prevent similar unplanned impacts in the future.

Read the full incident report →

Started Feb 04, 2026, 02:01 PM UTC· resolved Feb 05, 2026, 08:46 AM UTC

1. investigating Feb 04, 2026, 02:01 PM UTC

   Our application is currently experiencing instability. Users may experience degraded performance or intermittent issues. Our engineering team is investigating and working on a resolution.

2. monitoring Feb 04, 2026, 05:43 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Feb 05, 2026, 08:46 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 08, 2025, 10:48 AM UTC· resolved Dec 08, 2025, 10:58 AM UTC

1. investigating Dec 08, 2025, 10:48 AM UTC

   We are currently investigating this issue.

2. resolved Dec 08, 2025, 10:58 AM UTC

   This incident had no impact for Partners.

Read the full incident report →

Started Nov 14, 2025, 02:52 PM UTC· resolved Nov 14, 2025, 03:36 PM UTC

1. identified Nov 14, 2025, 02:52 PM UTC

   Ongoing Incident - Pricing APIs We are currently experiencing an incident affecting all our Pricing APIs. Since 3:15 PM CET on Friday, November 14, 2025, API calls are returning a 403 Partnership Forbidden error. Our technical teams are fully mobilized to resolve this issue as quickly as possible. We will keep you informed as soon as the service is restored. We apologize for any inconvenience caused. Incident en cours - APIs de Pricing Nous rencontrons actuellement un incident qui impacte l'ensemble de nos APIs de Pricing. Depuis 15h15 ce vendredi 14 novembre 2025, les appels retournent une erreur 403 Partnership Forbidden. Nos équipes techniques sont pleinement mobilisées pour résoudre ce problème dans les plus brefs délais. Nous vous tiendrons informés dès que le service sera rétabli. Nous nous excusons pour la gêne occasionnée.

2. resolved Nov 14, 2025, 03:36 PM UTC

   The service has now been restored. Our Pricing APIs are operational again as of 4:15PM CET. The incident that affected our Pricing APIs since 3:15 PM CET has been resolved. All API calls are functioning normally. Thank you for your patience and we apologize for any inconvenience caused. Le service est maintenant rétabli. Nos APIs de Pricing sont de nouveau opérationnelles depuis 16h15. L'incident qui affectait nos APIs de Pricing depuis 15h15 a été résolu. Tous les appels fonctionnent normalement. Nous vous remercions pour votre patience et nous excusons pour la gêne occasionnée.

Read the full incident report →

Started Oct 29, 2025, 04:17 PM UTC· resolved Oct 30, 2025, 12:05 AM UTC

1. investigating Oct 29, 2025, 04:17 PM UTC

   We’re currently experiencing service degradation due to a widespread incident at our cloud provider. Our team is actively investigating and working with the provider; mitigation options are limited at this time

2. investigating Oct 29, 2025, 04:25 PM UTC

   Investigating — Azure Portal access issues We’re investigating a provider-side incident affecting the Azure Portal. Some customers may be unable to sign in or access portal features. We’re working with Microsoft and will provide more information shortly.

3. investigating Oct 29, 2025, 04:26 PM UTC

   We are continuing to investigate this issue.

4. investigating Oct 29, 2025, 04:40 PM UTC

   Monitoring — Azure Portal Access Issues (DNS) We observed provider-side DNS issues causing availability degradation for some services and preventing access to the Azure Portal. We have taken mitigation steps expected to restore portal access shortly. We are continuing to investigate the underlying cause with Microsoft and assess additional mitigations. We will provide the next update within 60 minutes or sooner.

5. investigating Oct 29, 2025, 04:55 PM UTC

   Our Pricing API is currently unavailable, all calls to the Pricing API are currently failing. We are actively investigating and working to restore service

6. investigating Oct 29, 2025, 05:02 PM UTC

   Mitigation in progress — Azure Front Door impact Issues with Azure Front Door at our cloud provider have caused loss of availability for some services (Pricing api, P&P distributeurs). We’re working closely with the provider and will share more as we learn more.

7. investigating Oct 29, 2025, 05:22 PM UTC

   Mitigation in progress — Provider rollback to last known good state Our cloud provider has initiated a rollback to the last known good state to address ongoing availability issues impacting some services.

8. investigating Oct 29, 2025, 07:11 PM UTC

   Provider recovery in progress (Azure Front Door) Our cloud provider reports recovery is progressing actually

9. identified Oct 29, 2025, 07:45 PM UTC

   Recovery progressing Our cloud provider has completed the rollback. We’re seeing early signs of recovery as traffic is progressively restored. Services remain very degraded at this moment. The provider currently estimates full mitigation within the next four hours. We’re monitoring closely and will provide the next update in 60 minutes (or sooner if there’s a significant change). We apologize for the disruption.

10. identified Oct 29, 2025, 09:12 PM UTC

    Gradual recovery continues We’re observing continued improvements as our provider restores traffic. Pricing API availability and latency are improving, though intermittent failures may still occur. The provider expects gradual improvements to continue for at least the next hour. We’re monitoring closely and will provide the next update in 60 minutes (or sooner if there’s a significant change). Thank you for your patience.

11. monitoring Oct 29, 2025, 10:19 PM UTC

    Services stable, monitoring continues All monitors are green again, and Pricing API traffic has returned to normal levels compared to the same time yesterday. The incident remains open at our cloud provider; we’ll keep heightened monitoring before declaring full resolution on our side. Thank you for your patience.

12. monitoring Oct 30, 2025, 08:35 AM UTC

    Ignore

13. resolved Oct 30, 2025, 08:36 AM UTC

    The incident is fully resolved and services are stable. Root cause (provider): an inadvertent Azure Front Door configuration change introduced an invalid state, causing many edge nodes to fail. Thank you for your patience.

Read the full incident report →

Started Oct 09, 2025, 08:50 AM UTC· resolved Oct 09, 2025, 05:00 PM UTC

1. investigating Oct 09, 2025, 08:50 AM UTC

   We are currently facing partial disruptions. We don't know yet if it comes from our cloud provider or if it something more global.

2. investigating Oct 09, 2025, 08:55 AM UTC

   We are continuing to investigate this issue.

3. investigating Oct 09, 2025, 09:45 AM UTC

   Incident Update — Cloud provider issues We’re currently experiencing service degradation due to a widespread incident at our cloud provider. Our team is actively investigating and working with the provider; mitigation options are limited at this time. We’ll provide the next update within 60 minutes. We’re sorry for the disruption and appreciate your patience.

4. identified Oct 09, 2025, 10:11 AM UTC

   Azure Front Door incident Our cloud provider has acknowledged an incident affecting Azure Front Door, which may cause intermittent errors and increased latency when accessing our services. We’re actively engaged with the provider and monitoring for recovery; mitigation options remain limited until their fix is deployed. Next update in 60 minutes. Thank you for your patience.

5. identified Oct 09, 2025, 11:42 AM UTC

   Cloud provider network issues Our cloud provider has acknowledged difficulties within their network infrastructure, which may cause intermittent connectivity errors, elevated latency, and timeouts when accessing our services. We’re actively monitoring and working with the provider, and validating mitigations where possible. Next update in 60 minutes. Thank you for your patience.

6. monitoring Oct 09, 2025, 01:09 PM UTC

   Recovery in progress Our cloud provider is still working on the incident. Most services have returned to near full capacity, but minor latency and intermittent errors may persist for some users. We’re closely monitoring and coordinating with the provider until full recovery. Next update in 60 minutes. Thank you for your patience.

7. monitoring Oct 09, 2025, 04:36 PM UTC

   Near-normal operations Our services are operating close to normal. Our cloud provider is continuing to recover additional resources, so minor latency or intermittent errors may still occur for some users. We’re monitoring closely and will post a final update once full recovery is confirmed. Thank you for your patience.

8. resolved Oct 10, 2025, 07:33 AM UTC

   Services back to normal Our cloud provider has resolved the incident. All Wakam services have been operating normally since 18:00 CEST on 9 Oct 2025, and all monitors have remained green. We’ll continue to monitor closely. Post-mortem is available on Azure status history webpage https://azure.status.microsoft/en-us/status/history/ with tracking ID QNBQ-5W8. Sorry for the disruption, and thank you for your patience.

Read the full incident report →

Started Oct 01, 2025, 08:15 AM UTC· resolved Oct 01, 2025, 04:54 PM UTC

1. identified Oct 01, 2025, 12:57 PM UTC

   The September calendar box in Play&Plug Data Exchange is currently non-functional. Our technical team has identified the root cause and is implementing a fix. Workaround Available: Until the incident is fully resolved, users can continue their submissions using the "Multi-partnership submission" button as an alternative method. -> guide available here : https://wakam.notion.site/Partner-Data-eXchange-Play-Plug-Distributors-onboarding-v2-209b5182db7e807eb3b5df6a1890b6ff#:~:text=is%20now%20completed-,3.3%20Multi%2Dpartnership%20submission,-If%20you%20have

2. resolved Oct 01, 2025, 04:54 PM UTC

   This incident has been resolved thank you for your patience.

Read the full incident report →

Started Sep 10, 2025, 08:52 AM UTC· resolved Sep 10, 2025, 09:39 AM UTC

1. investigating Sep 10, 2025, 08:52 AM UTC

   We are currently investigating the issue

2. resolved Sep 10, 2025, 09:39 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 13, 2025, 02:43 PM UTC· resolved Aug 13, 2025, 02:43 PM UTC

1. resolved Aug 19, 2025, 03:38 PM UTC

   The document generation service stopped functioning from 12:52 PM making new subscriptions impossible. It is now operational.

Read the full incident report →

Started Apr 15, 2025, 12:59 PM UTC· resolved Apr 15, 2025, 12:59 PM UTC

1. resolved Apr 15, 2025, 12:59 PM UTC

   From 3:18 to 7:14 (UTC) the API Pricing service was down/very slow. Root cause is currently investigated. It seems to come from a maintenance action by our cloud operator.

Read the full incident report →

Started Mar 05, 2025, 01:16 PM UTC· resolved Mar 05, 2025, 05:32 PM UTC

1. investigating Mar 05, 2025, 01:16 PM UTC

   We are currently investigating the issue.

2. resolved Mar 05, 2025, 05:32 PM UTC

   Still investigating.

Read the full incident report →

Started Mar 04, 2025, 03:45 PM UTC· resolved Mar 04, 2025, 04:04 PM UTC

1. identified Mar 04, 2025, 03:45 PM UTC

   Partner Data eXchange is down. The team is resolving the issue as soon as possible.

2. resolved Mar 04, 2025, 04:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 11, 2025, 09:30 AM UTC· resolved Feb 11, 2025, 09:30 AM UTC

1. resolved Feb 12, 2025, 10:11 AM UTC

   Between 10:43 and 11:10, about 38% of requests returned unexpected 524 status code. The root cause of this incident was the unavailability of one of our 3rd party API.

Read the full incident report →

Started Jan 29, 2025, 11:30 AM UTC· resolved Jan 29, 2025, 11:30 AM UTC

1. resolved Jan 29, 2025, 04:13 PM UTC

   A technical incident affected the display of the formula page on our EcoMobility White Label Sales Funnel, making it temporarily impossible for customers to subscribe to new policies. Our technical teams worked to resolve the issue, and the service has been fully restored at 04:18 PM. All systems are now operating normally. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jan 27, 2025, 10:13 AM UTC· resolved Jan 27, 2025, 01:50 PM UTC

1. investigating Jan 27, 2025, 10:13 AM UTC

   Since 10:55 (Paris Time), we are facing abnormal amount of 524 errors on the pricing engine due to 3rd party API failures.

2. monitoring Jan 27, 2025, 10:23 AM UTC

   Service is back to normal since 11:18 (Paris Time)

3. resolved Jan 27, 2025, 01:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 07, 2025, 12:27 AM UTC· resolved Jan 07, 2025, 04:30 PM UTC

1. monitoring Jan 07, 2025, 06:49 PM UTC

   We are currently experiencing a technical issue with our partner in charge of the sales funnel, which is affecting payment validation and the sending of subscription confirmations. This situation may cause delays in receiving your confirmation emails and insurance certificates. Our technical teams are actively working to resolve this issue.

2. monitoring Jan 07, 2025, 06:57 PM UTC

   The sales funnel is up but with some instability. We are continuing to monitor for any further issues.

3. resolved Jan 08, 2025, 08:33 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 02, 2024, 02:30 AM UTC· resolved Dec 02, 2024, 02:20 PM UTC

1. resolved Dec 02, 2024, 03:57 PM UTC

   Due to the high latency of a 3rd party API, partners using ourPricing API may have experienced high latencies and unexpected 524 errors from 14:20 to 15:10 (UTC)

Read the full incident report →