Shipup - Notice history

Experiencing minor outage

FTP integrations - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Platform integrations - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026
96.80% uptime

Mondial Relay - Partial outage

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

DPD - Partial outage

70.39% uptime
Mar 2026 · 70.00%Apr · 70.00%May · 71.13%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Evri - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Royal Mail - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

InPost - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

FedEx - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Yodel - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

DPD Germany - Partial outage

62.44% uptime
Mar 2026 · 100.0%Apr · 79.15%May · 9.91%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Canada Post - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

DHL express - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Packeta - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

DHL - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Colissimo - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Correos - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Poste Italiane - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

DPD NL - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

APG - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

UPS - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Chronopost - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Geodis - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Others - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Claims - Operational

70.00% uptime
Mar 2026 · 70.00%Apr · 70.00%May · 70.00%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Reporting - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Notice history

View current status

May 2026

Notifications not created in time
ResolvedDegraded performance1 hour
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC

    There is some unusual delay between the import of carrier events and the creation of the associated notifications. We are investigating the issue.

We're experiencing lag in carrier connections with Colissimo and Chronopost
ResolvedDegraded performance120 hours 27 minutes
  • ResolvedUTC

    This incident has been fully resolved.

  • PostmortemUTC

    Description

    Date: May 15th 2026

    We experienced an issue affecting carrier event processing for Chronopost and Colissimo shipments.

    The incident started on May 4th 2026, but was only detected later after reports of delayed tracking updates, as it increased over time. The issue originated from our Event Fetching V3 system, where carrier events were being processed with increasing delay.

    On May 13th, we mitigated the issue by temporarily rerouting processing from Event Fetching V3 to our legacy Event Fetching V2 system, which reduced the lag and restored normal processing for Chronopost shipments.

    On May 15th, a similar issue reoccurred and affected Colissimo shipments as well. The same mitigation was applied to reduce the impact.

    The mitigations implemented during the incident were temporary measures. We are continuing to investigate the root cause and work on a permanent solution.

    Business consequences of the issue

    During the incident period, some merchants experienced delayed shipment tracking updates for Chronopost and Colissimo deliveries.

    As a consequence:

    • Shipment notifications could be delivered later than expected.

    • In some cases, notifications may not have been sent if carrier events exceeded internal expiration thresholds.

    • Shipment tracking visibility may have been temporarily degraded.

    The issue primarily affected shipments using Chronopost and Colissimo integrations.

    The absence of proper monitoring on event-processing lag delayed the detection of the issue and increased the duration of customer impact.

    Chronology

    • May 4th: Increased lag begins in carrier event processing on Event Fetching V3.

    • May 12th: First reports of delayed tracking updates are received.

    • May 13th: Investigation confirms lag affecting Chronopost event processing.

    • May 13th: Mitigation applied by rerouting processing from Event Fetching V3 to Event Fetching V2.

    • May 15th: Similar lag issue detected affecting Colissimo event processing.

    • May 15th: Same mitigation strategy applied to reduce impact.

    Learnings

    • We lacked proper monitoring and alerting on carrier event-processing lag.

    • The issue remained undetected for several days before customer reports triggered the investigation.

    • Existing fallback procedures using the legacy V2 system helped reduce impact, but are not a sustainable long-term solution.

    Short term actions

    Description of the short-term actions that could help prevent recurrence:

    • Add metrics and alerting on carrier event-processing lag

    • Improve operational visibility on Event Fetching V3 processing queues

    • Document and standardize mitigation procedures for rerouting processing traffic

    Long term actions

    Description of the long-term actions:

    • Investigate and resolve the root cause of lag generation in Event Fetching V3

    • Improve scalability and resilience of the event-processing pipeline

    • Review notification expiration rules and evaluate fallback mechanisms for delayed events

    • Reduce dependency on the legacy V2 system for incident mitigation

  • MonitoringUTC

    We took a mitigation action that will stabilise the tracking update latency. Trackers are getting up to date as we monitor.

  • InvestigatingUTC

    We received reports of delayed tracking updates on one of our top carriers. Our engineers are investigating the root cause and looking for a mitigation.

