Vendor reports: operationalResolved · vendor status “resolved”Official status API
Tipalti Hub Issues
Reported by Tipalti · Payments & Fintech · source last read 2 min ago
- Vendor start
- Apr 1, 2024, 14:31 UTC
- Vendor's clock
- Resolved
- Apr 1, 2024, 14:52 UTC
- Vendor's clock
- First seen by Statuswall
- Nov 11, 2026, 02:12 UTC
- Statuswall's clock
- Duration
- 21 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
What is unknown
Last update in these facts: 2026-11-11 02:12 UTC · summary s1, evidence c4d3fa699370aa59
Evidence (8)
- E1Tipalti reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Tipalti Hub Issues". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2024-04-01 14:31 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2024-04-01 14:52 UTC. (vendor) source (opens in a new tab)
- E8First seen by Statuswall: 2026-11-11 02:12 UTC. (Statuswall)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
Tipalti is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Apr 1, 2024, 14:31 UTCVendor-reported startVendor time
- Apr 1, 2024, 14:52 UTCVendor-reported resolutionVendor time
- Nov 11, 2026, 02:12 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall