All Systems Operational

Uptime over the past 90 days. View historical uptime.
Payments API Operational
90 days ago
99.99 % uptime
Today
Entities API Operational
90 days ago
100.0 % uptime
Today
Checkout API Operational
90 days ago
100.0 % uptime
Today
Webcomponents Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

DB Scheduled Maitenance Jul 22, 2025 06:00-08:00 UTC

We will be updating our DB engine version and applying a new monitoring agent to our instances
Posted on Jul 07, 2025 - 14:41 UTC
Jul 18, 2025

No incidents reported today.

Jul 17, 2025

No incidents reported.

Jul 16, 2025

No incidents reported.

Jul 15, 2025

No incidents reported.

Jul 14, 2025

No incidents reported.

Jul 13, 2025

No incidents reported.

Jul 12, 2025

No incidents reported.

Jul 11, 2025

No incidents reported.

Jul 10, 2025

No incidents reported.

Jul 9, 2025
Webcomponents: legacy components affected by security change
Postmortem - Read details
Jul 15, 16:12 UTC
Resolved - A security deployment in one of our domains disrupted legacy web components. Our infrastructure team created a new domain for improved security and isolation of our tokenization API. An update was made to the tokenization Web component. This change also impacted the legacy web component unintentionally. During that time, legacy web component users were not able to tokenize new cards. Our web component team has modified the code to ensure this will not happen again.
Jul 9, 18:00 UTC
Jul 8, 2025

No incidents reported.

Jul 7, 2025

No incidents reported.

Jul 6, 2025
Payments API Service Disruption
Resolved - Timeline

Jul 06, 2025 at 4:45 AM CST - JustiFi was alerted that database utilization reached 90%

Jul 06, 2025 at 4:55 AM CST - Database auto-scaling process initiated automatically

Jul 06, 2025 at 5:03 AM CST - Incident alert created due to some payment transactions not being saved successfully

Jul 06, 2025 at 5:05 AM CST - Auto-scaling process completed and all services resumed normal operation

Summary

A brief service disruption occurred affecting payment processing. Our automated systems detected and resolved the issue within 20 minutes. We apologize for any inconvenience this may have caused.
Jul 6, 10:00 UTC
Jul 5, 2025

No incidents reported.

Jul 4, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage