Delivery Solutions Outage History

Delivery Solutions is up right now

Pingoru has recorded 34 incidents for Delivery Solutions: 0 in the last 12 months and 0 in the last 90 days.

Source: production.status.deliverysolutions.co

34incidents recorded
0last 12 months
0last 90 days
–typical duration

Incidents, newest first

Major March 11, 2025 Delivery Assurance Outage 2h 50m Delivery Assurance

Started Mar 11, 2025, 09:37 AM UTC· resolved Mar 11, 2025, 12:27 PM UTC

  1. investigating Mar 11, 2025, 09:37 AM UTC

    We are currently investigating this issue.

  2. monitoring Mar 11, 2025, 09:59 AM UTC

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

  3. resolved Mar 11, 2025, 12:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 10, 2025 Place Order Downtime 8m

Started Mar 10, 2025, 11:30 AM UTC· resolved Mar 10, 2025, 11:38 AM UTC

  1. resolved Mar 10, 2025, 12:18 PM UTC

    We observed a downtime with our Place Order API for a period of 8 minutes As a side-effect of the Place Order downtime, please expect some delays in webhooks and notifications.

Read the full incident report →

Minor January 16, 2025 Intermittent Authentication Issues with Delivery Solutions API(s) 2h 9m Place Order, Delivery Assurance, Smart Windows, Rates

Started Jan 16, 2025, 02:11 PM UTC· resolved Jan 16, 2025, 04:20 PM UTC

  1. identified Jan 16, 2025, 02:11 PM UTC

    We are currently see elevated error rates due to intermittent Authentication Issues with Delivery Solutions API(s). We are actively working on a fix.

  2. monitoring Jan 16, 2025, 03:37 PM UTC

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

  3. resolved Jan 16, 2025, 04:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 22, 2024 Issue with Delivery Assurance API 34m Delivery Assurance

Started Oct 22, 2024, 08:54 AM UTC· resolved Oct 22, 2024, 09:29 AM UTC

  1. investigating Oct 22, 2024, 08:54 AM UTC

    We are currently investigating this issue.

  2. monitoring Oct 22, 2024, 09:14 AM UTC

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

  3. resolved Oct 22, 2024, 09:29 AM UTC

    This incident has been resolved.

Read the full incident report →