Some systems are experiencing issues

Past Incidents

27th December 2020

No incidents reported

26th December 2020

No incidents reported

25th December 2020

No incidents reported

24th December 2020

Portal API Retailer Portal API has degraded performance

Latency above threshold: 1.0343 seconds

  • Retailer Portal API is operational

    • 23rd December 2020

    Credit Engine Credit Engine has degraded performance

    Latency above threshold: 1.0209 seconds

  • Credit Engine is operational

    • CRM CRM is unavailable

    Unexpected HTTP status (500)

  • CRM is operational

    • CRM CRM is unavailable

    Unexpected HTTP status (500)

  • CRM is operational

    • CRM CRM is unavailable

    Unexpected HTTP status (500)

  • CRM is operational

    • CRM CRM is unavailable

    Unexpected HTTP status (500)

  • CRM is operational

    • CRM CRM is unavailable

    Unexpected HTTP status (500)

  • CRM is operational

    • CRM CRM is unavailable

    Unexpected HTTP status (500)

  • CRM is operational

    • 22nd December 2020

    Core API Core API has degraded performance

    Latency above threshold: 1.0391 seconds

  • Core API is operational

    • 21st December 2020

    Payment Service Payment Service has degraded performance

    Request timed out

  • Payment Service is operational

    • Payment Service Payment Service has degraded performance

    Request timed out

  • Payment Service is operational

    • Payment Service Adjustments to Payment Service Status Monitor

    Timeout settings on the Payment Service Status Monitor were causing a number of False flag incidents to be raised for Performance/Partial Outage.

    The status monitor configuration has been adjusted to reflect this change and the previous incidents have been removed from the list as false positives.

    20th December 2020

    Site Outage

    An outage occurred on the platform starting at approximately 07:30am.

    As soon as the issue was noticed action was immediately taken to resolve the incident. In this case by adding an extra instance into the load balancer and rebooting the unhealthy incident. We continue to investigate the cause of this problem.