All Systems Operational

Uptime over the past 90 days. View historical uptime.
VISP Operational
90 days ago
99.98 % 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
99.99 % 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
99.98 % 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
Nov 8, 2025

No incidents reported today.

Nov 7, 2025

No incidents reported.

Nov 6, 2025
Service Outage: VISP.net App Down
Postmortem - Read details
Nov 7, 13:51 UTC
Resolved - The issue that caused the VISP.net app to display the error “We’re sorry, but something went wrong” has been resolved. All services are now fully operational.

Our engineering team identified and corrected the root cause, and systems are being closely monitored to ensure continued stability.

We appreciate your patience while we worked through this issue. A detailed post-mortem report will be shared once it’s available.

— The VISP Team
Nov 6, 17:28 UTC
Update - The team is currently investigating the root cause of the issue and will share a post-mortem report as soon as it becomes available. We are actively monitoring all services to ensure stability. If you are still experiencing issues or have additional concerns, feel free to reach out to your VISP Client Success team via chat, phone, or email.
Nov 6, 14:43 UTC
Monitoring - We received an update that the Visp Web App should now be accessible again. Affected services are now recovering, and the team is continually monitoring the situation. Additional updates will be posted as soon as they are available.
Nov 6, 14:33 UTC
Investigating - Priority: Critical

We’re aware that users are currently unable to access the VISP.net app, encountering the error message:

“We’re sorry, but something went wrong.”

Our team is actively investigating the cause and working to restore full functionality as quickly as possible. This issue is our highest priority at the moment.

We’ll post an update as soon as we have more information.

Thank you for your patience and understanding.
Nov 6, 14:14 UTC
IPpay Outage Alert 11-06-2025
Resolved - Dear valued partners and clients,


The outage event has been resolved as of 10:28 AM Eastern.


Thank you,
IPpay, LLC Seabhac McGinty


Support Operations Manager
Nov 6, 15:51 UTC
Investigating - Valued Partners and Clients –

The IPpay gateway and IPReporting.com are currently experiencing a service outage. Our engineering team is actively working to restore services.

Updates as they become available.

Thank you,

IPpay, LLC
Nov 6, 15:37 UTC
Nov 5, 2025

No incidents reported.

Nov 4, 2025
An important update on your November VISP invoice
Resolved - Resolved
The delay in VISP invoices caused by a technical issue with a script on November 1st has been resolved. All invoices have now been generated successfully.

This issue did not affect subscriber invoices — all subscriber billing processes continued to run normally.

If you notice a temporary notification about a $200 minimum charge, please disregard it. Any incorrect charges that occurred as a result will be refunded as necessary.

ISPs are advised to contact the Client Success Team if they have any questions or need further assistance.
Nov 4, 13:31 UTC
Investigating - Your VISP invoices will be slightly delayed due to a technical issue with a script on November 1st. Our team is currently working to generate them manually.

This issue does not affect your invoices to your subscribers. All your subscriber billing processes are running normally.

You might see a temporary notification about a $200 minimum charge. Please disregard this notice. It's just a temporary alert while we resolve the issue.

Additional updates will be posted as soon as they are available.
Nov 3, 14:25 UTC
Nov 3, 2025
Nov 2, 2025

No incidents reported.

Nov 1, 2025

No incidents reported.

Oct 31, 2025

No incidents reported.

Oct 30, 2025

No incidents reported.

Oct 29, 2025

No incidents reported.

Oct 28, 2025
E-check AutoPay Processing Issue – Under Investigation
Resolved - The issue affecting E-check AutoPay transactions has been resolved. Payment triggers are now processing as expected, and all systems are operating normally. If you have further concerns, please contact the Client Success Team for assistance.

Thank you for your patience while we worked to resolve this matter.
Oct 28, 11:23 UTC
Investigating - We are currently investigating a system-wide issue affecting E-check AutoPay transactions. Reports indicate that scheduled payments did not process as expected, with no charge attempts recorded for impacted accounts.

Initial findings suggest the issue is not gateway-specific. Our DevOps team has confirmed that scheduled jobs executed successfully, but payment triggers were not initiated. A full audit is underway to determine the scope and root cause.

We appreciate your patience and will continue to provide updates as we learn more.
Oct 27, 19:41 UTC
Oct 27, 2025
Oct 26, 2025

No incidents reported.

Oct 25, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage