Incode logo

Is Incode Down?

FinTech & PaymentsLive status, outages, and incident history

No. Incode is up right now.

Every monitored Incode system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · every 60s

Know the moment Incode breaks

Incode is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Incode status page
How we know: the official Incode status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Incode Status Summary

As of 04:24 UTC on 9 November 2026, Incode is operational. PulsAPI checked Incode's official status page and found 9 of 9 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Incode, counting degraded performance as up. The latest incident, "Degraded Performance – End-to-End Encryption (E2EE) Flows in SaaS US", was on Oct 27, 2026 and lasted 40 min.

Cite as: PulsAPI, “Incode status”, checked 9 November 2026, 04:24 UTC. https://www.pulsapi.com/services/incode

Incode Component Status

The main Incode systems on this page. All 9 are operational right now.

9operational
Incode Omni » Omni Australia
Operational
Incode Omni » Omni Canada
Operational
Incode Omni » Omni Demo
Operational

6 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Incode Omni » Omni EU, Incode Omni » Omni Middle East, Incode Omni » Omni US, SOR Data Sources » Argentina Government Validation, SOR Data Sources » México - CURP validation, SOR Data Sources » México - INE Facial Government Validation.

See all of them free

Component statuses may change independently during partial outages.

Recent Incode Outages & Incidents

Incident history from the official Incode status page, including resolution updates.

Degraded Performance – End-to-End Encryption (E2EE) Flows in SaaS USResolved Oct 27, 2026 · 40 minResolved

This incident has been resolved. Between 21:13 and 22:00 UTC, E2EE flows in our SaaS US environment had elevated errors. The service has been working normally since then. We apologize for the inconvenience. --- [2026-10-27T22:34:11.648Z] (monitoring) The service handling E2EE flows in our SaaS US environment has been stable since approximately 22:00 UTC. Onboarding sessions and encrypted session events are processing normally. We are monitoring the service to confirm stability and will provide a final update once the incident is resolved. --- [2026-10-27T22:32:33.756Z] (identified) We have identified the cause of the issue affecting E2EE flows in our SaaS US environment and have applied mitigation measures. The service is available again and error rates are going down, but some users may still see intermittent errors when starting onboarding sessions or processing encrypted session events. Affected sessions can be retried. Other environments and non-E2EE flows are not affected. We will provide another update shortly. --- [2026-10-27T22:02:19.210Z] (investigating) We are currently experiencing an issue affecting the service that handles end-to-end encrypted (E2EE) flows in our SaaS US environment. Starting at approximately 21:14 UTC, some users may see errors or failures when starting onboarding sessions and processing encrypted session events. Affected endpoints (E2EE flows only): /omni/start interview-events e2ee/key

Elevated number of error 500s on several endpointsResolved Oct 5, 2026 · 31 minResolved

This incident has been resolved. --- [2026-10-05T11:36:52.662Z] (monitoring) We are seeing the recovery of systems across the board. The number of errors has returned to normal. --- [2026-10-05T11:30:00.390Z] (investigating) Since 10:54 UTC, some customers have been seeing elevated error rates on Omni API endpoints; our team is actively working on a fix. --- [2026-10-05T11:24:45.027Z] (investigating) We are currently investigating this issue.

Elevated number of errors faceDBResolved Sep 15, 2026 · 1h 28mResolved

This incident has been resolved. --- [2026-09-15T09:06:46.706Z] (identified) A recent infrastructure change caused a temporary service disruption. Recovery is underway, and some users may continue to experience intermittent issues. --- [2026-09-15T08:47:20.594Z] (investigating) We are currently investigating an issue regarding the elevated number of errors in faceDB.

Incode Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Incode incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 9 days with incidentsNov 9

Going further back: Incode uptime by month and every recorded Incode outage.

Live Incode Outage Reports

Problems reported by engineers using Incode. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow
Most recent report
Service DownSevereIowa, United Statesabout 37 days ago

I submitted verification seven times to chime. They are telling me it is not allowing them to see it from their end, but from my end, it is clear photos and perfect submission.

Something wrong with Incode on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Incode

Incode exposes 11 monitored components on its status page at status.incode.com — Incode Omni, Omni Australia and México - CURP validation among them. Follow Incode downtime, degraded performance and resolved incidents here, with uptime history alongside your other payments and fintech services.

Over the past 30 days, PulsAPI has measured Incode uptime at 100.00%. Response times, incident history, and SLA tracking for Incode are available on the PulsAPI dashboard.

Incode Status FAQ

Is Incode down right now?

The verdict at the top of this page comes from the latest poll of the official Incode status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Incode is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Incode recovers.

How do I check Incode uptime history?

PulsAPI tracks Incode uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Incode changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Incode outages?

PulsAPI reads the official Incode status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Incode components?

Yes. PulsAPI monitors 9 individual Incode components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Incode goes down?

Yes. Create a free account and subscribe to Incode: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Incode to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Incode problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Incode?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Incode plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Incode with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services