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 August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 29m agoLive, rechecked every 60s
How we know: the official Incode status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

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.

Create a free account

Component statuses may change independently during partial outages.

Recent Incode Outages & Incidents

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

Uptime history4 days observed
Aug 8100.00% averageAug 11
Elevated Errors – Face Recognition (Canada SaaS)Resolved Jul 29, 2026 · 1h 19mResolved

This incident has been resolved. The face recognition service is fully operational and we have confirmed normal performance through monitoring. Thank you for your patience throughout this incident. --- [2026-07-29T14:58:42.297Z] (monitoring) A fix has been implemented and we have confirmed that the face recognition service is now working as expected. We are continuing to monitor the situation closely to ensure full stability. We will provide a final update once we're confident the issue is fully resolved. --- [2026-07-29T14:37:53.382Z] (investigating) We are still investigating the root cause of this issue and continuing to work toward a resolution. We will share our next update within 30 minutes. Thank you for your patience. --- [2026-07-29T14:19:34.008Z] (investigating) We are currently investigating an issue affecting the face recognition service in our Canada SaaS environment. Some requests may be failing or returning errors. Our engineering team is actively investigating and working on a fix. We will provide updates as more information becomes available

SaaS US - Increased latencyResolved Jul 27, 2026 · 32 minResolved

This incident has been resolved. --- [2026-07-27T18:04:22.942Z] (monitoring) We are seeing signs of recovery, latency levels going back to normal. --- [2026-07-27T17:58:25.742Z] (investigating) We are currently investigating the issue

Degradation in SaaS US environmentResolved Jul 9, 2026 · 1h 7mResolved

This incident is now resolved. Facial verification and document processing have been fully stable with normal response times for the past several minutes --- [2026-07-09T23:43:11.985Z] (monitoring) Facial verification and document processing errors have stopped. Response times have returned to normal. We are continuing to monitor the service closely to confirm the issue is fully resolved before closing this incident --- [2026-07-09T23:37:19.891Z] (identified) Response times and error rates are improving across facial verification and document processing as additional capacity comes online. We are closely monitoring to confirm full recovery --- [2026-07-09T23:26:26.605Z] (identified) We are continuing to investigate elevated response times and errors affecting facial verification and document processing. After a period of improvement, we are again seeing increased error rates for a subset of transactions. Our engineering team is actively working on additional mitigations --- [2026-07-09T23:22:03.030Z] (identified) We have identified the cause of the elevated response times affecting facial verification and document processing. A fix was applied. Overall response times are improving --- [2026-07-09T23:11:24.593Z] (identified) We have identified an internal component causing elevated response times for facial verification and document processing and have rolled it back. Response times are improving. We are closely monitoring the service to confirm full recovery --- [2026-07-09T23:01:23.916Z] (investigating) We are currently investigating a service degradation affecting face processing and document processing. Some transactions may experience errors or delays --- [2026-07-09T22:45:04.734Z] (investigating) We have detected a degradation in one of our environments; We are currently investigating.

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

No Incode problems reported yet.

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?

PulsAPI checks Incode every 60 seconds. 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.

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%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Incode.

How fast does PulsAPI detect Incode outages?

PulsAPI polls the official Incode status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

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 PulsAPI account and subscribe to Incode. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Incode status changes.

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. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Incode alongside up to 9 other services at pulsapi.com/signup.

Track Incode with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Incode status changes.

Start free trial