Is Xink down?

Last checked 7m ago
Current status
Xink is up

No incidents right now.

Official status page: https://status.xink.io · Polled every 5 minutes · 32 components tracked

Xink is operational right now. Last checked 7m ago; the most recent incident resolved 18d ago.

Real-time Xink status, recent outages, and incident history — pulled directly from Xink's official status page at https://status.xink.io every 5 minutes. Pingoru tracks 32 Xink services and has captured 6 incidents in the last 90 days (99.69% uptime). Get email, Slack, Discord, or webhook alerts the moment Xink reports a new incident — free for 5 monitors, no credit card.

Users who monitor Xink also follow these Marketing services: Mailgun Klaviyo Iterable Braze Brevo Customer.io ZoomInfo Optimizely SurveyMonkey Yotpo View all 6,000+ providers
Xink uptime 99.69% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 18m
    Started May 26, 2026, 09:02 AM UTC · Resolved May 26, 2026, 09:21 AM UTC
    Outlook Add-in
    Timeline · 2 updates
    • identified · May 26, 2026, 09:02 AM UTC

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

    • 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.

    Latest: 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.

  2. Resolved 2h 14m
    Started May 20, 2026, 07:45 AM UTC · Resolved May 20, 2026, 10:00 AM UTC
    Outlook Add-in
    Timeline · 2 updates
    • identified · May 20, 2026, 09:54 AM UTC

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

    • 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.

    Latest: 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 settin…

  3. Resolved 2h 4m
    Started May 19, 2026, 07:45 AM UTC · Resolved May 19, 2026, 09:49 AM UTC
    Outlook Add-in
    Timeline · 3 updates
    • identified · May 19, 2026, 09:39 AM UTC

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

    • identified · May 19, 2026, 09:42 AM UTC

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

    • 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.

    Latest: 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 …

  4. Resolved 1h
    Started May 18, 2026, 08:36 AM UTC · Resolved May 18, 2026, 09:36 AM UTC
    Outlook Add-in
    Timeline · 2 updates
    • identified · May 18, 2026, 09:36 AM UTC

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

    • resolved · May 18, 2026, 09:36 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 6h 58m
    Started Apr 03, 2026, 02:45 AM UTC · Resolved Apr 03, 2026, 09:44 AM UTC
    IntegrationsIntegrationsIntegrationsIntegrationsIntegrations
    Timeline · 2 updates
    • 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.

    • resolved · Apr 03, 2026, 09:44 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Xink outage history

1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Xink outage history →

Or sign up free to get alerts when Xink breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 6 incidents View full outage history →