User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
Is Iplicit down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft 365 Email Disruption
Source: the vendor's status page · We are not affiliated with Iplicit.
What to try while Iplicit is having problems
Estimated fix: Not enough Iplicit history yet; similar Money outages lasted 56 min (median, typically 29 min–2 h; 19 outages).
- Avoid repeating payments or trades; check your history first. Cards and ATMs often still work.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → iplicit.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 49 min ago. Last stored result reached it in 131 ms.
Official status
Minor incident
Microsoft 365 Email Disruption Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 266 ms | 0 |
| Mon 22 | 0 | 0.0 | 140 ms | 0 |
| Tue 00 | 0 | 0.0 | 35 ms | 0 |
| Tue 02 | 0 | 0.0 | 68 ms | 0 |
| Tue 04 | 0 | 0.0 | 101 ms | 0 |
| Tue 06 | 0 | 0.0 | 79 ms | 0 |
| Tue 08 | 0 | 0.0 | 112 ms | 0 |
| Tue 10 | 0 | 0.0 | 101 ms | 0 |
| Tue 13 | 0 | 0.0 | 47 ms | 0 |
| Tue 15 | 0 | 0.0 | 124 ms | 0 |
| Tue 17 | 0 | 0.0 | 309 ms | 0 |
| Tue 19 | 0 | 0.0 | 61 ms | 0 |
| Tue 22 | 0 | 0.0 | 81 ms | 0 |
| Wed 00 | 0 | 0.0 | 67 ms | 0 |
| Wed 02 | 0 | 0.0 | 121 ms | 0 |
| Wed 04 | 0 | 0.0 | 39 ms | 0 |
| Wed 07 | 0 | 0.0 | 59 ms | 0 |
| Wed 09 | 0 | 0.0 | 51 ms | 0 |
| Wed 11 | 0 | 0.0 | 99 ms | 0 |
| Wed 13 | 0 | 0.0 | 105 ms | 0 |
| Wed 15 | 0 | 0.0 | 95 ms | 0 |
| Wed 17 | 0 | 0.0 | 185 ms | 0 |
| Wed 20 | 0 | 0.0 | 58 ms | 0 |
| Wed 22 | 0 | 0.0 | 89 ms | 0 |
| Thu 00 | 0 | 0.0 | 107 ms | 0 |
| Thu 02 | 0 | 0.0 | 58 ms | 0 |
| Thu 04 | 0 | 0.0 | 89 ms | 0 |
| Thu 06 | 0 | 0.0 | 77 ms | 0 |
| Thu 08 | 0 | 0.0 | 33 ms | 0 |
| Thu 10 | 0 | 0.0 | 31 ms | 0 |
| Thu 12 | 0 | 0.0 | 164 ms | 0 |
| Thu 14 | 0 | 0.0 | 107 ms | 0 |
| Thu 17 | 0 | 0.0 | 40 ms | 0 |
| Thu 19 | 0 | 0.0 | 116 ms | 0 |
| Thu 21 | 0 | 0.0 | 96 ms | 0 |
| Thu 23 | 0 | 0.0 | 69 ms | 0 |
| Fri 01 | 0 | 0.0 | 83 ms | 0 |
| Fri 03 | 0 | 0.0 | 112 ms | 0 |
| Fri 05 | 0 | 0.0 | 86 ms | 0 |
| Fri 07 | 0 | 0.0 | 62 ms | 0 |
| Fri 09 | 0 | 0.0 | 27 ms | 0 |
| Fri 11 | 0 | 0.0 | 32 ms | 0 |
| Fri 12 | 0 | 0.0 | 60 ms | 0 |
| Fri 14 | 0 | 0.0 | 66 ms | 0 |
| Fri 16 | 0 | 0.0 | 151 ms | 0 |
| Fri 18 | 0 | 0.0 | 132 ms | 0 |
| Fri 19 | 0 | 0.0 | 99 ms | 0 |
| Fri 21 | 0 | 0.0 | 131 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Iplicit badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Iplicit yet. Outages of 10 minutes or more get their own page here.
Having trouble with Iplicit?
One report per service every 10 minutes from this network. No account.
Follow Iplicit
Get an email when Iplicit goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Iplicit alerts to Slack, Discord or a webhook — free.
About Iplicit
We track Iplicit (iplicit.com) as part of the Money group. iplicit is cloud accounting software designed for growing organisations, combining real time reporting, automated workflows and multi entity consolidation.
Iplicit publishes an official status page at status.iplicit.com; when we can read it, its incident level is folded into the status shown here.
Common problems for money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 85 ms average, 27–151 ms range across 13 successful checks.
Questions
Is Iplicit down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft 365 Email Disruption
When was Iplicit last down?
We have not recorded a public Iplicit incident since monitoring began 6 days ago.
What is Iplicit's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Iplicit respond?
85 ms on average over the last 24 hours (27–151 ms).
Does Iplicit have an official status page?
Yes, at https://status.iplicit.com.
Iplicit not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Iplicit here at once, the problem is on Iplicit's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Iplicit. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.