All Systems Operational

Uptime over the past 90 days. View historical uptime.
VISP Operational
90 days ago
100.0 % uptime
Today
UBO Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
vPortal Operational
90 days ago
100.0 % uptime
Today
RADIUS Operational
90 days ago
100.0 % uptime
Today
Third Party Operational
90 days ago
100.0 % uptime
Today
Email Service - OpenSRS Operational
90 days ago
100.0 % uptime
Today
Hosting Service - Hostopia Operational
90 days ago
100.0 % uptime
Today
IPpay Operational
90 days ago
100.0 % uptime
Today
Authorize.net Operational
90 days ago
100.0 % uptime
Today
Paypal Operational
90 days ago
100.0 % uptime
Today
PaydUp.net Operational
90 days ago
100.0 % uptime
Today
Elavon Operational
90 days ago
100.0 % uptime
Today
Payment Express Operational
90 days ago
100.0 % uptime
Today
PlugNPay Operational
90 days ago
100.0 % uptime
Today
ProPay Operational
90 days ago
100.0 % uptime
Today
Stripe Operational
90 days ago
100.0 % uptime
Today
Oriental Bank 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.

System Metrics Month Week Day
RADIUS Response Time ?
Fetching
GraphQL API Response Time
Fetching

Sep 4, 2026

No incidents reported today.

Sep 3, 2026

Application Error After Recent Release : "We're sorry, but something went wrong."
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.

Aug 27, 2026

Error When Attempting to Load or View Statements
Resolved - This issue has been resolved. Statement viewing and loading are now functioning normally, and users should no longer encounter errors when accessing statements.

Thank you for your patience while we worked to restore service.
Aug 27, 05:12 UTC
Investigating - We are investigating an issue causing a "Sorry, something went wrong" error when loading or viewing statements.

The issue has been confirmed across multiple ISP instances, and our technical team is actively working on a resolution.

We will provide updates as more information becomes available. Thank you for your patience.
Aug 26, 14:34 UTC

Aug 26, 2026

Aug 25, 2026

No incidents reported.

Aug 24, 2026

No incidents reported.

Aug 23, 2026

No incidents reported.

Aug 22, 2026

No incidents reported.

Aug 21, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage