Xink Outage History

Xink is up right now

Xink had 18 outages in the last 2 years totaling 96h 56m of downtime — averaging 0.7 incidents per month.

There were 18 Xink outages since October 20, 2024 totaling 96h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.xink.io

Notice October 13, 2026

Xink UK service disruption

Detected by Pingoru
Oct 13, 2026, 02:35 PM UTC
Resolved
Oct 14, 2026, 12:39 PM UTC
Duration
22h 3m
Affected: Admin PortalImagesOutlook Add-in
Timeline · 2 updates
  1. monitoring Oct 13, 2026, 02:35 PM UTC

    On 13 October between 08:58 and 10:16 BST (09:58–11:16 CEST), Xink UK services, including the web portal, Outlook add-in sync and signature images, were unavailable or intermittently unreachable. We have mitigated the issue: service was restored at 10:16 BST and has been stable since. We are monitoring closely while we put measures in place to prevent a recurrence. Root cause analysis is ongoing.

  2. resolved Oct 14, 2026, 12:39 PM UTC

    On 13 October between 08:58 and 10:16 BST (09:58–11:16 CEST), Xink services in our UK data center were unavailable or intermittently unreachable, including the Admin Portal, Outlook add-in and signature images. Cause: A sudden spike in requests for signature images overloaded the image service in our UK data center. The failure then spread to the component that routes all traffic into the UK data center, making UK services unavailable until it was restarted. Resolution: Service was restored at 10:16 BST and has been stable since. On 14 October we increased the capacity of the image service in the data center. We apologize for the disruption this caused.

Read the full incident report →

Minor June 27, 2026

Server side - all data centers. Microsoft change caused brief server-side worker restarts and mail delivery errors (NDR)

Detected by Pingoru
Jun 27, 2026, 04:00 AM UTC
Resolved
Jun 27, 2026, 04:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 30, 2026, 09:02 AM UTC

    Between Saturday 03:00–06:00 UTC, a Microsoft-initiated change caused a subset of our server-side workers to fail and restart. The resulting brief loss of worker availability impacted a small subset of customers across all regions, leading to mail deliverability issues, including NDRs for some outbound messages.

Read the full incident report →

Minor May 26, 2026

EU - outlook add-in connection error, slow signature load

Detected by Pingoru
May 26, 2026, 09:02 AM UTC
Resolved
May 26, 2026, 09:21 AM UTC
Duration
18m
Affected: Outlook Add-in
Timeline · 2 updates
  1. identified May 26, 2026, 09:02 AM UTC

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

  2. resolved May 26, 2026, 09:21 AM UTC

    Preliminary Root cause: Unusually high spike in requests. Mitigation: We increased capacity to handle peak client load in the EU DC. Services are operating normally.

Read the full incident report →

Minor May 20, 2026

EU - outlook add-in error, no signature load

Detected by Pingoru
May 20, 2026, 07:45 AM UTC
Resolved
May 20, 2026, 10:00 AM UTC
Duration
2h 14m
Affected: Outlook Add-in
Timeline · 2 updates
  1. identified May 20, 2026, 09:54 AM UTC

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

  2. resolved May 20, 2026, 10:00 AM UTC

    Root cause: A background maintenance job began at 9:15 and pushed the database into heavy load. The spike was driven by an unusually high volume of clicks from misconfigured settings.

Read the full incident report →

Minor May 19, 2026

EU - outlook add-in signature load is slow

Detected by Pingoru
May 19, 2026, 07:45 AM UTC
Resolved
May 19, 2026, 09:49 AM UTC
Duration
2h 4m
Affected: Outlook Add-in
Timeline · 3 updates
  1. identified May 19, 2026, 09:39 AM UTC

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

  2. identified May 19, 2026, 09:42 AM UTC

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

  3. resolved May 19, 2026, 09:49 AM UTC

    This incident has been resolved. Root cause: EU database capacity lagged behind growing client traffic. Mitigation: we scaled and updated to higher tier the EU managed database to handle the increased load. This will prevent latency issue in the future.

Read the full incident report →

Minor April 3, 2026

Azure AD integration error: The provided client secret keys are expired.

