Juniper Square Outage History

Text message delivery of two-factor authentication codes are sending successfully.

Delays in emails from [email protected] Between 7:52 AM and 8:45 AM PT today, some email notifications sent from [email protected] were delayed rather than arriving right away. No email notifications were lost, only delayed, and any delayed messages have since gone out. If you're still waiting on an email notification you expected, contact [email protected].

We deployed a fix and the Compliance dashboard is now working. Other areas of Manager workspace and the Investor Portal were unaffected. A post-incident review is underway.

Between 4:02 AM PT and 4:12 AM PT, users may have experienced 522 connection errors or timeouts when attempting to log in to GP workspaces and LP portals. A temporary network routing issue with an upstream provider disrupted regional connectivity. Service has fully recovered, and all portal logins, features, and platform capabilities are operating normally.

Scheduled emails are now being correctly sent across the platform. Users should see newly scheduled automated notifications and email campaigns dispatching normally. We have completed our review of emails affected when this issue first occurred and confirmed that no additional emails were impacted. We're continuing to investigate the underlying root cause to prevent future occurrences.

This incident has been resolved. Some customers were temporarily unable to log in to specific workspace domains due to a traffic misrouting issue following a recent infrastructure migration. Our engineering team identified the root cause and resolved the issue. All affected workspace logins are now fully restored and operating normally.

This incident has been resolved.

Manager workspaces were slow to load, to the point of being intermittently inaccessible, from 11:48 PM PT to 12:30 AM PT. Some users may have seen a maintenance page at times during this period. Resolution: We identified that a logging service caused infrastructure over-utilization. We disabled the service and restored access by 12:30 AM PT. All systems returned to normal.

Our engineering team identified a performance regression following a recent update causing the recent performance issues. We rolled back the application to a previous stable version and performance has returned to normal levels. We’ve paused further updates and are actively working on a long term fix to prevent this from happening again. All core features and data remained secure and accessible throughout the incident. Our team is conducting a detailed code review and monitoring stability to ensure continued performance.

An expired domain certificate caused a temporary service disruption. Our engineering team applied a fix to restore connectivity, and all services are now operating normally. We’re reviewing our internal processes to prevent this from happening again.

We’ve successfully deployed a fix for the underlying update that caused the recent service disruption. All systems are continuing to operate normally. We’ll continue to monitor performance to ensure a smooth experience.

Resolved - Email Performance Juniper Square is fully operational. We’ve completed emergency maintenance to fix performance issues affecting email features. This fix addresses the slowdowns some users experienced following our database update on Friday, Feb 13. Our engineering team is now conducting a root cause analysis to identify exactly why the update behaved this way. We’re using these findings to improve our deployment processes and prevent similar issues in the future.

We’ve seen that email delivery has returned to normal. The message backlog is nearly cleared, and all email types are now processing and sending as expected. Our engineering team is continuing to investigate the root cause to ensure ongoing stability. We don’t expect any further delays at this time.

Resolved - Juniper Square platform availability Between approximately 9:10 AM and 9:30 AM PT, Juniper Square was intermittently unavailable. Users may have seen a "temporarily down" message during this window. We identified the issue as resource contention within our database caused by background processing. The site has fully recovered and is operating normally. To prevent recurrence, we are actively implementing optimizations to our background processing and data request logic.

This incident has been resolved.