All Systems Operational

VISP Operational
UBO Operational
API Operational
vPortal Operational
RADIUS Operational
Third Party Operational
Email Service - OpenSRS Operational
Hosting Service - Hostopia Operational
IPpay Operational
Authorize.net Operational
Paypal Operational
PaydUp.net Operational
Elavon Operational
Payment Express Operational
PlugNPay Operational
ProPay Operational
Stripe Operational
Oriental Bank Operational
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.
RADIUS Response Time ?
Fetching
GraphQL API Response Time
Fetching

Sep 11, 2026

No incidents reported today.

Sep 10, 2026

No incidents reported.

Sep 9, 2026

No incidents reported.

Sep 8, 2026

No incidents reported.

Sep 7, 2026

No incidents reported.

Sep 6, 2026

No incidents reported.

Sep 5, 2026

No incidents reported.

Sep 4, 2026

No incidents reported.

Sep 3, 2026

Resolved - Fixed the issue where some users were seeing an outdated version of the application after a release. Browsers will now automatically load the latest version, eliminating the need for a manual cache refresh in most cases. If you need assistance , contact the Client Success Team
Sep 3, 11:14 UTC
Update - We are continuing to work on a fix for this issue.
Sep 3, 11:14 UTC
Identified - Following a recent release, some users may encounter the message:

"We're sorry, but something went wrong."

This can occur when opening customer accounts or navigating to other areas of the application. The issue is typically caused by the browser loading an older cached version of the application while newer files have already been deployed.

Required Action:

Perform a hard refresh by pressing Ctrl + F5 (Windows) or Cmd + Shift + R (Mac).
If the issue continues, clear your browser cache and reload the application.

This will ensure your browser downloads the latest application build and resolves the mismatch between cached and updated files.

If you continue to experience issues after performing these steps, please contact the VISP Client Success Team for assistance.

We apologize for the inconvenience and appreciate your patience.

Sep 2, 12:38 UTC

Sep 2, 2026

Sep 1, 2026

No incidents reported.

Aug 31, 2026

No incidents reported.

Aug 30, 2026

No incidents reported.

Aug 29, 2026

No incidents reported.

Aug 28, 2026

No incidents reported.