Detected by Pingoru
Apr 03, 2026, 02:45 AM UTC
Resolved
Apr 03, 2026, 09:44 AM UTC
Duration
6h 58m
Affected: IntegrationsIntegrationsIntegrationsIntegrationsIntegrations
Timeline · 2 updates
  1. monitoring Apr 03, 2026, 09:37 AM UTC

    The error occurred because the client secret used by our service principal for the Azure AD (Microsoft Entra ID) integration had expired. A client secret acts as a password that allows our application to authenticate and communicate with Microsoft Entra ID. These secrets are intentionally configured to expire after a set period for security reasons. When the secret reached its expiration date, authentication attempts began failing with the error: "The provided client secret keys for app are expired." We have generated a new client secret and updated all affected systems. We scheduled the next renewal to prevent this from happening again.

  2. resolved Apr 03, 2026, 09:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 1, 2026

Investigating delays in click data reporting

Detected by Pingoru
Apr 01, 2026, 10:08 AM UTC
Resolved
Apr 02, 2026, 10:57 AM UTC
Duration
1d
Affected: Campaign Analytics
Timeline · 3 updates
  1. investigating Apr 01, 2026, 10:08 AM UTC

    We are currently investigating an issue affecting the performance of click data retrieval for some customers. In certain cases, large volumes of historical data may lead to slower response times or timeouts when accessing click analytics. The root cause relates to how detailed click data has been stored over many years. As data volumes have grown significantly, this now impacts query performance. Our team is actively working on a solution that will improve performance while maintaining the level of insight our customers expect. This may include optimizing how older data is stored and accessed. We will share further updates as we progress.

  2. investigating Apr 01, 2026, 10:09 AM UTC

    We are continuing to investigate this issue.

  3. resolved Apr 02, 2026, 10:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 3, 2026

EU Server Side Service Disruption

Detected by Pingoru
Mar 03, 2026, 11:27 AM UTC
Resolved
Mar 03, 2026, 12:37 PM UTC
Duration
1h 10m
Affected: Server-side (Re-routing)
Timeline · 2 updates
  1. investigating Mar 03, 2026, 11:27 AM UTC

    Affected clients are seeing permanent delivery failures when sending emails, with the error: "messages undeliverable to one or more recipients." Our team is actively investigating and implementing fixes. We will share more details soon.

  2. resolved Mar 03, 2026, 12:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 27, 2026

Outlook Add-in: Error contacting Xink: HTTP error: 500

Detected by Pingoru
Feb 27, 2026, 03:28 AM UTC
Resolved
Feb 27, 2026, 08:07 AM UTC
Duration
4h 38m
Affected: Outlook Add-in
Timeline · 2 updates
  1. investigating Feb 27, 2026, 03:28 AM UTC

    Clients may encounter connection issue with the add-in, showing "Error contacting Xink: HTTP error: 500" We are currently investigating this issue.

  2. resolved Feb 27, 2026, 08:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 4, 2025

Outlook Add-in: Error contacting Xink: HTTP error: 503

Detected by Pingoru
Dec 04, 2025, 10:14 PM UTC
Resolved
Dec 05, 2025, 02:57 AM UTC
Duration
4h 43m
Affected: Outlook Add-in
Timeline · 4 updates
  1. investigating Dec 04, 2025, 10:14 PM UTC

    Clients may encounter connection issue with the add-in, showing error 503. We are currently investigating this issue.

  2. monitoring Dec 04, 2025, 10:18 PM UTC

    Applied updates for the add-in caused initial connection issue with Classic Outlook. Restarting the Outlook application will fix and restore the connection. Please advise users to restart their Outlook application to clear the error.

  3. resolved Dec 05, 2025, 02:57 AM UTC

    Incident has been resolved

  4. postmortem Dec 05, 2025, 02:57 AM UTC

    ## Description The Outlook 365 Add-in for Classic Outlook encountered connection issue \(Error 503\) where email signatures failed to load. ## Root Cause The issue was caused by an important update for the Add-in which requires Classic Outlook to restart in order to complete. ## Impact * **User Experience**: Add-in is not connecting and signatures are not inserted when composing emails. * **Business Impact**: No critical data loss or security issues. ## Resolution Users must restart Outlook app to clear the error and complete the Add-in update.

Read the full incident report →

Minor November 7, 2025

Xink add-in in Outlook on the web - Signature image are loading with high latency

Detected by Pingoru
Nov 07, 2025, 09:56 AM UTC
Resolved
Nov 08, 2025, 12:29 AM UTC
Duration
14h 33m
Affected: Outlook Add-in
Timeline · 3 updates
  1. monitoring Nov 07, 2025, 09:56 AM UTC

    We are actively investigating reports of slow image loading when composing a new email. This is only specific to the Xink add-in in Outlook on the web. Initial analysis confirms the issue does not occur in Outlook Classic or the New Outlook preview. Affected users may experience delayed rendering of signature images, intermittent image load errors, or instances where images fail to load entirely. Evidence points to a performance degradation in the Microsoft API used by the add-in to retrieve signature assets in Outlook on the web.

  2. monitoring Nov 08, 2025, 12:28 AM UTC

    Microsoft has published official details regarding this incident on the Microsoft 365 Service Health Dashboard (SHD) under ID EX1183800. Our investigation confirms that the issue originates from Microsoft’s services and is not related to the Xink platform. We’ll continue to monitor the situation, but no action is required from Xink customers at this time. For more information, please refer to Microsoft’s SHD. https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/EX1183800

  3. resolved Nov 08, 2025, 12:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 20, 2024

UK Xink service unreachable

Detected by Pingoru
Nov 20, 2024, 02:30 PM UTC
Resolved
Nov 20, 2024, 03:15 PM UTC
Duration
44m
Affected: Server-side (Re-routing)Admin Portal
Timeline · 2 updates
  1. identified Nov 20, 2024, 04:35 PM UTC

    Clients may experience issues accessing the Xink UK portal due to some services being unreachable or responding slowly. The problem originated from a scheduled automatic update that failed, impacting service availability. To address this issue, we scaled additional resources to restore functionality and improve service performance. We apologize for the inconvenience and appreciate your patience as we work to restore services to normal.

  2. resolved Nov 20, 2024, 04:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2024

Server-side Mail delivery issue - EU Server

Detected by Pingoru
Oct 20, 2024, 10:28 AM UTC
Resolved
Oct 20, 2024, 02:10 PM UTC
Duration
3h 41m
Affected: Server-side (Re-routing)
Timeline · 5 updates
  1. investigating Oct 20, 2024, 10:28 AM UTC

    We are experiencing some problems with the Server-side (rerouting) service. As a result, some of our clients with server-side enabled may experience issues in email delivery. We are currently working on resolving the issue as our TOP PRIORITY. In the meantime, we suggest temporarily disabling the transport rule >https://support.xink.io/support/solutions/articles/1000311916-it-pro-how-to-disable-server-side-transport-rule We will get back with an update when you can re-activate the transport rule. We apologize for this incident and working to resolve it urgently.

  2. identified Oct 20, 2024, 01:21 PM UTC

    Spamhaus (Microsoft's default spam service provider) is blocking our EU IP and some of our clients with rerouting enabled sent messages are not received.

  3. monitoring Oct 20, 2024, 01:25 PM UTC

    EU IP has been delisted with Spamhaus and service is restored.

  4. resolved Oct 20, 2024, 02:10 PM UTC

    This incident has been resolved.

  5. postmortem Oct 22, 2024, 12:38 AM UTC

    Due to SpamHouse \(Microsoft's default spam service provider\) blocking one of our EU IP relay, between October 19, 2024 15:58:51 and October 20, 2024 11:27:37, some of our clients with rerouting enabled received NDRs or were unable to send emails. Below is an error that affected users received. 2024-10-20 11:42:20 1t2UKC-0000000738v-1Zz9 \*\* [xxxx@](mailto:[email protected])domain.com R=dnslookup T=remote\_smtp [H=xxx-nl.mail.protection.outlook.com](http://H=hcs-nl.mail.protection.outlook.com) \[52.101.68.36\] X=TLS1.3:TLS\_AES\_256\_GCM\_SHA384:256 CV=yes: SMTP error from remote mail server after RCPT TO:: 550 5.7.1 Service unavailable, Client host \[40.68.36.243\] blocked using Spamhaus. To request removal from this list see [https://www.spamhaus.org/query/ip/40.68.36.243](https://www.spamhaus.org/query/ip/40.68.36.243) AS\(1440\) \[[DB5PEPF00014B97.eurprd02.prod.outlook.com](http://DB5PEPF00014B97.eurprd02.prod.outlook.com) 2024-10-20T11:42:20.814Z 08DCF05E631C54C6\]

Read the full incident report →