Infosoft - Notice history

All systems operational

100% - uptime

Merchant - Operational

100% - uptime
Apr 2023 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2023
May 2023
Jun 2023

API - Operational

100% - uptime
Apr 2023 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2023
May 2023
Jun 2023

Self Service - Operational

100% - uptime
Apr 2023 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2023
May 2023
Jun 2023
Operational

Third Party: Auth0 → Europe (PROD) → Auth0 Machine to Machine Authentication - Operational

Third Party: Auth0 → Europe (PROD) → Auth0 Email Delivery - Operational

Third Party: Vipps MobilePay → Recurring API - Operational

Third Party: Auth0 → Europe (PROD) → Auth0 User Authentication - Operational

Mastercard Payment Services - Operational

100% - uptime
Apr 2023 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2023
May 2023
Jun 2023

Notice history

Jun 2023

Azure Network Issue
  • Resolved
    Resolved

    This incident has been resolved.

    Now known issues persists.

  • Update
    Update

    All services seems to be running at regular levels.

    We have an increase in number of succesfully processed requests, and a reduction in response times that are consistent with the normal operating range.

    We will continue to monitor the progress.

    Note: that other services are also affected by this outage, we are currently observing reduced response times and timeouts from Vipps settlement processing. This have a limited impact on our services.

  • Monitoring
    Monitoring

    Microsoft reports a mitigation has been deployed to their infrastructure.

    We are already seeing improvements across the board, but we will continue to monitor.

    Microsoft expects the error to be fully resolved around 10.00 CEST.

  • Investigating
    Investigating

    Our primary hosting platform, Microsoft Azure, is experiencing general network connectivity issues across Europe.

    Unfortunately this is impacting our services, meaning you will experience degraded performance.

    Investigation shows no significant impact except for some delays in the UI services.

    We will continue to monitor and provide an update once things are running as expected.

    Since this is an upstream issue with multiple failures there is little we can do to mitigate the problem immediately. For the underlying status issue have a look at https://status.azure.com/en-us/status

Issue with accessing reporting and analytics data
  • Resolved
    Resolved

    During a semi-automated upgrade of the platform runtime environment, the reporting and analytics component stopped responding to queries because it was being moved around.

    The Merchant client uses this component for query/search of Subscribers and was unable to produce any results while the component was unresponsive.

    The reporting and analytics component is once more up and running and everything should proceed as normal.
    All other operations was working as normal during the outage.

    Root cause:
    The reporting and analytics component was misconfigured causing only one instance to be running at any given time. The automated upgrade caused long responsetimes and frequent restarts of the component.
    The issue has now been mitigated and configuration adjusted to allow multiple concurrent instances to prevent outages similar to the current one.

May 2023

No notices reported this month

Apr 2023

Swedbank Pay Agreement Registration Timeouts
  • Resolved
    Resolved

    This incident has been resolved.

    All agreement registrations are now being processed in a timely fashion.

    The root cause was a misconfiguration in an internal component responsible for Swedbank Pay processing.

  • Monitoring
    Monitoring

    There is an issue with Swedbank Pay, causing new agreement registration to timeout.

    The effect is that new orders and attempt to create a new Swedbank Pay agreement will produce an error message instead of the Swedbank Pay terminal.

    We have identified the problem and rolled out a fix.

    We are continuing to monitor the situation and will update this incident once we have confirmed the issue is rectified.

Apr 2023 to Jun 2023

Next