iplicit logo

Is iplicit Down?

FinTech & PaymentsLive status, outages, and incident history

Degraded. iplicit is up but having problems.

iplicit is reporting degraded performance as of November 14, 2026. Expect slower responses or more errors. The affected components are listed below.

DegradedChecked just nowLive · every 60s1 active incident

Don't find out like this next time

You searched to find out iplicit was down. Next time we tell you, usually before your customers do, and always before you think to check.

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

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

Status report

iplicit Status Summary

As of 16:59 UTC on 14 November 2026, iplicit is reporting degraded performance. PulsAPI checked iplicit's official status page and found 7 of 8 components operational, with 1 active incident. The latest incident, "Microsoft 365 Email Disruption", started on Nov 13, 2026 and is still open.

Cite as: PulsAPI, “iplicit status”, checked 14 November 2026, 16:59 UTC. https://www.pulsapi.com/services/iplicit

iplicit Component Status

1 of 8 iplicit components are impaired. Worst problems listed first.

1degraded7operational
Email Service
Degraded
API
Operational
Interfaces » Accounts Payable Automation
Operational

5 more components tracked

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

Also tracking Interfaces » Bank feed, Interfaces » Fixer.io, Interfaces » MTD, Interfaces » XE.com, Iplicit.

See all of them free

Component statuses may change independently during partial outages.

Recent iplicit Outages & Incidents

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

Microsoft 365 Email DisruptionStarted Nov 13, 2026Investigating

Email services are improving as Microsoft progresses recovery from the earlier outage. We are seeing increasing numbers of emails being successfully delivered, although delays may continue while outstanding email backlogs are processed. We will continue to monitor the service as recovery progresses. --- [2026-11-13T11:12:45.946Z] (investigating) We are continuing to investigate this issue. --- [2026-11-13T11:12:24.486Z] (investigating) Microsoft is currently experiencing a widespread service disruption affecting Outlook and Exchange Online, resulting in issues accessing and sending emails. iplicit remains operational. However, functionality that relies on email may be affected: • Sending emails: Sales invoices, authorisation notifications and other emails sent through Microsoft 365 accounts may fail. You can check the Email log and Communication log in iplicit (Settings > Email & Communications) to identify failed messages. We are checking whether failed messages will need to be resent once Microsoft's services are restored, and will confirm here. • Receiving emails from iplicit: Emails sent to mailboxes on Outlook or Microsoft 365 may be delayed or fail to arrive, including verification codes and password reset emails. If you have phone or authenticator app verification set up, please use that to sign in. • AP Automation: Invoices sent or forwarded from Microsoft 365 mailboxes may be delayed in reaching your AP Automation mailbox. Email delivery may be affected differently depending on how your organisation's email account is configured. Emails sent through Microsoft 365 accounts may fail at the point of sending. Emails sent successfully through other providers may still experience delivery delays when the recipient uses Microsoft-hosted email. We recommend checking the Email and Communication logs for important messages, particularly sales invoices and authorisation notifications. We are investigating whether affected messages will require resending once Microsoft's services are restored. Our Support team is also currently unable to reliably receive emails. If you require assistance, please contact Support via in-app chat, or by telephone on 020 3900 2391 rather than by email. We are monitoring the situation and will provide further updates as services are restored. We apologise for any inconvenience.

PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619): iplicit not affectedResolved Oct 26, 2026 · 0 minResolved

Closing this status update. --- [2026-10-22T13:25:11.060Z] (monitoring) On 21 October 2026, critical security vulnerabilities in the PHP programming language were made public. Known as “PHP2Shell”, they are tracked as CVE-2026-109618 and CVE-2026-109619. The UK National Cyber Security Centre (NCSC) has issued guidance asking organisations to find and update any systems that use PHP. We have completed an assessment. The iplicit platform is not built on PHP, so the platform and your data are not affected by these vulnerabilities. We have also reviewed the sub-processors that support our service. Each has confirmed that their services handling iplicit customer data are not affected. You don’t need to do anything, and the iplicit service is running normally. We take the security of your data seriously and follow ISO 27001 practices. We will keep monitoring NCSC guidance and update this notice if anything changes. If you have questions, please contact our Support team in the usual way.

iplicit Uptime History

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

Uptime history3 days observed
Nov 12100.00% average · 2 days with incidentsNov 14

Live iplicit Outage Reports

Problems reported by engineers using iplicit. 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 iplicit problems reported yet.

Are you seeing iplicit problems too?

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

About iplicit

iplicit's status page at status.iplicit.com lists 8 components, such as API, Email Service and Accounts Payable Automation (AP Automation). We read that page every few minutes and keep the incident history, so you can tell whether a problem is on iplicit's side or yours.

iplicit Status FAQ

Is iplicit down right now?

The verdict at the top of this page comes from the latest poll of the official iplicit 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 iplicit 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 iplicit recovers.

How do I check iplicit uptime history?

PulsAPI tracks iplicit uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever iplicit changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect iplicit outages?

PulsAPI reads the official iplicit 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 iplicit components?

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

Can I get alerts when iplicit goes down?

Yes. Create a free account and subscribe to iplicit: 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 iplicit 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 iplicit problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor iplicit?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so iplicit 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 iplicit with the rest of your stack

4372+ 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