Enigma Outage History

Enigma is up right now

Enigma had 8 outages in the last 2 years totaling 3h 35m of downtime — averaging 0.3 incidents per month.

There were 8 Enigma outages since December 7, 2025 totaling 3h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.enigma.com

Critical May 22, 2026

Enigma TIN verification service disruption

Detected by Pingoru
May 22, 2026, 06:13 PM UTC
Resolved
May 22, 2026, 06:28 PM UTC
Duration
14m
Affected: TIN Verification
Timeline · 2 updates
  1. investigating May 22, 2026, 06:13 PM UTC

    We’re experiencing a service disruption to the KYB service's TIN verification component. If you use our API to verify TINs/EINs, you may encounter an error. Our team is currently working to restore the service, and we apologize for any inconvenience.

  2. resolved May 22, 2026, 06:28 PM UTC

    This incident has been resolved. Service is fully operational.

Read the full incident report →

Critical May 22, 2026

IRS TIN Match degraded performance

Detected by Pingoru
May 22, 2026, 03:44 PM UTC
Resolved
May 22, 2026, 06:29 PM UTC
Duration
2h 44m
Affected: TIN Verification
Timeline · 2 updates
  1. monitoring May 22, 2026, 03:44 PM UTC

    IRS servers are currently not responding to TIN verification requests. This is common during busy periods and is likely to resolve soon. Our team is monitoring the situation.

  2. resolved May 22, 2026, 06:29 PM UTC

    IRS servers are responding normally to TIN verification requests.

Read the full incident report →

Notice May 14, 2026

GraphQL API Degraded Performance

Detected by Pingoru
May 14, 2026, 05:42 PM UTC
Resolved
May 14, 2026, 05:30 PM UTC
Duration
Timeline · 1 update
  1. resolved May 14, 2026, 05:42 PM UTC

    We’re currently experiencing degraded performance issues with the GraphQL and KYB v2 APIS. Our team is currently working to restore normal performance levels. We apologize for any inconvenience.

Read the full incident report →

Major April 30, 2026

GraphQL API Outage

Detected by Pingoru
Apr 30, 2026, 05:06 PM UTC
Resolved
Apr 30, 2026, 05:10 PM UTC
Duration
3m
Affected: GraphQL APIKYB Service v2
Timeline · 3 updates
  1. investigating Apr 30, 2026, 05:06 PM UTC

    We’re experiencing a service outage with the GraphQL API. Our team is currently working to restore the service. We apologize for any inconvenience.

  2. investigating Apr 30, 2026, 05:06 PM UTC

    We are continuing to investigate this issue.

  3. resolved Apr 30, 2026, 05:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 17, 2026

Enigma KYB v2 outage

Detected by Pingoru
Mar 17, 2026, 05:15 PM UTC
Resolved
Mar 17, 2026, 05:31 PM UTC
Duration
16m
Affected: KYB Service v2
Timeline · 2 updates
  1. investigating Mar 17, 2026, 08:52 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 17, 2026, 08:52 PM UTC

    This incident has been resolved. Service is fully operational.

Read the full incident report →

Critical March 6, 2026

Enigma KYB watchlist screening disruption

Detected by Pingoru
Mar 06, 2026, 12:47 AM UTC
Resolved
Mar 06, 2026, 01:02 AM UTC
Duration
14m
Affected: Watchlist Screening
Timeline · 2 updates
  1. investigating Mar 06, 2026, 12:47 AM UTC

    We’re experiencing a disruption to the KYB service's watchlist screening component. If you use our API to screen entities against government watchlists, you may encounter an error. Our team is currently working to restore the service, and we apologize for any inconvenience.

  2. resolved Mar 06, 2026, 01:02 AM UTC

    This incident has been resolved. Service is fully operational.

Read the full incident report →

Notice February 28, 2026

Enigma KYB degraded performance

Detected by Pingoru
Feb 28, 2026, 05:43 AM UTC
Resolved
Feb 28, 2026, 05:43 AM UTC
Duration
34s
Timeline · 2 updates
  1. investigating Feb 28, 2026, 05:43 AM UTC

    We’re currently experiencing degraded performance issues with the KYB service. Our team is currently working to restore normal performance levels. We apologize for any inconvenience.

  2. resolved Feb 28, 2026, 05:43 AM UTC

    This incident has been resolved. Service is fully operational.

Read the full incident report →