Emails not sent anymore
ResolvedMajor outage54 hours 19 minutes
  • ResolvedUTC

    Sendgrid emails do now go through. Emails that were held up during the outage will be sent automatically by Sendgrid.

    Carrier notifications are still being exceptionally sent.

  • UpdateUTC

    We are continuing to work on a fix for this incident.

    The reason that led SendGrid to lock our account has been solved. We are now waiting for SendGrid to unlock our account to be back on normal.

    To be noted: none of this incident has been caused by a security issue, but only by a false classification by a Spam listing organization.

  • IdentifiedUTC

    We identified the reason SendGrid blocked our account, and this reason is being corrected.

    We also requested the SendGrid Compliance Team to unlock our account; we are waiting for their answer.

    Please note: all the Carrier Notifications are sent correctly and have not been disturbed.

    During the incident, all the filtered Carrier Notifications are exceptionally sent, to make sure none of the Shoppers miss an important update about their packages.

  • InvestigatingUTC

    SendGrid detected spoofing by one of our customers and blocked our account, preventing any mail from being sent.

Cannot access archive data through API
ResolvedPartial outage2 hours 55 minutes
  • ResolvedUTC
    This incident has been resolved.
  • IdentifiedUTC

    Following a deployment, we identified that API requests that attempt to fetch archived data (older than 6 months) are failing.

Apr 2026

Global platform instability
ResolvedDegraded performance9 hours
  • ResolvedUTC

    The root cause of the incident was identified and a complete fix deployed.

  • MonitoringUTC

    We took mitigation measures and are monitoring as performances go back to normal.

  • ResolvedUTC

    We experience global platform instability since 9am today.

DPD DE event fetching is down
IdentifiedPartial outage
  • IdentifiedUTC

    We are working closely with the carrier to implement a new integration method.

  • InvestigatingUTC

    Due to changes on the carrier's side, we can no longer fetch events and send notifications on DPD DE trackers.

Mondial Relay Pickup Point information is no longer updated
ResolvedDegraded performance667 hours 48 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC

    We implemented a fix and are currently monitoring the result.

    We started updating pickup point information again on 07/05 4pm UTC

  • IdentifiedUTC

    Since April 13 2pm, we fail to update Mondial Relay pickup point information (f.i. opening day & hours).

    As a result, the information shared in notifications and tracking pages may be outdated or missing.

    We are in contact with the carrier to fix the incident.

APR12
Database maintenance
CompletedMaintenance4 hours
  • CompletedApril 12, 2026 at 12:00 PMUTC
    Maintenance has completed successfully
  • In progressApril 12, 2026 at 8:00 AMUTC
    Maintenance is now in progress
  • PlannedApril 12, 2026 at 8:00 AMUTC

    We will be performing a scheduled maintenance on our database on April 12th, 2026. This maintenance window will begin at 10:00 AM and is expected to last approximately 2 hours.

    This maintenance has been scheduled during a window corresponding to reduced activity on our platform and its users.

    All the following services will be impacted :

    - API:

    * POST Orders / Trackers

    * POST Delivery Date Estimation (Smart Delivery Estimates + ShipupETA library)

    * GET Orders / Trackers

    - Access to the Shipup back-office

    - Chrome extension - Webhooks

    - Retrieving of events from the carriers

    - Sending of notifications

    - Order-fetching integrations (Magento, Shopify, Prestashop)

    - Third-party integrations (Zendesk, Gorgias, Klaviyo)

    - Retrieving Feedback from customers

    - Package reports

    - Tracking page access by end users

    We appreciate your patience and your understanding.

    As always, if you have questions or issues, please contact us at support@shipup.co.

Issue with authentication
ResolvedPartial outage35 minutes
  • ResolvedUTC
    This incident has been resolved.
  • InvestigatingUTC

    Some users are not able to log into our backoffice.

Mar 2026

MAR31
USPS Integration maintenance
CompletedMaintenance168 hours
  • CompletedApril 07, 2026 at 7:00 AMUTC
    Maintenance has completed successfully
  • In progressMarch 31, 2026 at 7:00 AMUTC
    Maintenance is now in progress
  • PlannedMarch 31, 2026 at 7:00 AMUTC

    As part of a planned migration and due to unannounced changes in USPS API pricing policy, we have placed our USPS integration into maintenance as of Tuesday, March 31, 2026 at 9:00 AM.

    The maintenance is expected to last until the end of the week. During that maintenance window we will:

    • migrate to new USPS APIs

    • collect all the necessary credentials from USPS users

    If you import USPS trackers in Shipup, please follow steps 1 to 3 described here and share your credentials to your representative.

    ⚠️ These credentials are highly sensitive and must be shared via a secure channel (for example, a temporary link from a password manager). Any credential sent directly via email will be considered compromised.

Previous

Mar 2026 to May 2026

Next